Some troubleshooting I did with Trent today showed:

a) the "host -t soa local." call triggered a query to 127.0.0.53 as
expected, network-wise, which got a response right away

b) we snapshotted ip route and ip addr just before the host call, and
saw that the interface responsible for the default route (and route to
his dns server) was still down. I wonder if dns_reachable() in
/usr/lib/avahi/avahi-daemon-check-dns.sh is doing the right thing. It
looks for 127.0.0.1 (and not 127.0.0.53), and, failing that, for a
default route. The default route exists, but the link it goes through is
still down:

2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel
state DOWN group default qlen 1000

default via x.x.x.x dev eno1 onlink linkdown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to