I found something very strange. On the affected system:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
So, the loopback interface only has IPv4 on it somehow. Yet, IPv6 is
enabled on the system, and other network interfaces have IPv6 addresses
assigned to them fine.
I rebooted the system and it is now in the state I would have expected,
where loopback has both address families assigned:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
However, I do reboot this system regularly, and I have had the resolved
issue for quite some time, so there must be something that happens
during normal system operation that causes the loopback address to be
unassigned. I do not understand what could possibly cause that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2136976
Title:
DNSStubListenerExtra=[::1]:53 stopped working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2136976/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
