delegate top level domain

[Barry Margolin]

In article <9vagh6$212 at pub3.rc.vix.com>,
Francisco Sánchez  <f.a.sanchez at terra.es> wrote:
>
>Hello
>
>I am engaged in creating a internal zone for a group of computers.  This 
>zone is "company".  Then each machine will have a name such as 
>"machine.company".
>
>No problem for this.  I deal with "company" as if it were "com" or "net", 
>that is, the top level domain.
>
>The problem comes when I want a second dns server, not the one where the 
>"company" zone is, to resolve these private domains.
>
>I have created a recod at this other dns server with the following:
>
>---
>.                               IN      NS      DNS.MYCOMPANY.COM
>DNS.MYCOMPANY.COM       IN      A       123.123.123.123
>---

That doesn't say that your server is hosting the "company" domain, it
claims that your server is a root server.  Unless your server really *is* a
root server, this won't work.

>Note that DNS.MYCOMPANY.COM is a legal internet domain and correctly 
>resolves to the right IP for the dns server.
>
>Then in the named.conf file the following entry:
>
>---
>zone "company" {
>        type master;
>        file "named.company";
>};
>---

Why are you configuring the second dns server as a master for "company" if
you want it to query your server?  Why don't you configure it as a slave,
so that it will pull the zone over from your server?  Or as a forwarder:

zone "company" {
  type forward;
  forwarders { <address of your server>; };
};

>This is supposed to be the same as the internic dns records for, say, the 
>"com" top level domain.  How do they do it?

They operate the root servers, which contain delegation records for the
TLDs.  You don't have a root server, so you're different.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, 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.