In article <[EMAIL PROTECTED]>, "Luis Silva" <[EMAIL PROTECTED]> wrote:
> Ok, thanks a lot for the reply. > Lets pretend that the names in the RFC are still the ones used. If the > client queries the "a.isi.edu." name server asking for the A address of the > "c.isi.edu." server, the zone information from "isi.edu." must have this > address in the name's list, right? Yes. It's a pretty common mistake to leave these records out, and it results in intermittent failures. > Many Thanks > Best Regards, > Luis > > > On Mon, Sep 22, 2008 at 2:46 PM, Stephane Bortzmeyer <[EMAIL PROTECTED]>wrote: > > > On Mon, Sep 22, 2008 at 02:29:32PM +0100, > > Luis Silva <[EMAIL PROTECTED]> wrote > > a message of 15 lines which said: > > > > > I noticed that is it possible to name the Name Server without not > > > considering the name of the zone. > > > > Yes. > > > > > But, what happen if the name server is only authoritive for the > > > first zone? > > > > No problem and it is even a simpler case, since you do not have to > > publish glue. > > > > > what happen if a client contacts directly a name server from the > > > "isi.edu." zone with the query "A" "c.isi.edu.". This can happen > > > right? > > > > Yes, and there is no problem: > > > > % dig @ns.east.isi.edu A c.isi.edu. > > > > ; <<>> DiG 9.5.0-P2 <<>> @ns.east.isi.edu A c.isi.edu > > ; (1 server found) > > ;; global options: printcmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31441 > > ... > > > > (Names have changed since the RFC was published.) > > -- Barry Margolin, [EMAIL PROTECTED] Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group ***
