[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Moving DNS
- Subject: RE: [cobalt-users] Moving DNS
- From: Greg Hewitt-Long <cobaltusers@xxxxxxxxxxxxxxxxxxx>
- Date: Sun May 25 18:30:01 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
> > how do the gtld nameservers get updated?
>>
>
>Your registrar takes care of that when you update the IPs for the
>nameservers.
>
>
>> The output from dnsreport.com shows that the gtld nameservers
>> have a TTL of 172,800 seconds - ie, 48 hours - does that mean
>> I have to wait 48 hours for it to refresh? Is there a way to
>> speed this up?
>>
>
>If you change the TTL before on the old nameservers it should happen
>faster, but it really depends on a lot of ISPs that don't obey the TTL
>and have their own idea of what your TTL should be. I remember AOL would
>be fast when I moved and the old @Home was a week once.
I've had problems with local ISPs when we moved their clients' sites from one machine to another - we were able to email hostmaster@ with a CC to support@ and request that they drop their cached DNS records - I think it's just a case of removing a pri.domain.tld from their nameserver and that was enough to pickup the change.
Many ISPs run their own refresh - it saves a TON of traffic for large ISPs - but it is technically NOT correct imho.
regards
Greg
--
http://www.webyourbusiness.com/
Providers of E-Commerce Software &
Web Design Consultancy and Services.
PH: (970) 266-0195 FAX: (970) 266-0158