Re: Help, I can´t make a delega tion :(

2009/5/29 Reyner Herrpinark Lugo <[email protected]>:
>
> I have already done that Todd, and I can only get answers if I make a query from the example.com's machine.
>
> With: "dig ns1.us.example.com @127.0.0.1" on the tip-server machine (10.7.20.3) I get the correct answer:

Here is how I see your system.  Please correct me if I'm wrong:

tip-server.example.com:  authoritative for example.com
ns1.us.example.com:  authoritative for us.example.com

> But Todd, this does not solve what I hope. I expected that queries to reach the delegated name server, for example, if within the zone us.example.com (in 10.7.20.2 server) I have:
>
> us.example.com |test |604800 |a |null |10.7.20.253 |
>
> When I type "dig test.us.example.com @127.0.0.1" on the tip-server machine (10.7.20.3) I expected something like this:
>
> ;; ANSWER SECTION:
> test.us.example.com.   604800   IN   A   10.7.20.253
>
> ;; AUTHORITY SECTION:
> us.example.com.   604800   IN   NS   ns1.us.example.com.

The data I gave you was only for the ns1.us.example.com server.  You
also have to configure the tip-server with the corresponding
information that it needs to send us.example.com queries to
ns1.us.example.com.  So here is what you have to do:

On tip-server.example.com:
NS record for example.com pointing to tip-server.example.com.
A record for tip-server.example.com.
NS record for us.example.com pointing to ns1.us.example.com.
A record for ns1.us.example.com.
A/CNAME/TXT records for *.example.com.

On ns1.us.example.com:
NS record for us.example.com pointing to ns1.us.example.com.
A record for ns1.us.example.com.
A/CNAME/TXT records for *.us.example.com.

With the above data, a query:
  dig @tip-server.example.com lugo.us.example.com
will result in tip-server replying with an referral to
ns1.us.example.com and the A record for that nameserver in the
ADDITIONAL section.  Then it's up to your resolver to chase that
referral.

I know it does seem strange that you have to put both NS and A records
for ns1.us.example.com in both tip-server and ns1, however, it's
required.  The NS record for us.example.com tells it that it should
look for a nameserver ns1.us.example.com and you must also give it the
A record because the hostname ns1.us.example.com is in the same root
domain (example.com).

If the nameserver for us.example.com was something else, for example
dns55.register.com, then you would not require that A record in either
zone because you're not authoritative for the register.com zone.

-- 
Regards...      Todd

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get