Cole Tuininga wrote:
On Mon, 2006-04-10 at 10:27 -0400, John Abreau wrote:
Cole Tuininga wrote:
I wasn't aware that AOL was screwing this up as well.
Last I was aware, AOL cached DNS entries for a minimum of two weeks, no
matter what the TTL.
However, I don't
see anything that can be done about their blatant disregard for the way
DNS is designed to work.
Saying "the hell with 'em" is probably your only realistic option.
Well, some folks take the approach that they will try to make sure
services remain forwarding for at least two weeks, to accommodate this.
As I try to remember to set TTL's to a low value for a while before
making changes, I usually say "to hell with 'em" and only support the
forwarding for a little longer than the TTL allows fo
If you're doing that for an enterprise, sure; but does GNHLUG have the
resources and spare machine to do that for the server migration?
--
John Abreau / Executive Director, Boston Linux & Unix
ICQ 28611923 / AIM abreauj / JABBER [EMAIL PROTECTED] / YAHOO abreauj
Email [EMAIL PROTECTED] / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
