The Host's "A" Record Is Registered in DNS After You Choose Not
to Register the Connection's Address
تتسأسع
This article was previously published under Q275554
IMPORTANT: This article contains information
about modifying the registry. Before you modify the registry, make sure to back
it up and make sure that you understand how to restore the registry if a problem
occurs. For information about how to back up, restore, and edit the registry,
click the following article number to view the article in the Microsoft
Knowledge Base:
256986
Description of the Microsoft Windows Registry
SYMPTOMS
In Windows 2000, if you clear the
Register
this connection's address in DNS check box under
Advanced
TCP/IP Settings for a network interface, the IP address may register an
A record for the host name in its primary DNS suffix zone.
For example,
this behavior may occur if you have the following configuration:
- The DNS service is installed on the server.
- The DNS server zone is example.com, where the
example.com zone can be updated dynamically.
- The server host name is Server1.example.com, where Server1 has
two network adapters that have IP addresses of 10.1.1.1 and
10.2.2.2.
If you click to clear the
Register this
connection's address in DNS check box on the network adaptor that has
the IP address of 10.2.2.2 and then you delete the host record for
Server1.
example.com 10.2.2.2, the host record for
Server1.
example.com 10.2.2.2 is dynamically added back to the zone
late. The unwanted registration of this record can be reproduced if you restart
the DNS service on the server.
CAUSE
By default, when the DNS service is installed on a computer that
is running Windows 2000, it listens to all of the network interfaces that are
configured by using TCP/IP. When DNS causes an interface to listen for DNS
queries, the interface tries to register the host A record in the zone that
matches its primary DNS suffix. The interface tries to register the host A
record regardless of the settings that have been configured in the TCP/IP
properties. This behavior is by design and can take place under the following
circumstances:
- The DNS service is installed on the server whose configuration you are
trying to change.
- The DNS zone that matches the primary DNS suffix of the server is enabled to
update dynamically.
RESOLUTION
NOTE: The resolution that is described in
this article only works on member servers that run DNS in a domain. It does not
resolve this issue on domain controller computers. For additional information
about how to resolve this issue on a domain controller, click the article number
below to view the article in the Microsoft Knowledge Base:
292822
Name Resolution and Connectivity Issues on Windows 2000 Domain Controller with
Routing and Remote Access and DNS Installed
To prevent a DNS server from
registering an A record for a specific interface in its primary DNS suffix zone,
use one of the following methods.
Method 1
WARNING: If you use Registry Editor
incorrectly, you may cause serious problems that may require you to reinstall
your operating system. Microsoft cannot guarantee that you can solve problems
that result from using Registry Editor incorrectly. Use Registry Editor at your
own risk.
Configure the DNS service to publish specific IP addresses to
the DNS zone. To do so, make the following registry modification:
PublishAddresses
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
Data
type: REG_SZ
Range: IP address [IP
address]
Default value: blank
This modification
specifies the IP addresses that you want to publish for the computer. The DNS
server creates A records only for the addresses in this list. If this entry does
not appear in the registry, or if its value is blank, the DNS server creates an
A record for each of the computer's IP addresses.
This entry is for
computers that have multiple IP addresses, only a subset of which you want to
publish. Typically, this prevents the DNS server from returning a private
network address in response to a query when the computer has a corporate network
address.
DNS reads its registry entries only when it starts. You can
change entries while the DNS server is running by using the DNS console. If you
change entries by editing the registry, the changes are not effective until you
restart the DNS server.
The DNS server does not add this entry to the
registry. You can add it by editing the registry or by using a program that
edits the registry.
Method 2
Remove the interface from the list of interfaces that the DNS
server listens on. To do so, follow these steps:
- Start the DNS Management Microsoft Management Console (MMC).
- Right-click the DNS server, and then click Properties.
- Click the Interfaces tab.
- Under Listen on, click to select the Only the following IP addresses check box.
- Type the IP addresses that you want the server to listen on. Include only
the IP addresses of the interfaces for which you want a host A record registered
in DNS.
- Click OK, and then quit the DNS Management
MMC.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft
products that are listed at the beginning of this article.