Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm hosting some Windows servers on Rackspace, and have added them to a domain. Each server has two NICs, a public and private NIC. The public NIC has a public IPv4 and IPv6 address, while the private NIC has an RFC1918 address for communicating with other VMs within the datacenter.

The AD DNS has registered A and AAAA records for each IP address, for each client. Therefore, CLIENT01 looking up the IP address for CLIENT02 first gets the AAAA record, and then the public A record, then the private A record.

I know for my purposes, I only want the clients communicating with each other on the private network, because public bandwidth is billable. Also, the firewalls on each device behave differently for each NIC.

Is there an easy way of specifying (as a matter of policy?) that only a specific NIC should register its address in the AD DNS, so that client name resolution for other clients only returns a private address?

share|improve this question

In the Advanced TCP/IP settings for the IPv4 and IPv6 configuration of the external adapters, uncheck Register this connection's address in DNS in the DNS tab.

enter image description here

share|improve this answer
Can I automate this with GPO? Or is this a 'log onto each box and uncheck a box/run a script' type thing? – growse Nov 14 '12 at 15:53
You can probably automate it with a netsh script, but I don't think there are any point-and-click GPOs for this. I could be wrong, though. – MDMarra Nov 14 '12 at 15:54
Ok, I'll see if I can powershell it, or something. Thanks. – growse Nov 14 '12 at 15:57

Your Answer


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.