DNS w/o Internet

[Barry Margolin]

In article <3919BF7F.F6841834 at ix.netcom.com>,
Thomas Gagne  <tgagne at ix.netcom.com> wrote:
>I was reading in a BIND FAQ that if a DNS is not connected to the internet,
>some of the root problems can be eliminated by configuring DNS to be primary
>for parents.
>
>In other words, as I understand it:
>
>My intranet's domain is "int.strikeitrich.com".  The paper suggest I can
>configure the same DNS server as being primary for "strikeitrich.com" and
>"com".  Does that make sense to everyone?  Once this is done, will my named
>stop ARPing my intranet to death looking for the root servers?

No.  Unless the server is authoritative for the root domain, it wants to
contact a root server to update the list that it read from the hints file.
Don't bother making your server primary for strikitrich.com or com, just
make it primary for ".".

>Also, currently my named can return IP addresses for hostnames, but it seems
>unable to do the reverse.  Could that be related to the lack of root servers?
>
>My DHCP server is dynamically updating my DNS.  Inserting records into
>192.168.1 are successful but inserting the reverse records 1.168.192 are
>failing.  Again, could this be the problem of missing roots?

I don't think so.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.