Entry

I can't query dnscache for domains that I host with tinydns w/o including my ip in the @ file?

Dec 7th, 2001 03:01
Brian Coogan, Mattias Wadman, Brandon Berry,

This would only be true if your tinydns servers aren't reachable 
through the normal chain of delegation from the root servers.  If this 
is true, it's normally because you are running an internal nameserver 
for your private namespace and you don't wish this to be reachable 
externally.  This scenario is called "split horizon" and is further 
discussed in the FAQTS question: "How do I implement split horizon DNS 
using djbdns?".
The brief answer is that you simply tell djbdns to consult your tinydns 
directly and not try to find it via the root servers.  You do this by 
adding a file containing the IP address of your tinydns server named 
after your internal domain to the root/servers directory, ie:
    echo 192.168.1.5 > /service/dnscache/root/servers/internal.dom
where internal.dom is the internal domain name and 192.168.1.5 is the 
IP of the tinydns server you want to use for internal.dom queries.
Including the tinydns address in the @ file will only work 1/12 or less 
of the time and will give rise to huge dns delays and instability.  
Don't do it :)