> So it wouldn't be perfect, but it would probably work decently as a
> fail-over.
Considering that there's no other way other than short TTLs to do
geographic load-balancing w/failover -- even mega-hitting GLB hardware
has a rather explicit reliance on the TTLs it gives out based on
r
> 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.
The registrars aren't returning anything to non-authoritative
recursors, the roots are. And th
> This actually happened to me recently: The potential customer, who
> is now hosting with some $10/month outfit, thinks that $50/month is
> about all he can muster for a redundant solution. And you have to
> agree with him, sort of. A 5X increase in his hosting bill seems
> like an awfu
> Maybe I'm missing something, but if you query one of the root
> servers for a domain's NS servers, they are always returned in the
> order that they are listed in your domain name registration.
"Registrar order" is not observed by the recursors querying the
authoritative namese
> I only raise the issues about primary and secondary because all my
> domains have dns.skywaves.net as the primary. That is a deicated
> name server on a DS3, and it is never remotely overloaded. But
> dns.skywaves.com, on a separate line at home, gets an awful lot of
> inquiries.
Y
> 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.
> ..
> I think the trick may be whether or not the DNS server that handles
> the client requests round-robins the cache. It appears that Windows
> 2003 DNS does do this, and BIND also appears to do this based on
> tests that I just did.
All modern recursors use an intelligent response-time + roun
> ...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
Hi Sandy -
And that answers the question I just posed to Matt regarding my two name
servers.
Thanks.
-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 fo
For example, database-backed sites whose database can be open for
writing at only one site are a *helluva* lot harder to balance.
You're right about that. There is some interactivity on the site, but it all
results in emails to the office, so no db sync'ing issues here.
-d
---
This
Another option to consider ... www.ultradns.com has a service that does
this. I've never priced it, so it may be pricey.
Rob
---
[This E-mail scanned for viruses by Declude Virus]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTE
11 matches
Mail list logo
