Cant browse external company website while on company domain?

Someone please shed some light on this for me, i know its not that complex but i cant figure it out :/

My client has a domain xyz.com.  Their domain is hosted with GoDaddy and GoDaddy manages the DNS for the domain.  There is a A record in place on GoDaddy that points to the IP of the website which is hosted by another company.

The website for anyone except folks at the office works fine.

In the office there is a Win 2008 R2 domain controller running DNS for all the client machines.  The domain name of the internal domain in the office is xyz.com.  

I have created a www record in DNS on the server to point to the IP just like GoDaddy but instead all the clients just get a blank white screen.  From a mobile phone, any other machine on the planet they get to the site fine.

Is there some other type of record i need to add to the internal DNS in the office to make internal requests go out to the correct site on the net?

I have tried ipconfig /flushdns, clear dns cache, rebooting, etc...

Thanks Everyone
orlandotommyAsked:
Who is Participating?
 
DrDave242Connect With a Mentor Commented:
There may be a redirect on the site that redirects www.xyz.com to simply xyz.com (which will show up as the URL changing in the web browser when you access the site externally), or there may be references within the site code that refer to it as xyz.com instead of www.xyz.com.

If one of these is the case, there's only one thing you can do to fix it without causing other problems: remove the redirect or change the site code so that it only refers to the site as www.xyz.com.
0
 
orlandotommyAuthor Commented:
That seems to be the case, if i go to www.xyz.com it shows up in a browser as xyz.com when the site comes up?

So what exactly should i do now since that is the case?
0
 
DrDave242Commented:
Since the website is hosted by another company, you'll need to get them involved, as they're likely the ones who put the redirect there. Tell them you need the redirect removed and explain why.

They may try to tell you to create a blank host record (a record that refers to xyz.com) on your local DNS server instead of removing the redirect, but that won't work in an Active Directory domain. There are already blank host records there, and AD uses them to identify domain controllers. Creating another record won't fix the website issue and will cause other problems.

It is possible that the other thing I mentioned is also present: references in the site code to xyz.com rather than www.xyz.com. If the web host removes the redirect but the site still won't display (or only partially displays) when accessed from inside the office, that's probably the cause, and the site's code will have to be modified.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.