This is what happens under AOL 9.1

[Rara Avis]

Do you get 208.100.11.68 when you ping www.tractorbynet.com?

Not that I'd question the technical support at AOL , but common sense would indicate the problem isn't at TBN's end or everyone would see what AOL users see.

Thanks Mike...

IT IS STILL HAPPENING BY NAME under both AOL9.1 and AOL Desktop...
BUT I can reach TractorByNet under both the above versions using 208.100.11.68

This would seem to indicate that AOL has a bad name table someplace on the east coast...

So I just patched 208.100.11.68 into my favorites and forwarded the material on to AOL...

Mark this as closed at this end...

 

[Reg]

I'm tired, not thinking very straight right now.
Something about DNS...?

ipconfig /flushdns

has been known to clean up some name/address resolution problems.

I'll try to come back to this in the morning - need sleep, like NOW !

 

[MikePA]

From ipconfig /displaydns

www.tractorbynet.com
----------------------------------------
Record Name . . . . . : www.tractorbynet.com
Record Type . . . . . : 5
Time To Live . . . . : 40317
Data Length . . . . . : 4
Section . . . . . . . : Answer
CNAME Record . . . . : tractorbynet.com

 

[Reg]

Thanks Mike...

IT IS STILL HAPPENING BY NAME under both AOL9.1 and AOL Desktop...
BUT I can reach TractorByNet under both the above versions using 208.100.11.68

This would seem to indicate that AOL has a bad name table someplace on the east coast...

So I just patched 208.100.11.68 into my favorites and forwarded the material on to AOL...

Mark this as closed at this end...

What I think I was thinking last night;

If it persists then it might be "stale" in the name translation cache.
I think that was why I suggested ipconfig /flushdns - - which works on wherever your DNS is (likely your ISP). It will in any case refresh at some point, depending on your level of activity & some params that your IPS sets.

Don't worry about it, it will go away, your ISP won't exactly "fix" anything.

 

[Rara Avis]

What I think I was thinking last night;

If it persists then it might be "stale" in the name translation cache.
I think that was why I suggested ipconfig /flushdns - - which works on wherever your DNS is (likely your ISP). It will in any case refresh at some point, depending on your level of activity & some params that your IPS sets.

Don't worry about it, it will go away, your ISP won't exactly "fix" anything.

Well...magically this morning everything is back to normal after a couple of days with NO JOY via the AOL...I did send them an email documenting everything last night...SO WHO KNOWS...

But I've filed the numbers away, JUST IN CASE this ever happens again...Thanks MIKE and everyone else on this crazy site...

 

[Ibrahim]

There was no Nameserver issue. This is unrelated to name servers.

The problem is that AOL or your AOL browser is cacheing content.

-Ibrahim