• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows Server 2003 and Reverse DNS zones

RadiclDreamer

RadiclDreamer

Diamond Member
Cross posting this here since it got no love in Software for Windows. If a mod can delete the old I would appreciate it 🙂

I have two dns servers in my environment, dns1 and dns2. They are both running server 2003.
We are doing massive expansion to the network and as such there have been several new subnets created. Each of these subnets have been given an ip helper to the dhcp server and a scope on the DHCP server has been created with dns1 and dns2 ip addresses given as the dns servers.

The fun starts when I look at reverse records, seems that some vlans automatically created their reverse lookup zone, (but not all clients show) but some did not have a lookup zone. So, for example I have 172.25.100.x Subnet in the dns server under reverse lookup but none of the clients who are receiving an address on 172.25.100.x are registering a reverse lookup. Clients are 99% XP.

I tried creating the lookup zones but it doesnt seem to be helping.

Any idea what would cause this? Let me know if you need more info.
 
Yes, this is what I want to happen. The only reason its important is i have a production app that checks the reverse record
 
Have you tried doing an ipconfig /registerdns on one of the affected machines? I am pretty sure that the machines only try to register DNS once and assume that if they reacquire the same address, that the information is still registered. DHCP basically hands out information once, and if the same machine reboots it will ask DHCP "is this address still mine" rather than "I need an address." Each are handled differently on XP. Basically "is this address still mine" gets a simple DHCP ACK or NAK and the client starts using it, a NAK results in an "ok so what is my IP."

You can accomplish the same thing by deleting the lease in DHCP while the computer is off if you only have users on site and you don't want to hold their hand through the scarey cmd window.
 
Last edited:
imagoon said:
Have you tried doing an ipconfig /registerdns on one of the affected machines? I am pretty sure that the machines only try to register DNS once and assume that if they reacquire the same address, that the information is still registered. DHCP basically hands out information once, and if the same machine reboots it will ask DHCP "is this address still mine" rather than "I need an address." Each are handled differently on XP. Basically "is this address still mine" gets a simple DHCP ACK or NAK and the client starts using it, a NAK results in an "ok so what is my IP."

You can accomplish the same thing by deleting the lease in DHCP while the computer is off if you only have users on site and you don't want to hold their hand through the scarey cmd window.
Click to expand...

Ive tried this several times, no change there either.
 
When you created the zones, did you give 'Domain Computers'... I think it is "create" and "Update" access to the zone? I need to check that part out. Also are these AD integrated or stand alone zones?

I am not at work / in front of DNS servers so my memory maybe failing me on the terms.
 
DNS1 is AD integrated, DNS2 is secondary and gets notified of changes. Ive created the zones and allowed dynamic update is there anything else that could cause it? Does it matter that I host 2 domains on the dns server?

So both servers host container.parentdomain.com and otherparentdomain.org but the dhcp server is configured to give out otherparentdomain.org as the dns suffix. I thought this would only affect forward so thats why I left it out at first.
 
OK, perhaps I'm slower than normal tonight, but I'm having a hard time understanding all of the details behind the issue. Mind answering these?

So... you have two different DNS zones, and two different DNS servers? Are both zones on both servers? Are zone transfers enabled between the two servers for those zones?

What is the dns suffix for the computer name on the workstations? Are there any group policies modifying DNS or DHCP behavior?

Does either zone machine the Active Directory domain name? In which zone are you wanting the clients to register? Are you wanting the clients to register in both the forward lookup zone (zone.tld) and the reverse lookup zone (in-arpa)? Might it be acceptable to have the DHCP server request the DNS registration on behalf of the client, instead of requiring the client to perform the registration?
 
you have two AD right? best place to keep dns. and dhcp servers.

the reverse dns is auto created by dhcp server but updates to those records require authentication perms
 
RadiclDreamer said:
DNS1 is AD integrated, DNS2 is secondary and gets notified of changes. Ive created the zones and allowed dynamic update is there anything else that could cause it? Does it matter that I host 2 domains on the dns server?

So both servers host container.parentdomain.com and otherparentdomain.org but the dhcp server is configured to give out otherparentdomain.org as the dns suffix. I thought this would only affect forward so thats why I left it out at first.
Click to expand...

The DNS server is a member of which domain? Sounds like the client computers are in a different AD domain than the DHCP / DNS servers? If so, is there a domain trust configured to allow the clients update rights to DNS?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top