> It's the root server's order and the querying server's handling that > matter.
Absolutely not. It is ONLY the querying recursor's handling that matters, for it is that recursor that is talking to the authoritative NSs, and it makes a more "locally intelligent" choice than you think. > ... the order is fixed when it comes back from the root servers and > is likely to be used that way... Wrong. Google "order multiple nameservers," geez. > 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. You're mixing up client resolver "primary/secondary DNS" and recursor "primary/secondary NS" -- one of which exists, the other doesn't. --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. e-mail: [EMAIL PROTECTED] SpamAssassin plugs into Declude! http://www.imprimia.com/products/software/freeutils/SPAMC32/download/release/ Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases! http://www.imprimia.com/products/software/freeutils/exchange2aliases/download/release/ http://www.imprimia.com/products/software/freeutils/ldap2aliases/download/release/ --- 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.
