Re: Single Zone Forwarding Dilema

2009-06-08 Thread Kal Feher
First you should check that you can receive a valid response for the
intended zone from your forwarders (from your caching server) not from your
pc. It wasn't clear from your initial email that this is what you did.

yourcacheserver ~ # dig @forwarder_address A host.fwd.zone.net

Although it may seem appropriate to mask the domain you are looking up. It
does make solving your problem quite difficult. If the above test works yet
other queries fail, I would suggest providing the full result of a:

yourlocalpc ~ # dig @yourcacheserver A host.fwd.zone.net

You may also wish to provide the query logs for this query.


On 8/6/09 4:01 PM, Matus UHLAR - fantomas uh...@fantomas.sk wrote:

 On 06.06.09 01:10, Ben Croswell wrote:
 If you want to force forwarding you will probably want to add the forward
 only; directive.
 
 By default your server will try to follow NS delegations and then forward if
 it can't follow them
 
 I think it's the opposite - the server will try to query the configured
 forwarders first, then to continus in usual NS resolution.
 
 Forward only; tells it to not even bother trying to follow NS delegations.
 
 and thus I recomment not to use this for public zones - if the forwarders
 are unavailable or from some reason can't answer, the classic resolution
 will be used.
 
 I guess the configured forwarders have one of these problems

-- 
Kal Feher

___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Single Zone Forwarding Dilema

2009-06-05 Thread Mark S. Turczan

Folks,

I'm trying to understand the behavior of a single zone that I'm  
forwarding queries for.


Essentially, when I do a dig fwd.zone.net SOA the request seems to be  
properly forwarded to the nameservers in the forward statement. I've  
verified this with tcpdump running on my primary nameserver.


But when I attempt to resolve a host record in fwd.zone.net it doesn't  
seem to be forwarded to the proper nameservers and instead goes out to  
the Internet.


I've verified that the host record exists on the remote nameservers to  
which I am forwarding by looking up the record directly from the  
remote nameserver.


This is what the forwarded zone's configuration looks like:

// zone: fwd.zone.net
zone fwd.zone.net
{
type forward;
forwarders { public ip withheld; public ip withheld; };
};

Am I correct in understanding that each and every query for any record  
in the forwarded zone should be forwarded to the specified nameservers  
and not go out to the Internet? BTW, I'm running BIND 9.3.5-P1.


Regards,

Mark




___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users