http://site.com works outside but not inside network

[mattx]

There will be a simple explanation for this but can't see it. http://Http://site.com will work outside network, on another ISP etc, but if you are inside the network which is a 2003 domain then won't. Only http://www.site.com will work. Site.com is just the example btw. Also the site is hosted outside the domain. Someone point me in the right direction or give me a clue....

[saundersmatt]

Will the no www site resolve with nslookup?

[mattx]

Will the no www site resolve with nslookup?

 

nslookup outside the network resolves the correct IP on both http://site.com and http://www.site.com - so clearly there is no problem there - it's if you are on the internal network only http://www.site.com will work. The http://site.com comes up as the site is under construction ?!

[saundersmatt]

I meant on the internal network. Sounds to me like dns is giving the incorrect ip. Is there a zone for site.com configured on your internal dns server?

 

Another issue I have seen is that the webcache is caching old information. Do you have one, can you clear it's cache?

[john]

is the domain of the internal company network site.com?

 

If so you need a DNS entry for www as the name to the IP the site resolves to, we used to have this issue before I re-built the domain and named it a non-valid public TLD

[m25man]

There will be a simple explanation for this but can't see it. http://Http://site.com will work outside network, on another ISP etc, but if you are inside the network which is a 2003 domain then won't. Only http://www.site.com will work. Site.com is just the example btw. Also the site is hosted outside the domain. Someone point me in the right direction or give me a clue....

 

Your internal namespace shares the same TLD as your hosted web site therefore you must have an internal dns record pointing to your real www site.

 

Look up split DNS this is your issue.

[mattx]

Your internal namespace shares the same TLD as your hosted web site therefore you must have an internal dns record pointing to your real www site.

 

Look up split DNS this is your issue.

 

Whilst reading up on my bad and old DNS skills - this is what came up so will investigate.

[m25man]

It was late and I was on the Bus when I replied last night so here is a study guide You Need to Create a Split DNS!