Dhcp not updating reverse ptr record
If you’re an experienced Windows system engineer, they may seem a little trivial.
But even the most highly trained and savvy administrator can get in a hurry and make a mistake.
It then acts like a teenager who can’t get the car keys, growing sullen and exhibiting a variety of bad behaviors. Let’s say you’re a VAR with a customer you plan to upgrade from NT 4.0 to Windows 2000 Server or Windows Server 2003.
The desktops use DHCP with a scope option that includes the IP addresses of two DNS servers managed by the customer’s broadband provider.
If you do give it a value, the resolver first tries the Primary Suffix, then the Connection-specific Suffix, then the parent suffixes of the Primary Suffix.
The TCP/IP settings for all network interfaces share an optional set of DNS suffixes that the Registry calls a Search List.
You’re so pleased with the ease of the upgrade that you forget to reconfigure the TCP/IP settings of the newly upgraded DC to point at itself for DNS. (If you’ve installed the Support Tools, you can run Netdiag /fix.) Now change the DHCP scope option to point clients at the new DC for DNS, then chase down any statically mapped servers and desktops and correct their DNS entries.
The TCP/IP Settings window calls this the Primary Suffix.
If a query using the primary suffix fails, and the Append Parent Suffixes option is checked, the resolver strips the leftmost element from the primary suffix and tries again. The TCP/IP settings for each network interface can have a unique DNS suffix, populated either statically or with DHCP.
Like a manager who doesn’t want to get dirty hands, it can let some other DNS server do the grunt work. The server that gets the job of doing the recursive queries and delivering the results is called a forwarder.
If you have a business relationship with an ISP, you might get an agreement with them to use their DNS servers as forwarders.
This agreement would allow your DNS server to send recursive queries to the ISP’s name servers.