It depends on what you query. If you query one of the root servers,
even netsol.com's NS records always appear in order, but if you query a
server like ns1.netsol.com, it will round robin the order. It's the
root server's order and the querying server's handling that matter.
My understanding of DNS is that for a non-cached domain, it will first
to to the root server to find out which NS servers are authoritative and
the order is fixed when it comes back from the root servers and is
likely to be used that way unless the client is randomizing for some
reason. The client then goes directly to the first NS server listed and
requests the appropriate records, but most applications/systems, such as
Windows with some Web browser, will fail-over to the next NS in line if
the query times out, and the server that they are querying should also
fail over, or at least negatively cache the unresponsive server so that
it isn't repeatedly hit. I would imagine that failing over is
application dependant, but I haven't bothered to read the RFC's.
Matt
Dave Doherty wrote:
I've experienced it both ways. It seems that some registrars return
the DNS servers primary-first, but NetSol at least, in my experience,
returns a name server in random order.
And I think that the root servers follow the lead of the registrars, no?
-d
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
