@enr0n Nick, did you compare the full path of what i wrote? Also what do you mean if I could provide specific example? As i wrote in main question you dont need anything specific as i tried in fresh brand new Ubuntu 22.04. Just install fresh new operating system and try to resolve google.com and system wont resolve, as it appears, the path is wrong initially. If you read closely, the path that to resolv.conf in the OS has two dots, while it should have no dots in the beginning of the path. Thats why i tested and asked here thinking that there is a bug
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Invalid Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
