• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 930
  • Last Modified:

internal and external same domain name web site display problems

Hello all,

we have small office with active directory, dns and exchange server 2003 on single server. internal and external domain names are the same "mydomain.com". I have setup static host a record in internal dns server: mydomain.com forward lookup zone with "www"  name so users could access company website hosted externally. this host a record points to external ip address of mycompany.com internet website. everything worked good for long until internet website reconstruction. website is developed under adobe flash. when users try to navigate www.mycompany.com it displays background color of the website with 0% (or 100% on some machines, or browsers) and do not load contents.
I tried to clear browsers cache, adobe flash player cache. cleared cache on local dns server, restarted dns service, but issue  not resolved. it i manually change dns server ip address from internal dns server to external, then everything works. something wrong with internal dns server, though the iP address of the external website haven't changed.

pls, help, how can i resolve this problem.
2 Solutions
Kash2nd Line EngineerCommented:
what happens when you open up the website on the server itself. does it load properly ?
guramnAuthor Commented:
same on the domain controller itself. screen attached
guramnAuthor Commented:
Any ideas?
My guess would be that it is a problem with the website design, not a problem with the internal DNS.  For instance if some of the URLs in the HTML or flash code reference "domain.com" instead of "www.domain.com".  Or perhaps there is a reference to some other name like "images.domain.com" for which you haven't created an A record on your internal DNS to point to the external IP.
I agree with footech.  It's likely that something within the site's code references either domain.com (with no explicit hostname) or a hostname.domain.com FQDN that has no corresponding record in your internal DNS server.

If it's the latter, the fix is simple enough: create the necessary host record(s) on your server.  (You may need to contact the site developer or run a packet trace to determine what FQDNs are being referenced.)  Unfortunately, in my experience, the former is more likely, as referencing a site as domain.com rather than www.domain.com seems to be the hip thing among website designers nowadays, for reasons I'm sure someone thinks are valid.

If this is what's going on, you're in a bit of a fix.  Creating a blank host record on your DNS server and pointing it to the website's IP address is a bad idea; it will fix the website issue, but it may cause issues with AD, which uses blank host records for DC location.  Honestly, the best solution would be to contact the site developer and get them to change all references in the code to www.domain.com.

The root of the problem is that your internal and external domains have the same name.  If the site developer won't change the site code, your alternative is to rename your AD domain.  This is possible, but it can be a daunting task.

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now