Where is the New Website? I Thought it was Up Now.
We run into this one from time to time. There could be a few things going on. This article will cover some things to change on your end and some more troubleshooting that can be done.
Your Web Browser
Your browser may have the old website cached. You visit it often, so you need to clear your cache. You can do this in your browser settings or else try a force refresh (the shift key + the reload button). Another good idea is to just try restarting your web browser. Also, restarting your computer could take care of a bunch of issues that we’re discussing here – so that’s also worth a try.
Since you visit your website often, your computer may think that your website is on your old hosting account still (if the new website is now hosted by us or else hosted somewhere different). The cure for this is just time – you have to wait for DNS updates to happen. You could try restarting your computer – that sometimes helps. You could view the website on another device or computer that hasn’t accessed it for a while. You could also go to another network (a good excuse to run to Starbucks) and try it there – and this is also a test that can be done for the next thing we’ll discuss… your internal network.
Another option is to change your hosts file – but the only drawback here is that you might forget to change it back later and your website might move later on and you might forget that you’ve done this.
Your Internal Network
We’ll try not to get too technical (at first)… when your internal network at your office is set up, you often have to name it and very often the name for it is the domain name of your company. When this is done, your office computer network thinks the website is at the old address. This, then, has to be changed by your IT staff. Try another network and see what happens – so try a mobile device that uses your cell phone network or run down to Starbucks or even hop on another wireless/wi-fi network that might be available in the area.
Let’s Get Technical
And now the technical part (for your IT staff)… you have an internal DNS server running. In it, there are settings that say where the website is. These are the “A” record settings for the domain name. They need to be edited to point to the new IP address for the website so that your staff can see the new website on our servers now. Please contact us for the correct IP address to use.
Make sure you change both “A” records if you have two – meaning, one for the domain name with the “www” (which is actually a sub-domain) and one for the domain name without the “www” in it. If you have a CNAME record for the “www” version of the domain name, then you only have to make one change instead of two (and this is the better way to have DNS set up).
Once you make the changes, you may need to restart the DNS service for the changes to take effect. Make sure you do that.
If you still cannot see the new website from your internal network, then let’s review what to do. First, please re-read this entire page and make sure you’ve tried everything here. Second, look for another DNS server on your network or find out which DNS servers everybody is using and make sure those are all updated. Third, see if you can flush DNS internally (or restart the entire server/servers that’s controlling DNS). Fourth, use your network tools. Do an “nslookup” or “dig” internally and see what’s going on. I’ve even seen networks where the company domain name was hard-coded into each computers “hosts” file (very sloppy but it works… sort of).
Still Not Working?
Well, if from outside your network the website can be seen fine, then we’ve done our part. If the problem is only internally, then that’s your issue. We want to help but we’re not on-site IT people and we do not know the intricate ins and outs of your private network. This article will probably help you take care of 95% of the possible issues. If it still does not work, then something else is wrong. Do some searches on Google to find out what’s wrong or else get some more help diagnosing problems on your internal network. Good luck!