Aaron Mulder on 18 Oct 2006 18:38:40 -0000 |
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) I don't get this, since as far as I can tell 192.168.0.1 should forward first to 192.168.1.1 and itself get the answer in a fraction of a second and return to the caller. Any suggestions? I don't know how to tell where the problem is. Unfortunately it's not an option to just point clients to 192.168.1.1 because the "internal" BIND server has host data for the internal domain and the upstream fast server does not. Thanks, Aaron ___________________________________________________________________________ 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
|
|