DC - Propagating DNS (msdcs) Entries Manually

Hi Everyone,


I've had a thorough search on here and Google and I can't even find another question like mine, let alone a solution...

I work for a company with (4) physical sites, for the sake of argument: London / Sunderland / Lincoln / Bristol

In November, we decided to P2V Bristol domain controller, but because the old one was a particularly bad build (tiny hard disk, hadn't been updated etc) we went ahead and removed the old DC gracefully, and simply built a new virtual DC in its place.

In addition to this, we re-addressed the network, converting it from a 192.168.2.x subnet to 10.2.0.x.

In order to ensure that we can still talk to some legacy hardware, the new DC is setup with a primary 10.2.0.x address, but has an additional NIC with a 192.168.2.x address configured with no DNS or gateway.

But here's the problem:

1. Despite both NICs having the 'Register this connection in DNS' setting disabled, the server regularly creates itself an A record in DNS for the 192.168.2.x address.
2. Within Sites and Services, the new subnet and the new DC are configured correctly.
3. Within DNS, under _msdcs the server UID listed in ADS&S is nowhere to be found.
4. Under '_msdcs\dc\sites' and '_msdcs\gc\sites' the Bristol site has disappeared completley.
5. Within DNS at the top level, the A record for the DC (the namless record) is not there (the NS record is however)

This means that the DC itself is running perfectly happily but that none of the clients in Bristol are actually using it, as DNS is forcing them over to a remote DC.

This is reported in DCDIAG, with the following error:

Doing initial required tests

   Testing server: Bristol\BRDC01
      Starting test: Connectivity
         The host
         088d1b55-f112-34ab-c121-f77d6a0d567a._msdcs.mycompany.com
         could not be resolved to an IP address. Check the DNS server, DHCP,
         server name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your
         firewall settings.
         ......................... BRDC01 failed test Connectivity

Realistically then, my question is whether anyone knows how to force the DC to re-propagate DNS with these entries. I have seen discussions which suggest restarting the NETLOGON service, I have done this but:

1. The DNS entries for msdcs etc do not re-appear.
2. The 192.168.2.x address for the server does re-appear (after manual deletion) when I restart the service.

It seems to me that having the 192.168.2.x address is causing the issues, but i'm failing to see a way of either identifying why it is causing problems, or how to resolve it, aside from simply removing the NIC.

Any help much appreciated!