Michael C. Toren on 18 Oct 2006 18:52:33 -0000 |
On Wed, Oct 18, 2006 at 02:38:35PM -0400, Aaron Mulder wrote: > We have a BIND 9.3.1 server that seems not very responsive and an > upstream DNS server that is quite fast. Let's say the BIND server is > 192.168.0.1 and the upstream server is 192.168.1.1. In the BIND > configuration for 192.168.0.1, we have: > > options { forward first; forwarders { 192.168.1.1; }; ... }; > > So then if you go to a client on the network whose DNS server is > 192.168.0.1 you get this: > > nslookup yahoo.com 192.168.1.1 > (returns in a fraction of a second) > nslookup yahoo.com 192.168.0.1 > (takes a while, sometimes times out, sometimes returns in 10+ seconds) Just a guess, but it sounds like perhaps the 192.168.0.1 server is attempting to contact the forward-first server but timing out, and then going out to the internet at large to resolve the request. One way to test this theory would be to change the "forward first" line of the configuration to "forward only", and then see if the server is *ever* able to resolve a request... -mct ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|