View Single Post
  #7   (View Single Post)  
Old 15th May 2008
crayoxide crayoxide is offline
Fdisk Soldier
 
Join Date: May 2008
Posts: 46
Default

Quote:
Originally Posted by cwhitmore View Post
I went to advanced settings from Windows DNS and choose "BIND secondaries" which eliminated most of the errors.
hrmmm ... something is not adding up here as that does not make sense.

Usually, the "BIND secondaries" option's default mode is selected. It is there only for versions of BIND 4.9.4 and earlier. Windows 2k and 2k3 servers compress the transfer and BIND <= 4.9.4 would choke on it. Not that it matters that much as it just toggles compression, but it should not be a factor that helped eliminate errors for a BSD box with a default install.

Perhaps too much shotgunning of options has taken place and it is time to regroup? Some thoughts to consider to help you baseline:

1. Is the BSD box a default install without any additional makes with strange options set that may have taken place and it is running version 7 of the OS?

2. Is the BSD box in the same room/subnet on the same switch stack as the MS DNS servers?

If you can do a zone transfer whilst in house but then it fails remotely, it is a network topology issue as opposed to a configuration issue.

This next point might be a non-issue ..

3. If the DNS server is config'd to ask a WINS server for names it can not find, it will insert a record in the zone datafile that *is not* a standard record type and BIND will refuse to load the zone.

4. Since you have the option checked that says "Only Servers listed on the Name Servers tab", try switching it to "Only to the following servers" and hard code in an IP address instead of relying on yet another DNS lookup just to get an IP address.

HTH's
Reply With Quote