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

I have a Windows Server 2008R2 Active Directory and Exchange 2010 server (client access, hub transport and mailbox roles) in a primarily Linux server environment. A Linux server running BIND9 is master for all zones, including AD specific ones, with updates allowed from the Windows server (and from a separate Linux DHCP server). A linux/postfix mail transport acts as the domain MX server and a smart relay for the Exchange server.

The Windows server is exchange.domain.tld (type= authoritative) but also has a type="internal relay" accepted domain within Exchange for domain.tld.

THE PROBLEM: The Windows server updates the DNS with itself as the A record for domain.tld - which it certainly isn't. This breaks DNS lookups for the company web server. I'm currently working around this by removing update access to domain.tld but leaving it in place for the AD specific subdomains, but this generates many errors (Event ID 5774) in the Windows server event log.

Additionally, the Windows server has a second NIC which connects to a private IP address range (used for a VOIP telephony system), and this address is also being set as an A record for domain.tld

Is there a way to limit/control what the Windows server updates? Any alternate suggestions about how to structure DNS in this environment would also be welcome.

share|improve this question

1 Answer 1

up vote 2 down vote accepted

Presumably you've had to set up a windows domain for exchange to work properly, is this server the domain controller too? If so it will automatically register itself as the top-level domain A record.

Also, yes there is a way you can work around this. Open network connections, right click on the NIC in question, click tcp/ip v4 then click properties. In the next window click advanced, then click DNS, then at the bottom uncheck "register this connection's addresses in DNS":

enter image description here

share|improve this answer
    
Yes, the machine is the domain controller. Thanks for the workaround. That is exactly what I was after. –  Runc Aug 1 '12 at 12:54

Your Answer

 
discard

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.