ISP still not resolving to DNF host

[parabola]

Anyone else still waiting for an ISP to resolve to the new host?

I'm in Ontario, Canada and can only log-in via the IP address posted.

[Adam Dicker]

I am on rogers in Toronto and I am resolving fine.

-=DCG=-

[parasane]

Anyone else still waiting for an ISP to resolve to the new host?

I'm in Ontario, Canada and can only log-in via the IP address posted.

I'm on the Buffalo, New York, line of Adelphia, located in Olyphant, Pennsylvania, and it's not resolving yet for me, either. Yet if I run off of my own nameservers, which I have cacheing in Houston, Texas, and here in my office in Olyphant, it works just fine. I guess that's Adelphia for ya'.

[NETGEEK]

I'm on comcast in Chicago and still have to pull by IP as well.

[TravelFastpitch]

I am also on comcast and have been online at dnforum.com for 3 hours now.

[parabola]

Sympatico is still not pulling for me.

[cyphix]

Internode in Australia & been resolved now for about 10 hours or so.

[NETGEEK]

I am also on comcast and have been online at dnforum.com for 3 hours now.

That's cause you are special Andy

[TravelFastpitch]

That's cause you are special Andy

You must be using sharing the same comcast line with the United Center. I hear there is a lack of performance over there.

[NETGEEK]

You must be using sharing the same comcast line with the United Center. I hear there is a lack of performance over there.

LOL

[NameTower]

I am on rogers in Toronto and I am resolving fine.

-=DCG=-

Same.

[parabola]

Sympatico, Niagara Region -- still no resolution.

[Domagon]

Next time DNForum moves servers, they should do what the pros do and drop the TTL on the old IP down to some low value, say 5 minutes or less, a few days prior to moving to a new IP to minimize caching issues.

If name servers change too, then one should either drop the IP out and flush the zone, or depending on the setup, simply put the new IP in there too for about a week or so.

Ron

[RMF]

Works fine on the westcoast of british columbia

RMF

[biggedon]

I'm on comcast in Chicago and still have to pull by IP as well.

In "chi-town" as well!

get it at home .......but via "ip" at work. :(

[Mr Webname]

get it at home .......but via "ip" at work. :(

Yet another reason not to go to work! :-D

[ToastyX]

I don't understand why people keep mentioning their location every time there's a DNS issue because location has nothing to do with it. It's most likely a caching issue.

Windows maintains its own DNS cache, so if you use Windows, try opening a command prompt and enter the following command:

ipconfig /flushdns

If that doesn't help, there's only two things you can do:

1. Use a different DNS server
2. Wait it out

It has nothing to do with your location, and your ISP only matters if you're using their DNS servers.

[ToastyX]

Also, make sure you don't have dnforum.com in your hosts file with the old IP. It shouldn't be there anyway unless you put it in there and forgot about it.

[Nameable]

Comcast is a pain in my ass. Their caching nameservers give inconsistent results for 'dig www.dnforum.com' -- Sometimes I get .10 with a sensible TTL (like 86xxx or thereabouts). Then I sometimes get .186 with a ttl like 65xxx, but sometimes I can see .186 with a TTL of or near 86400, which just shouldn't happen unless your authoritative servers are giving out bad data (they're not, I checked @dns1-3).

I've been watching their dns since the changeover and it seems like their caches don't obey TTLs like they should, or the data is cascading down from other servers that I can't see.

[Domagon]

Fault isn't with Comcast, but DNForum for not transitioning the name servers / IP ... see my reply several message up in the thread.

What's likely happening is that one or more of Comcast's name servers has likely cached the old name servers with a TTL of 2 days...many webhosts use 2 days for their name servers - also some ISPs ignore TTLs for name servers for various reasons.

And since DNForum's old name servers still have the old IP in them, that's what's going to be cached - and thus even if the TTL on the IP expires, Comcast will refresh it again with a 86400 TTL.

Some folks will likely continue to have problems getting here for many more days. Again, this is a lesson for any website changing name servers - at minimum, update the old ones with the new IP too! That alone can make all the difference.

Ron