Hello Jeremy, Thank you for your reply.
>> Let me define what "hung" means in our experience: We find that named is >> running but will not respond to queries, "rndc status" will respond with >> output but that output shows that named is not processing any queries (see >> below), other rndc commands appear to work as well (e.g., "rndc dumpdb"). > >Does it work if you restart named? Yes. That is, everything is up and running again after we restart named. 9.9.1-P3 has been running on several servers since 10/3 without any known issues... until today. > >If not, can you confirm it is listening on your intended interfaces >(including 127.0.0.1) even if not working? > >> $ time host www.google.com 127.0.0.1 >> ;; connection timed out; no servers could be reached > >Can you confirm that you can query for that without? (Such as dig >@216.239.34.10 www.google.com or dig @8.8.8.8 www.google.com) > >> $ time host localhost 127.0.0.1 >> ;; connection timed out; no servers could be reached > >Do you have a localhost zone defined? (Sometimes the messages from host >like the one above are misleading and even the named may be working >correctly but it is slow.) Yes, we do have a localhost zone defined. However, queries for 3rd party hostnames (e.g., www.google.com) were failing as well. > > Jeremy C. Reed > ISC > > _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
