Public bug reported:
I have been symlinking /etc/resolv.conf to a stub file generated using
the resolvconf service (i believe this is default behavior). I just
pushed a change to all the desktops under my control to remove this
symlink, and manage /etc/resolv.conf as a static file. Immediately
after, DNS resolution failed for about 1/3 of the desktops under my
control. I was able to fix this by sending the "touch /etc/resolv.conf"
command to all our desktops (via saltstack).
Further information:
OS: Ubuntu Focal 20.04
Kernel: 5.11.0-27-generic or 5.11.0-41-generic
Method of deploying changes: saltstack
Reproduce:
if [ -L /etc/resolv.conf ]
then
unlink /etc/resolv.conf
fi
cat > /etc/resolv.conf <<EOF
nameserver xx.xx.xx.xx
nameserver yy.yy.yy.yy
domain example.com
search example.com
options ndots:2 timeout:1
EOF
ping google.com # fails
touch /etc/resolv.conf
ping google.com # succeeds
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: dns resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957993
Title:
DNS issues when replacing /etc/resolv.conf symlink with static file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1957993/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
