Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Currently we have an Active Directory setup, and say the name is 'domain.com'. The DNS entries for domain.com has two A records pointing to the two domain controllers. I would like internal users to be able to access our website by using http://domain.com/ but, we don't run the site off the domain controllers and I don't want to install IIS or some other service just todo a redirect to www.domain.com.

If I understand correctly, I should be able to delete those entries, and add a new A record pointing to the IP of the web server and things will not break, as clients typically use the SRV records to locate domain controllers and whatnot.

Is this correct? I don't want to cause an outage is the reason I'm asking before just changing it. :)

share|improve this question
1  
Of course if you would be happy to use domain.com the problem goes away (unless you have a server called "www"). –  John Rennie Jun 25 '09 at 16:26
add comment

5 Answers 5

up vote 12 down vote accepted

You're learning why you shouldn't use the same domain name for your Active Directory as you're using for your external Internet presence.

The "A" records for the domain referring to the domain controllers are used for DFS to resolve the name of the domain to a domain controller (primarily for client computers to access the SYSVOL). If you delete those "A" records you're going to see group policy break, amongst other things.

If you can't rename the AD domain, I think you're stuck putting IIS (or some other HTTP server) up on those boxes to redirect client computers to the right host.

This is why I name my AD domains "ad.domain.com". You should have a really, really good reason before you create a DNS zone on a private DNS server that matches a zone that the Internet has authoritative DNS servers for already. You've done that, and added Active Directory into the mix.

share|improve this answer
    
I totally agree. –  Maxwell Jun 25 '09 at 16:18
add comment

It is required that those A records point to domain controllers. They are must for DFS (SYSVOL, Netlogon access) and replication. In this case you can live dangerously and use some redirection tool or live with asking users to type www.domain.com. You can relieve their pain someways by making a favorites entry for domain in IE or making that home page for them. So they have to type it seldom.

share|improve this answer
add comment

This is the Active Directory equivalent of putting a gun to your servers and pulling the trigger multiple times.

If the entries were created by AD then do not mess with them. You will regret it.

share|improve this answer
1  
That's a little bit extreme. You can always do a "net stop netlogon" / "net start netlogon" to get those records re-registered. –  Evan Anderson Jun 25 '09 at 16:12
1  
It's a gratifying visual, though! –  squillman Jun 25 '09 at 16:22
add comment

You may solve your problem by deploying a custom host (/system32/drivers/hosts) file to them as a quick fix, i would not recomment messing with the active directory dns entries.

share|improve this answer
4  
No solution involving "hosts files" should be considered a good idea, IMO. Having said that, if you were to do that you'd break access to the domain SYSVOL from those client computers. –  Evan Anderson Jun 25 '09 at 16:17
    
Think i should have better read this question. thanks. –  Maxwell Jun 25 '09 at 16:22
add comment

If you want your users to get to you web page then just create a new host name in your DNS Manager (not Active Directory) called www and point it to your external web host. Done. then users just need to type www.yourdomain in their browser.

Bit late for you I recon but might help others.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.