> Ok, so adding it to /etc/resolv.conf is actually one of the supported ways.
well, I wouldn't call it 'supported' as you're then responsible for managing the resolv.conf file, but it will bypass resolved completely (assuming you don't put 127.0.0.53 in the file, and you only use your upstream nameserver(s)). The normal glibc getaddrinfo() that uses the resolv.conf entries to find nameserver(s) to query is of course supported no matter what you have in the resolv.conf file, but that rarely has bugs. > try connecting to that address: > > avl@fpc:~$ telnet fe80::4687:fcff:fe9e:4ac7 22 > Trying fe80::4687:fcff:fe9e:4ac7... > telnet: Unable to connect to remote host: Invalid argument you want to telnet to your local host? anyway, Ubuntu isn't the right place to take this up - you should open an upstream bug to systemd if this is an issue for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853669 Title: systemd resolves own hostname to link local ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
