|Neill R on 1 Jun 2008 20:26:06 -0700|
I have an internal bind 9.2 name server - 10.10.5.33 which is the primary NS for dozens of client systems. The server is setup in such as way where it is authorative for all client zones - such as client1.company.com, client2.company.com, but for all other requests (like google.com) it forwards to our ISP's Name Server.
I recently ran into a situation where a new *compliant* client (client 3) does not want their zone files on the same machine as other client zones, so I decided we can setup a seperate name server on the client network - 10.10.20.33 and just setup a "type forward" zone entry on my primary NS for client3.company.com. I configured the compliant client zones and rolled out the new DNS server with no issues. However, when I try to resolve client3.company.com via the primary NS I get no answer. Below is a sample of my primary NS named.conf. I have ruled out mosty all the obvious things, like network connectivity and access to the DNS ports, and DNS control ports.
Thanks in advance
//Client 1 Zones
//Client 2 Zones
___________________________________________________________________________ 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