Did a quick test with the originally attached test file, this only happens if 'mdns4' is last on the nsswitch.conf line. I don't think this is the default we ship anymore, we currently ship:
hosts: files mdns4_minimal [NOTFOUND=return] dns
TJ: Do you have the exact nsswitch.conf line the user was using?
With regards to the multi second timeouts.. this should only happen if the user is looking up a .local hostname or reverse DNS specifically for 169.254.x.x.. I'd also wonder if they had a interface with a 169.254 link-local address assigned. Do you also happen to have the output of "ip addr" and "ip -6 addr"
Alternative I am lathiat on IRC, maybe you can put me in contact with the user?
Did a quick test with the originally attached test file, this only happens if 'mdns4' is last on the nsswitch.conf line. I don't think this is the default we ship anymore, we currently ship:
hosts: files mdns4_minimal [NOTFOUND=return] dns
TJ: Do you have the exact nsswitch.conf line the user was using?
With regards to the multi second timeouts.. this should only happen if the user is looking up a .local hostname or reverse DNS specifically for 169.254.x.x.. I'd also wonder if they had a interface with a 169.254 link-local address assigned. Do you also happen to have the output of "ip addr" and "ip -6 addr"
Alternative I am lathiat on IRC, maybe you can put me in contact with the user?