 |  |
Re: IP Renumbering Nightmare Coming....
From: Mia''s Virtual Post Office
Date: Friday, June 13, 2003
Time: 2:03:11 pm
On Friday, June 13, 2003, at 03:38 PM, John May wrote:
> Actually, I'm still looking for an answer to the following 2 questions:
>
> - Is there any way to force a slave server to refresh to the master
> server? If so, then I don't see the need to change the Refresh, Retry
> and Expire settings on the zone records, which is good because it's
> one less thing to have to write an Applescript for (and I don't have
> one already).
I'm really not sure..
>
> - "TTL of SOA" - should this be set to a small value as well? Or do
> the TTLs of the individual A records override it? If it needs to be
> set, can you provide an example Applescript to do such?
>
>
Given the lack of brain power and obvious mental problems in AOL,
TimeWarner land among others, a TTL is now MOOT. No one seems to
adhere to RFCs or standards anymore.
Sure, set the TTL to like 300, ie., 5 minutes. It really does not make
much of a difference when there are morons out there caching DNS for
72+ hours. I cannot for one minute believe that there is enough of a
load on AOL's servers or RR's servers that they have to cache DNS and
subvert TTL's. The TTL of the Authoritative server should be respected
without questions, ALWAYS, PERIOD!
I could run a root server off a dual proc pentium and never miss a
beat. The root servers themselves, while overbuilt, are designed such
that two of them could run the whole internet. And little
AOL/TimeWarner seem to think that they are some how special, and do not
need to respect TTL's.
We have 6, yes SIX name servers! Why? To distribute load and for
redundancy. Load is the least of my worries. We have two for our main
DNS servers, used for colo/hosting queries. Two are used for our
dialup and wireless/T1 customers. Finally the last two are purely
internal for testing, and our own internal queries, etc. I could
probably run the whole internet off of two of them. So this load issue
with AOL and others is pure bull.
Ok, enough of my rant. TTL's are worthless, plain and simple.
The best way to change IP addresses is by setting up a redirect on a
linux/OSX box. Keep both your IP ranges/connections active. Switch to
the new IP addresses and redirect all POP/SMTP/UDP/HTTP, etc., from the
old IP to the new one. Since the host header is passed on, your server
(with the new IP) will know what to do with the incoming packets.
Now do a dump of the logs on that nix box. You will note that even
with your 5 minute TTL, incoming requests will be banging away for
hours, days, and up to a week or more!!!
We just moved a web hosting service with 4 servers over to a new IP
range today. No down time BTW. And even though their TTL's are 300,
we are seeing tens of thousands of requests from those 24.x.x.x IP
ranges from that crummy cable service..
Its a new game out there. I just want others to be aware that a TTL is
now useless. You are better off either binding the old/new IP's to
each box, or using various host/IP re-directs in conjunction with your
provider, or on your own.
You cannot expect to just turn off one pipe and turn the other on. If
you want to stay up, you cannot rely on a TTL anymore, or DNS. It just
is not gonna work.
Regards,
Jeremy Anthony Kinsey
e-mail: jer@mia.net
________________________________________________________
Bella Mia, Inc. www.mia.net
401 Host Drive www.dslone.com
Lake Geneva, WI. 53147 www.hostdrive.com
Phone: (262)248-6759 www.bella-mia.com
Fax: (262)248-6959 www.thednsplace.com
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696