How to Stop a Cennection from Registering in DNS 1

[Ztrek7]

Windows Server 2000, running DNS, active directory integrated. It is a DC. I just added a second NIC to access a second network. The problem: An entry keeps appearing in the DNS forward lookup zone. I unchecked the register this connection in DNS, disabled NETBIOS on the WINS tab, and only thing enabled on connection is TCP/IP (No Client for MS network,etc). I even went as far as unchecking the main connection's register setting but to no avail.

I can't have this keep popping up because clients are resolving to this which cannot talk on that network.

Any ideas?

 

[kbing]

I encountered this issue on W2003 Standard server. I had to remove the DNS entries from the 2nd NIC. Mine was a DC with DNS services locally. The 2nd NIC in my case was for a backup network so no need for DNS.

 

[Ztrek7]

Good Idea. I took off the DNS entry, and it told me that since I did that, and itself is a DNS server, that it would "fix" it for me.

The entry popped back up.

Tried setting DNS to something I new is not a DNS server. The entry popped back up.

Starting to remind me of the "Cat came back" song.

Any ideas?

 

[nsantin]

When using an Active Directory-integrated DNS zone the DNS server will automatically add NS records corresponding to themselves.

To stop this configure the following registry value on each affected DNS server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters

Registry value: DisableNSRecordsAutoCreation
Data type: REG_DWORD
Data range: 0x0 | 0x1
Default value: 0x0

This value affects all Active Directory-integrated DNS zones. The values have the following meanings:
Value Meaning
----------------------------------------------------------------------
0 DNS server automatically creates NS records for all Active
Directory-integrated DNS zones unless any zone, that is hosted
by the server, contains the AllowNSRecordsAutoCreation
attribute (described earlier in this article) that does not
include the server. In this situation, the server uses the
AllowNSRecordsAutoCreation configuration.

1 DNS server does not automatically create NS records for all
Active Directory-integrated DNS zones, regardless of the
AllowNSRecordsAutoCreation configuration in the Active
Directory-integrated DNS zones.

 

[Ztrek7]

nsantin,

I had my hopes up on that one!

I put it in with a value of 1, restarted DNS server,still with no luck.

Need another idea!

Thanks

 

[AJP69]

I use 3 multihomed NICs in all my servers, two interserver lans and one workstation lan.

Our DC is also a DNS server but it does not do DHCP.

A few things you might try checking:

1. Do not put any values in the the default gateway of the second NIC (assuming it should never have to leave the subnet)

2. Make sure that under network and dial-up connections under Advanced settings on the Advanced menu you have the lans in the right order.

3. Check that your DNS host records in the workstation lan are not being deleted, as a temporary fix you can disabled DNS dynamic updates while you sort it out.

Let us know how you get on.

 

[drexelpike]

i'm having the exact same problem. its driving me nuts. ive done everything listed above and until i fix this i just have to keep deleting the records in the forward lookup zones.

does anyone else have any ideas?