Microsoft KB Archive/253575
Article ID: 253575
Article Last Modified on 2/28/2007
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q253575
Domain Name System (DNS) dynamic updates of Pointer (PTR) records cannot be performed on a classless reverse lookup zone.
To create PTR records in a reverse lookup zone, follow these steps on the parent and child DNS servers:
On the Parent DNS Server
- Create a non-subnetted reverse lookup zone. For example, if you have subnetted your 192.168.1.0 network into two subnets, 192.168.1.0-127 and 192.168.1.128-255, and you want to create reverse lookup zones for the first subnet, create a reverse lookup zone for 192.168.1.0. The zone name is 1.168.192.in-addr.arpa.
- Right-click the new zone, and then click New Delegation.
- Click Next. In the Delegated Domain box, type 0/25, where 0 is the subnet address and 25 is the number of bits used for subnetting.
- Click Next. Add the child DNS server's name and address when you are prompted, click OK, and then click Finish.
- Right-click the parent zone (not the delegated zone), and then click New Alias.
- Type the alias (the last octet of the IP address). For example, type 1 for a host with an IP address of 192.168.1.1.
- In the Fully Qualified Domain Name box, type the CNAME value. For example, type 1.0/126.96.36.199.in-addr.arpa, and then click OK.
- Repeat steps 6 through 8 for every host that needs to be added.
On the Child DNS Server
- On the child DNS server, create a subnetted reverse lookup zone. For example, 0/188.8.131.52.in-addr.arpa.
- Create PTR records for every host under the new zone. In the Host IP Number box, type the last octet of the IP address. In the Host Name box, type the fully qualified domain name of the host.
NOTE: This example is for a subnetted class C network. For networks that use other class addresses, make the appropriate changes. For more information about subnetted reverse lookup zones see the following article in the Microsoft Knowledge Base:
174419 How to Configure a Subnetted Reverse Lookup Zone on Windows NT
This behavior is by design. It is not possible to perform dynamic updates of DNS records on a classless reverse lookup zone.
Additional query words: CIDR
Keywords: kbenv kbnetwork kbprb KB253575