Skip to main content

Replies sorted oldest to newest

Hey guys.  I just found this out yesterday.  My hosting service made changes to their public IP space.  Somehow I had to make changes to my "nameserver", not them.  If you don't know what this means, don't feel bad, I don't either. They did not automatically take care of this because of something about the law says I have to make the change.  Well I tried and failed and as no surprise their customer support line had "unusually high volume".  This apparently has happened to many of their customers.  No telling when I will get this resolved, but hopefully by tomorrow.  Thanks for your patience. 

 

By the way I highly recommend NOT using Homestead to host a website.  Besides this kind of stuff, it is buggy, and expensive compared to others. 

Originally Posted by Rich Battista:

Hey guys.  I just found this out yesterday.  My hosting service made changes to their public IP space.  Somehow I had to make changes to my "nameserver", not them.  If you don't know what this means, don't feel bad, I don't either. They did not automatically take care of this because of something about the law says I have to make the change.  Well I tried and failed and as no surprise their customer support line had "unusually high volume".  This apparently has happened to many of their customers.  No telling when I will get this resolved, but hopefully by tomorrow.  Thanks for your patience. 

 

By the way I highly recommend NOT using Homestead to host a website.  Besides this kind of stuff, it is buggy, and expensive compared to others. 

 

Rich,

 

Had a similar problem on a company website I maintained several years ago.  Yep, if public IP addresses for servers get changed, that can hose things up pretty good, including DNS (domain name service) which is what happened to you.

 

Name servers handle incoming domain name requests (like a website address) and those name servers (usually there's two of them for redundancy) sends responses back with the corresponding IP addresses so that the request for the domain (like when you type or bring up www.ogauguerr.com on your browser) can be resolved and your web browser delivers the page to you.

 

Sometimes hosting services rely on other's name server services.  That's typically why they can't implement the change.  While I've done these myself in the past,  I'll admit that I don't recall any law requiring the customer to request the change.

 

Don't be too hard on them initially, when something major like a public IP address change is done it's going to cause a lot of disruption and providers do tend to get hit hard with lots of calls.  What would be unacceptable, however, is them not being proactive and informing customers of this impending change so one can prepare for it.

 

The other sucky thing is that as soon as something like this happens, popular search engines like Google will quickly drop the website off the top search hit results, and may take a couple of weeks before it will be restored.

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×
×