I fixed this. We had copied known-good zone files from a production box for the testing. However, we did not add records for our new IP address we were testing with. Adding the appropriate PTR and A records solved the issue.
What I was doing was testing a BIND 8 setup for split DNS (the term split-brain DNS gives me the creeps). Have it working now. Could have used BIND 9, but I keep reading that the new version is a little too tough on requiring proper DNS behavior and some clients don't work right with it. Haven't really investigated this issue too far yet. At 10:20 AM 4/18/2003 -0500, you wrote: >You are welcome. > >Were you the only 10.0.0.13 on the network? I'm able to ping 10.0.0.13 >and 10.0.0.21 from behind my firewall, though they refuse a telnet >connection and are not running DNS. Would that foul things up? > >On 2003.04.18 08:44 Dustin Puryear wrote: > > 10.0.0.13 is indeed up. Otherwise named could not bind to it as shown by > > sockstat. Certainly a valid thing to test Will, thanks. > > > >_______________________________________________ >General mailing list >[email protected] >http://brlug.net/mailman/listinfo/general_brlug.net --- Dustin Puryear <[EMAIL PROTECTED]> Puryear Information Technology Windows, UNIX, and IT Consulting http://www.puryear-it.com
