Strange behavior with zone forwarding.

Nate Campi nate at wired.com
Fri Feb 22 17:56:09 UTC 2002


On Fri, Feb 22, 2002 at 12:54:41PM +0000, jjhirschauer at duke-energy.com wrote:
> 
> I am on BIND 8.2.2-P5+IBM. I have many master zones, a few slave zones, 
> and a few forward zones. The master and slave zones work fine. One of the 
> forward zones (not sure about the rest) works sometimes. Example: I start 
> named, check the log and everthing looks good, dig for 
> hostname.fwddomain.com (internal zone with name changed) and get the 
> proper response. I stop named, start named, check log (everything okay), 
> and perform the same dig. This time the server thinks that it has to go 
> outside for the answer and returns only the external SOA of fwddomain.com 
> with an NXDOMAIN response. This behavior is completely unpredictable. Any 
> thoughts?

To forward the .test TLD internally, I make sure I "forward only", thus
no fallback to outside DNS servers.

zone "test" {
        type forward;
        forward only;
        forwarders { 10.0.0.10; };
};

-- 
Nate Campi     Job: hostmaster at lycos.com and root at wired.com

"A C program is like a fast dance on a newly waxed dance floor by people
carrying razors."    - Waldi Ravens. 



More information about the bind-users mailing list