Home / user-156174

platzhirsch's questions

Martin Hope
platzhirsch
Asked: 2019-09-20 17:38:37 +0800 CST
  • 2

This seems to be a behavior difference which only started in either 18.10 or 19.04.

While avahi-resolve --name my.subdomain.local returns a valid IP address and is working it doesn't work outside of that, i.e. ping, curl or chrome.

The name resolution does still work though for subdomain.local. This seems to be related to the fact that *.subdomain.local is resolved as mDNS CNAME.

Content of nsswitch.conf

passwd:         compat systemd
group:          compat systemd
shadow:         compat
gshadow:        files

hosts:          files mdns4_minimal [NOTFOUND=return] dns
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

Content of /etc/resolv.conf

nameserver 127.0.0.53
options edns0
dns avahi 19.04 mdns
Martin Hope
platzhirsch
Asked: 2016-05-25 00:34:06 +0800 CST
  • 0

On a Thinkpad X1 Carbon 4th Generation installing Ubuntu 16.04 with home encryption enabled I ran into the same problem as described here: After new Ubuntu 15.04 installation, startup asks for password even though no disk encryption was set up

I tried to solve it using the proposed answers, however, there is no /dev/disk/by-id only:

  • by-partlabel
  • by-partuuid
  • by-uuid

Fstab tells me the following information

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=a7a2ee5e-14a7-423a-b32d-7f73bc076ce6 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=F2B1-8BBE  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/nvme0n1p3 during installation
#UUID=41826f3b-d376-4e1e-9ce6-0370b1b9969d none            swap    sw              0       0

And `sudo cat /etc/cryptab' returns:

cryptswap1 UUID=41826f3b-d376-4e1e-9ce6-0370b1b9969d /dev/urandom swap,offset=1024,cipher=aes-xts-plain64

It looks to me like the configuration is correct which I why I assume it's a NVMe specific issue.

16.04