Am 16.05.19 um 16:09 schrieb Vincent Lefevre: > On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote: >> On 2019-05-16 14:41:44 +0200, Michael Biebl wrote: >>> Am 16.05.19 um 14:22 schrieb Vincent Lefevre: >>>> On 2019-05-16 14:15:37 +0200, Michael Biebl wrote: >>>>> Looks like you have a local resolver configured in /etc/resolv.conf >>>>> (which should be reachable via lo, even if eth0 is down). >>>> >>>> Yes, /etc/resolv.conf contains >>>> >>>> nameserver 127.0.0.1 >>>> nameserver 192.168.1.1 >>>> >>>> as I use "unbound". >>> >>> So host talks to unbound, which apparently takes those 12s to answer. >>> Not sure what can be done about this in avahi-daemon. Ideas? >> >> Should this be regarded as a bug in unbound, then? > > Actually, no, unbound is not the problem: > > Whether I have > > nameserver 127.0.0.1 > nameserver 192.168.1.1 > > or just > > nameserver 192.168.1.1 > > in /etc/resolv.conf, "time host -t soa local." shows a 10-second > timeout.
If you don't have network access, then this is expected, I'd say. What happens, if you only list your local 127.0.0.1 in /etc/resolv.conf? > Or would the old /etc/resolv.conf (with 127.0.0.1) be cached somewhere > on the system? > Well, the assumption that /usr/lib/avahi/avahi-daemon-check-dns.sh makes is, that if a local resolver is configured in /etc/resolv.conf, then it is safe to assume that host lookup can be done, even if there is not default route (== network access). -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
