To:
Bruce Campbell <bruce.campbell@apnic.net>, dnsop@cafax.se
From:
Nathan Jones <nathanj@optimo.com.au>
Date:
Wed, 9 May 2001 17:39:49 +1000
In-Reply-To:
<Pine.BSF.4.21.0105091625580.43413-100000@julubu.staff.apnic.net>; from Bruce Campbell on Wed, May 09, 2001 at 04:33:11PM +1000
Sender:
owner-dnsop@cafax.se
Subject:
Re: Should a nameserver know about itself?
On Wed, May 09, 2001 at 04:33:11PM +1000, Bruce Campbell wrote: >Is the assumption that a nameserver should have information about itself >correct? I'm not aware of such a requirement, even though it sounds like a good thing for a host to know. Here's a scenario that I think is valid, in which a nameserver wouldn't know about itself: Foo use ns1 and ns2 for their own domain, but use dnshost1 and dnshost2 for their customers. foo.example. IN NS ns1.foo.example. foo.example. IN NS ns2.foo.example. ns1.foo.example. IN A 192.168.1.1 ns2.foo.example. IN A 192.168.1.2 dnshost1.foo.example. IN A 192.168.2.3 dnshost2.foo.example. IN A 192.168.2.4 Bar is a customer of Foo: bar.example. IN NS dnshost1.foo.example. bar.example. IN NS dnshost2.foo.example. dnshost1 and dnshost2 are authoritative only nameservers (no recursion). When a delegation request is lodged for bar.example., your script queries dnshost1 for it's own A record and gets a referral to either the root servers or the example. servers, since it does not host foo.example. and does not offer recursive resolution. -- nathanj