> ...and to make things a bit more confusing...an NS query to my > various servers for different domains always sends the first > response in the registrar order and then it randomizes after the > first request. So this means that the load should be heavier on the > primary name server as registered, but the busier the domain, the > more likely it would be cached, and the more likely the load would > be closer to 50:50, or at least that's my read on this.
The round-robin + response time algorithms should "kick off" with a call to randomize() the NS list. Seems you're still not considering the complexity of DNS recursor code. There's a lot happening in there; it doesn't just take any old set of responses at face value and hurry the next request out. A surprisingly large amount of sorting and prioritization can occur between one response and the next request. --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.
