Host names

[buzz]

The automated messages I get from the new boards use herogames. com in their URLs, while to board actually uses
herogame.dans.cust.servlets.net. CLicking links is, ergo, non-functional. I figure Ben is working on this, but I thought I'd mention it.

[archermoo]

Yeah, they're just waiting for the new DNS to propagate. Which can take an annoyingly long time...

[Simon]

The DNS change has gone through. At least on my side.

What this means is that all the pieces are in place, it's just up to everyone's individual DNS to update before you'll be accessing the new site through the proper URI (herogames.com). You'll know you're on the right site when you go to http://www.herogames.com and have a login button on the left-hand nav-bar ;)

[archermoo]

Cool, seems to have propagated to my ISPs servers as well...

[Edsel]

Originally posted by dsimon
The DNS change has gone through. At least on my side.

What this means is that all the pieces are in place, it's just up to everyone's individual DNS to update before you'll be accessing the new site through the proper URI (herogames.com). You'll know you're on the right site when you go to http://www.herogames.com and have a login button on the left-hand nav-bar ;)

Doesn't seem to have gone through to my ISP yet (nor the server at work either). It will be interesting to see how long it takes.

[Koshka]

Originally posted by dsimon
You'll know you're on the right site when you go to http://www.herogames.com and have a login button on the left-hand nav-bar ;)

:: checking site :: No login button yet. Doing mouseovers on the navbar links gives me a mix of "herogames.com" and "herogame.dans.cust.servlets.net" . I assume once the DNS goes through all those will be "herogames.com" as well?

[TechnoViking]

I had the nav bar on Tuesday night, but now it is gone. My ISP (speakeasy.net) does weird stuff like this. :)

Mike

[Simon]

Mike - I'm with speakeasy as well (GREAT service!) and have been seeing the same thing....it keeps bouncing between the old server and the new.

Sigh.

Soon ;)

[Ben Seeman]

Okay, VeriSign has 4 hours to make everything right and then I'm gonna rain hellfire down upon them. Grrrrrr.

Why is it so difficult for these companies to do things that they've been doing for years? When you call them they act like you have no idea what you're talking about.

Grrrrrr.

[buzz]

Originally posted by Ben Seeman
Okay, VeriSign has 4 hours to make everything right and then I'm gonna rain hellfire down upon them.

DANGER! DANGER BEN SEEMAN! VERISIGN! DANGER!

Seriously, VeriSign/Network Solutions is ass. Premium prices for sub-standard service. I trasnferred a bunch of domains I own over to GoDaddy.com in the past year or so and have had no hassles. They're also about $15-$20 cheaper.

[TechnoViking]

Originally posted by dsimon
Mike - I'm with speakeasy as well (GREAT service!) and have been seeing the same thing....it keeps bouncing between the old server and the new.


It should not complain, no one else is willing to run DSL or cable modem half way up a mountiain:).

Mike

[MisterVimes]

Originally posted by Ben Seeman
Okay, VeriSign has 4 hours to make everything right and then I'm gonna rain hellfire down upon them. Grrrrrr.

Why is it so difficult for these companies to do things that they've been doing for years? When you call them they act like you have no idea what you're talking about.

Grrrrrr.

It used to take a max of 48 hours.
Now... at work I am on our Network (so I have no idea what's up with that)
At home I'm on AT&T Cable and it still doesn't resolve.

[Ben Seeman]

Well I've just had our a second "Escalation Ticket" submitted to the VeriSign technical staff...

Why am I not hopeful? :|

[MisterVimes]

Originally posted by Ben Seeman
Well I've just had our a second "Escalation Ticket" submitted to the VeriSign technical staff...

Why am I not hopeful? :|

Because NetSol is now in the clutches of the technically inept Verisign, who is now run by Sales people who are as technical as a Thimble.

[Balok]

FYI, it still hasn't propagated out here (to the east coast). I don't know if that's Network Solutions, or I just need to wait longer -- just figured I'd let you know in case the information was in some way helpful.

[buzz]

Originally posted by Balok
FYI, it still hasn't propagated out here (to the east coast). I don't know if that's Network Solutions, or I just need to wait longer -- just figured I'd let you know in case the information was in some way helpful.

Ditto here in Chicago.

I'm tellin' ya: GoDaddy.com. None of this waiting a week for DNS to propagate. :cool:

[Nato]

Hmmm. I had the same problem as Dan Simon and someone else. I was getting the new 'Login' button on the left and the boards were actually on herogames.com. Now it's back to before. Wierd. I use Verizon as my ISP.

[MisterVimes]

Originally posted by buzz
Ditto here in Chicago.

I'm tellin' ya: GoDaddy.com. None of this waiting a week for DNS to propagate. :cool:

And Domain Names for $8.95!!!!!!!!!!!!!!!!!!!!

[Jerry A!]

Originally posted by buzz
Ditto here in Chicago.

I'm tellin' ya: GoDaddy.com. None of this waiting a week for DNS to propagate. :cool:

Actually, your registrar has very little to do with when someone will pick up your DNS changes.

It's a function of how correctly configured your local ISP's DNS caching servers are setup.

Many don't respect TTLs b/c they're trying to avoid massive updates all the time and trying to avoid having transient errors visible to the end-users ("Well why is it working now, when it wasn't working 15 minutes ago? What do you mean you don't control myfavoritewebsite.com, you are the internet after all...")

[buzz]

Originally posted by Jerry A!
Actually, your registrar has very little to do with when someone will pick up your DNS changes.

I know, I used to work for an ISP. :)

But it seems evident that some registrars drag their feet, or have arcane proceedures in place, and some don't. Unlike Network Solutions, GoDaddy (and MyDomains.com, for that matter) gets out of my way and lets *me* manage my domains.

Barring problems or people with cache servers, DNS should take 24-48 hours to propagate, iirc. HG has been waiting since, what, Monday? Tuesday?

And I'm not even using a podunk ISP. I'm at work, and we have T1 leased directly from Sprint.

[MisterVimes]

Originally posted by buzz
I know, I used to work for an ISP. :)

But it seems evident that some registrars drag their feet, or have arcane proceedures in place, and some don't. Unlike Network Solutions, GoDaddy (and MyDomains.com, for that matter) gets out of my way and lets *me* manage my domains.

Barring problems or people with cache servers, DNS should take 24-48 hours to propagate, iirc. HG has been waiting since, what, Monday? Tuesday?

And I'm not even using a podunk ISP. I'm at work, and we have T1 leased directly from Sprint.

Beat me to it... We have a T1 from Qwest and I'm experiencing the same problems. For this to be so universal, the only common factor is the Registrar not being timely...

In the days I worked for Bellsouth.Net and Interland (web hosting company), anything longer than 24 hours on global propogation was unheard of

[Jerry A!]

Originally posted by buzz
I know, I used to work for an ISP. :)

But it seems evident that some registrars drag their feet, or have arcane proceedures in place, and some don't. Unlike Network Solutions, GoDaddy (and MyDomains.com, for that matter) gets out of my way and lets *me* manage my domains.

Barring problems or people with cache servers, DNS should take 24-48 hours to propagate, iirc. HG has been waiting since, what, Monday? Tuesday?

And I'm not even using a podunk ISP. I'm at work, and we have T1 leased directly from Sprint.

But this isn't currently an issue with the registrar's turn-around for a request. The registrar's servers will never be touched unless they also changed nameserver records. If that's the case, then all bet's are off anyway.

Any registrar can show you the changes that you make immediately. However, those changes still need to get to the root servers to be propagated to the Internet-at-large. This is a batch job that must be submitted to NetSol and is applied at roughly 0500 and 1700. Thus it doesn't really matter which registrar you're working with (for this type of change).

After that, once the whois records are updated, then the new DNS information still has to propagate.

So...

Assuming that the original TTL was 24hrs for www.herogames.com, then yes, for all well behaving servers things should have propagated within 48 hours.

However, using your example of Sprint (which I know a good deal about since they provision our service), I can tell you that they don't respect TTLs. Depending on the segment you're on, they'll expire and retry only once every day or every other day.

As another point of reference, I run my own caching nameserver that queries the root servers instead of my ISP's. I have the correct values. Other people on Comcast's network are still pulling the old records. And the local region caching servers pull from their master caches. So there's no guarantee that when the record expires they'll pull the new one.

Then there are those servers who only expire a record once it goes beyond the max post-TTL life of one week. AOL used to be notorious for this.

However, a good rule of thumb is to always give yourself a week to deal with caches that will only cycle an a weekly basis (of which AOL used to be notorious for).

And beyond that, dealing with bad infrastructure in places around the world, reaslistically you can expect approximately 3 weeks for changes to hit every corner of the globe (though those last 2 wks only encompass something like 1-2% and in really messed up areas).

[Jerry A!]

Originally posted by MisterVimes
Beat me to it... We have a T1 from Qwest and I'm experiencing the same problems. For this to be so universal, the only common factor is the Registrar not being timely...

The registrar was timely. That's why the root servers have had the records since yesterday.


In the days I worked for Bellsouth.Net and Interland (web hosting company), anything longer than 24 hours on global propogation was unheard of

That's back before the days of sprouting ISPs that were poorly designed and then bought out by larger ISP conglomerates who never corrected the infrastructure issuse.

Also, as I said earlier. In the modern era, you need to cache heavily in order to avoid the support calls from all the twinks out there who can't comprehend transient errors with an AS.

Sad but true. As with anything else, once you commoditize anything to the point of general accessibility, it becomes crap. :D

[MisterVimes]

Originally posted by Jerry A!
Sad but true. As with anything else, once you commoditize anything to the point of general accessibility, it becomes crap. :D

Ain't that the truth... lowest common denominator

[Jerry A!]

Get in contact with servlets.net and ask them what the hell you're paying them for!

Your issues aren't propagation issues. ns1.servlets.net and ns2.servlets.net (your registered nameservers) aren't providing the same information.

The worst part is that ns2.servlets.net which is providing the old/bogus information has a TTL of 86400 so it'll hose anyone that queries it for an entire day.

Even worse, they're also serving out NS records pointing to ns1.dn.net and ns2.dn.net. Oh, the freakin' horror of lame delegations.

My guess is that they can't figure out how to make their own servers authoritative, and thus ns2 isn't getting a zone transfer from ns1.

Sorry I didn't catch this earlier.

[Simon]

Jerry -

First off, thanks for the info! I never thought to check that.

I've been with Servlets.net for about 7 years now and can honestly say that they are an exceptionally conscientious host. I've certainly run into problems on occasion....I don't think there's a server in the world that won't have any issues.....but they've always been very prompt (and honest) in responding to them.

Here's what they sent me when I forwarded your post to them:
<blockquote>
Our secondary DNS services are temporarily hosted on a DNS server provided by one of our upstream providers until we complete our network infrastructure move and updates. We
asked them to correct the issue on their DNS servers and just now heard back that the changes have been completed.

As this posting mentions, it might take a little time for anyone who retrieved bad info from ns2 to update.
</blockquote>

They're going to continue to keep an eye on the situation and will make sure that it gets resolved.

The network infrastructure move and updates that they mention is a rather large-scale upgrade in their hosting facilities. They're pulling a lot of stuff "in-house" and will be increasing their capabilities by quite a bit as they get settled into their new digs.

Anyway, hopefully this will help us get past this issue.....the transfer onto the new server has been extremely smooth except for this.....it will be very good to get this taken care of.

Thanks again!