|
|
 |  |
Re: still having problemsFrom: Men & Mice Support Date: Friday, October 27, 2000
Time: 12:29:35 pmIt's still there. When did you make the request?
Here's the usual order of events:
1. Request is made. Change is put into the queue.
2. At the next update, a.root-servers.net gets the change. Updates
occur twice a day.
3. Over time (within a few hours), the other servers authoritative
for com get the change from a.root-servers.net.
4. The record stays in the caches of some resolvers for up to 2 days
(according to the rules). For those resolvers that don't follow the
rules (e.g. AOL), the record might stay in cache far longer.
All in all, give it 3 days for such changes to take effect for most
of the world. The rest of the world, those using non-compliant
resolvers, might take weeks.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
At 9:58 AM -0500 10/27/00, Albert Rodriguez wrote:
>hey chris,
>
>can you run this test again? i had network solutions delete that i
>record. just wanting to double check.
>domain is masterpix.com.
>
>thanks.
>albert :-)
>
>Men & Mice Support wrote:
>
>> At 12:17 PM -0500 10/26/00, Albert Rodriguez wrote:
>> >hello folks,
>> >
>> >i'm still getting call that people can't reach my site via www.
>> >can someone look this over? the domain is masterpix.com
>>
>> The problem is that www.masterpix.com is a registered host, meaning
>> that it's listed in the com domain.
>>
>> From f.gtld-servers.net:
>> www.masterpix.com. A 216.60.90.141
>> masterpix.com. NS ns1.masterpix.com.
>> masterpix.com. NS ns2.masterpix.com.
>>
>> To fix this, you'll have to go through Network Solutions. Start here:
>> http://networksolutions.com/cgi-bin/makechanges/itts/host
>> --
>> ____________________________________________________________________
>> Chris Buxton Men & Mice
>> cbuxton@menandmice.com We Make DNS Easy!
|

Return to Digital Point Solutions' Home Page |