Externally hosted website not showing on internal network

[rchaiguy]

So we just moved our website to Bluehost. We had previously been hosting it on our Apple servers but wanted to get them off.

Everything went smoothly in the move but I have a couple snags. First off I can see our temporary under construction page http://www.flextechutah.com only when I am outside our local network. When I am on the local network our old, internally hosted site, shows up not the new one.

My thinking is of course, this is because Apache is still running. So I shut off the web server services on all of our Lion servers. Tried to load the url again, and it still goes to the old page OR it shows a 404 page not found (of course because the web server is now off).

What am I doing wrong here? I can't make changes to the new site until I can load it via a local browser.

I will add that we still need web serving services because our Filemaker server is spiting out PHP generated slugs for our art department. Other than that, we don't need Apache running. Is their going to be a conflict?

Thoughts?

 

[MisterMe]

Ever heard of DNS? It means Domain Name Service. This is the protocol that translates the domain names into IP addresses. This is done by a network of computers known as Domain Name Servers. When new Internet servers go online, it often takes several minutes for the Domain Name Server network to propagate the name of the new domain to all DNS servers. When the DNS network has your new web server in its database, everyone will be able to access it.

 

[rchaiguy]

Yeah I am familiar with DNS

I didn't think this was a propagation issue simply because everyone external to us already sees the new page. I could wait another 48 hours to see if this is really the case. If it isn't then I will post back here.

 

[psingh01]

A local DNS server rerouting traffic to the old internal site?

 

[Les Kern]

A local DNS server rerouting traffic to the old internal site?

gots to be

 

[rchaiguy]

So if it is DNS rerouting how would I tell which one it is?

Here is the other issue, for our PHP-generated slugs and online proofs we still need to use the internal web server. If I nuke the DNS record that is rerouting traffic to the internal page won't that also mess up all our internal web services?

 

[rwwest7]

Who was in charge of this move? Were they a computer person?

You can't have one name resolving to two different addresses. Sounds like more planning is needed, and maybe some training as well.

 

[rchaiguy]

That makes sense...

what if we just bought the .net version of our domain for internal use and then we could route traffic as needed that way.... would that work?

 

[rwwest7]

what if we just bought the .net version of our domain for internal use and then we could route traffic as needed that way.... would that work?

You don't need to buy anything for internal use. You will still need to update all your links that you want to keep internal. But you can use something like .internal. For anything inside your firewall you can do whatever you want to make it work.