redirecting root hints to fake internal root server

Colin Harvey colinedwardharvey at
Tue Aug 27 18:44:43 UTC 2013

Thanks for the information.  Sorry for not posting my named.conf but privacy rules... 
My landscape is on domain for which I am wholly authoritative.  Internally I need to resolve from Corporate.  Thus I don't have the child/parent type delegation issue as you describe.  

From: Ben Croswell <ben.croswell at>
To: Colin Harvey <colinedwardharvey at> 
Cc: bind-users at; WBrown at; " at" < at> 
Sent: Tuesday, August 27, 2013 2:37 PM
Subject: Re: redirecting root hints to fake internal root server

If you load a parent domain, in this case ., you must have a delegation for the child domain in the parent the parent. Even though that delegation isn't used for resolution purposes it lets the parent know the child exists. The child won't be forwarded if the server believes it doesn't exist. 
For example if I load and also want to forward there must be an NS delegation for it. If there isn't the server says I load and doesn't exist so there is no reason to forward. 
Hard to tell if this is your issue with no config to look at, but it may be.
On Aug 27, 2013 2:14 PM, "Colin Harvey" <colinedwardharvey at> wrote:

Thanks.  But I already have that option for the zone.  Still not seeing traffic going to
>From: "WBrown at" <WBrown at>
>To: Colin Harvey <colinedwardharvey at> 
>Cc: bind users <bind-users at>; at 
>Sent: Tuesday, August 27, 2013 1:20 PM
>Subject: Re: redirecting root hints to fake internal root server
>From: Colin Harvey <colinedwardharvey at>
>> My environment is firewalled from the real world.  For queries on 
>> zones to which I'm not master, I want to recurse to a corporate 
>> server.  nslookup 
>> internal.corporate.server works fine.  Setting "." to use this 
>> internal server in the root.hints file does not.  In fact I do not 
>> even see my system trying to recurse.  (I'm looking at network 
>> traffic with a sniffer.)
>> My root.hints:
>> .    600    IN    NS    internal.corporate.server.
>> internal.corporate.server.    600    IN    A
>> Alternatively I've setup a forwarding zone in named.conf to query 
>> for ''.  When monitoring the 
>> network for udp data over port 53, I'm not even seeing the query 
>> being forwarded.  Why?
>Add these lines to your options section:
>        forward only;
>        forwarders {;};
>Confidentiality Notice: 
>This electronic message and any attachments may contain confidential or 
>privileged information, and is intended only for the individual or entity 
>identified above as the addressee. If you are not the addressee (or the 
>employee or agent responsible to deliver it to the addressee), or if this 
>message has been addressed to you in error, you are hereby notified that 
>you may not copy, forward, disclose or use any part of this message or any 
>attachments. Please notify the sender immediately by return e-mail or 
>telephone and delete this message from your system.
>Please visit to unsubscribe from this list
>bind-users mailing list
>bind-users at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list