<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [registrars] WG: [council] Fast Flux DNS
- To: "'Margie Milam'" <Margie.Milam@xxxxxxxxxxxxxxx>, "'Thomas Keller'" <tom@xxxxxxxx>, "'Ross Rader'" <ross@xxxxxxxxxx>
- Subject: RE: [registrars] WG: [council] Fast Flux DNS
- From: "John Berryhill" <john@xxxxxxxxxxxxxxxxx>
- Date: Wed, 5 Mar 2008 23:54:25 -0500
- Cc: <registrars@xxxxxxxxxxxxxx>
- In-reply-to: <02D96C107E1B2445B9CD5065309187C32CCC6F@boiexch1.mm-ads.com>
- List-id: registrars@xxxxxxxxxxxxxx
- Organization: John Berryhill, Ph.d., Esq.
- References: <012401c87d44$739bfd30$fa0d11ac@1und1.domain> <02D96C107E1B2445B9CD5065309187C32CCC6F@boiexch1.mm-ads.com>
- Reply-to: <john@xxxxxxxxxxxxxxxxx>
- Sender: owner-registrars@xxxxxxxxxxxxxx
- Thread-index: Ach6FnkeWiLEoDhKStWR8KJQoKBigwDLXrFgAHMbz9AADMf8gA==
> At MarkMonitor, we generally don't see customers asking
> for multiple DNS updates per day,
How would you even know that?
At your end, for EXAMPLE.COM, all you are going to see is:
NS1.BIGCORP.COM
NS2.BIGCORP.COM
You have, as a registrar, ABSOLUTELY NO WAY OF KNOWING, how often the DNS is
being updated for EXAMPLE.COM. The DNS records for EXAMPLE.COM are not even
on your network. You are performing continuous AXFR's on your customer's
nameservers and watching their DNS? Why? Do your customers know this?
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|