Slow DNS Change


Recommended Posts

blame your ISP :o ;)

Again - there really seems to be a lack understanding how DNS works!!! A users ISP really has really nothing much to do with it - unless really screwed up, it does what its told. It will cache entries for the length of the TTL, so having a TTL of almost 8 hours just before you make the move to a new host - maybe not the best option.

;; ANSWER SECTION:

www.neowin.net. 28000 IN A 66.98.144.45

;; AUTHORITY SECTION:

neowin.net. 28000 IN NS ns1.rackshack.net.

neowin.net. 28000 IN NS ns2.rackshack.net.

28000 / 60 / 60 = 7.7777 hours

A few things I noticed in the change over - for one, there was the change that pointed name servers to nsX.theplanet.com - those servers were just pointing to the old rackshack servers. And those planet servers sucked all together - most of the time they would not even respond.

So even after the domain was updated to point to the new name servers, you were justing going to cache the old entry for another 8 hours.

I also caught some other name servers listed, before the move to the current zoneedit servers - that sure couldn't of helped.

Before I would blame anyone's ISP for the problem with the move - I would look long and hard at who planned the dns change. I am sorry - but it sure did not seem like a well planned out move.

In a nutshell - DNS should of been a minor blip on the move. It does seem the other server was online and ready before the move. So as the domain was pointed to the new name servers - your done. As the ttl expired - everyone would of looked to the new location.

In prep for the move - the ttl's on the rackshack servers should of been lowered before the move. They could of been taken down to the 1 minute level, or the smallest level rackshack was willing to use - the smaller the ttl, the higher the traffic.

Since the old rackshack servers still show valid for www.neowin.net - how about pointing them to the new address? Which could of been used to make the move - even before the domain updated to point to new name servers.

A move could of been made to the new servers, before the change to the domain was even active. As the move got close - keep lowering the TTL. If your sure you have dns up and running on the new servers. Do the cut - point the old servers at the new host, or even point them to the new nameservers, etc..

At most people will only come to the old host for the length of the TTL, which should of been a few minutes - not hours.

It sure seems like someone dropped the ball on the change over when it comes to DNS - so don't be telling users to blame their ISP. When there was clearly issues out of the their ISP's control that did NOT help in the cut over to the new servers.

Link to comment
Share on other sites

Before I would blame anyone's ISP for the problem with the move - I would look long and hard at who planned the dns change.  I am sorry - but it sure did not seem like a well planned out move.

...

It sure seems like someone dropped the ball on the change over when it comes to DNS - so don't be telling users to blame their ISP.  When there was clearly issues out of the their ISP's control that did NOT help in the cut over to the new servers.

Let's put Budman in charge of the next move :D

For those who care... I have unedited my hosts. file and it works properly now.

Link to comment
Share on other sites

and that folks, is how DNS works!  everyone give budman a round of applause.

ok..who actually read it? :laugh:

::bends over and moons budman::

: :laugh:

Dudes whats up with my Warning Level!? :blink:

40%!?

Someone wanna PM ME! :(

Have I been a bad boy!!! :unsure:

Link to comment
Share on other sites

ok..who actually read it? :laugh:

Which seems to be the MAJOR problem around here - if it's freaking longer than 3 words nobody reads it - which is most likely why the move went so bad. You got Billy telling Bobby how do something - and he reads the first 3 words and goes off and does something.

Then when asked what he did - you get back "I don't know" :)

Is it just me, or does the vast majority of neowin users seem to read and write at about a 3 grade level. Here I'll put what went wrong with the move in terms that people will read and understand.

"Neowin Screwed the POOCH"

But when people start asking quesitons - you get mods saying - "Blame your ISP". Which is BS, pure and simple.

Link to comment
Share on other sites

Oh Budman, chill out. Don't make me get the definition of a joke for you. I read your entire post. Thank you ever so much for explaining it all for me in the ever so patronizing way that you do.

Geezus christ, I was wrong apparently. Everyone makes mistakes.. except you I guess.

Link to comment
Share on other sites

Which seems to be the MAJOR problem around here - if it's freaking longer than 3 words nobody reads it - which is most likely why the move went so bad. You got Billy telling Bobby how do something - and he reads the first 3 words and goes off and does something.

I read, and now I know what to do whenever I move hosts. So thanks BudMan (Y)

Link to comment
Share on other sites

Geezus christ, I was wrong apparently. Everyone makes mistakes.. except you I guess.

No - I make my fair amount of mistakes, everyone does. But what I do not do - is go about giving bad information. If you did not know why there was issue with DNS. Maybe you should of looked into it vs telling people to blame their ISP.

More than likely there was more than a few calls to ISP's asking about why they can not get to neowin, etc..

And then when someone makes an attempt at explaining atleast what part of the problem was - you make jokes! So was neowin being offline for an extended period of time for most likely a HUGE portion of the userbase funny to you??

I am sure, quite a few people did not find it funny.

Link to comment
Share on other sites

My original comment "blame your ISP" was a joke as well. The :o ;) was an attempt to point out it was tongue in cheek. Ok maybe it was bad form given that I'm a mod and people may take me more seriously than intended. I'll admit to that.

Did I find it funny that I couldn't access neowin for a day? No. Did I care? No because it would be back up soon and theres always other things to do.

On a side note, you claim people don't read long posts. You know what stops me dead in my tracks most of the time from reading yours? You're incapable of making a post that isn't condescending. Who wants to read through tripe? Perhaps if you employed a different angle at trying to inform people of what you know instead of making them feel stupid is all that is needed.

Link to comment
Share on other sites

I'm not normally one to back a mod ;);) but Spyder is right, he gave information to the best of his knowledge (Blame ISP) and then you jump down his throat with "go about giving bad information" instead of correcting him politely.

Link to comment
Share on other sites

I appreciate it ffx, but I don't want this to turn into even more of an argument.. unfortunately I contributed to it enough. I think budman and I both explained where we're coming from and that's that.

The DNS has updated and everyone is happy now, so lets call this thread a day, shall we?

closed

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.