Solved

Active Directory and website with same domain name but different server

Posted on 2014-04-11
3
920 Views
Last Modified: 2014-04-11
On my Windows 2008 R2 Active Directory server (which also is the DNS server), my AD domain name is MyDomainName.com.
Our college website, hosted on a separate server, has the same domain name, namely, MyDomainName.com.

In my DNS settings, I have MyDomainName.com pointing to 10.0.0.30, which is the AD & DNS server, and MyDomainName.com also has an A Record for 10.0.0.32, which is the webserver.

When accessing the website MyDomainName.com, the initial pause between adding the domain name to your browser and site actually appearing, can take many annoying seconds.  When I added another A Record pointing to our website and gave it Web.MydomainName.com, then the site appears very quickly.

I don't really know what is going on, but I am guessing the long delay has something to do with the AD Domain name having the same domain name as the website is the root of the problem?  The problem only happens on the campus where the AD server is, while off campus the domain name only points to the website IP address.
Is there something I am supposed to do on our DNS server to prevent this long delay from occurring?  So that when a browser makes a request to the AD/DNS server, it returns the IP address of the webserver immediately.  Or am I barking up the wrong tree with this?

NOTE: I have added this also to the IIS Web Server Topic, though our website does not use IIS.
0
Comment
Question by:hbcit
  • 2
3 Comments
 
LVL 25

Expert Comment

by:Zephyr ICT
ID: 39993524
The easiest and fastest solution will be to just make everyone use www ... Example www.yourwebsite.com ... You already did this creating a record named web, just replace that with www and it should be ok ...

It has indeed to do with your AD having the same domain name...

There's other solutions, but you're probably not going to like them ;)
0
 

Author Comment

by:hbcit
ID: 39993534
Thanks, have done that :)

So... what would be another solution... out of curiosity. :)
0
 
LVL 25

Accepted Solution

by:
Zephyr ICT earned 500 total points
ID: 39993538
Other solutions would be:

1) Rename the AD Domain
2) Install IIS on the Domain Controller(s) and create a redirection from yourdomain.com>www.yourdomain.com (for example)

Just off the top of my head :)
0

Join & Write a Comment

Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
Synchronize a new Active Directory domain with an existing Office 365 tenant
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now