Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Solved
what would cause missing reverse DNS entries?
Posted on 2012-12-26
hi everyone
having a strange problem with some clients missing reverse DNS records. The forward entries are there. Scavenging is turned on but this happens with only a few random clients. We recreate the reverse DNS entry manually to fix. Any idea what would cause missing reverse DNS entries ? Not sure what other information to provide, other than we are not seeing any errors in the logs.
having a strange problem with some clients missing reverse DNS records. The forward entries are there. Scavenging is turned on but this happens with only a few random clients. We recreate the reverse DNS entry manually to fix. Any idea what would cause missing reverse DNS entries ? Not sure what other information to provide, other than we are not seeing any errors in the logs.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
3
2
6 Comments
Do you have your DHCP scope configured correctly for DDNS?
Always dynamically update DNS A and PTR records
Discard A and PTR records when lease is deleted
Dynamically updates DNS A and PTR records for DHCP clients that do not request updates
Do you only have DCs as your DNS servers in the TCP\IP settings?
Always dynamically update DNS A and PTR records
Discard A and PTR records when lease is deleted
Dynamically updates DNS A and PTR records for DHCP clients that do not request updates
Do you only have DCs as your DNS servers in the TCP\IP settings?
Active today
Do the affected clients have anything in common that the other clients don't (OS version, static vs. DHCP address, etc)?
Active today
ok so we have multiple remote sites, each with domain controllers. Each remote site is on a different network, for example 192.168.x.0 and 192.168.y.0 and 192.168.z.0... All are routed to the core site, with no traffic restrictions on the inside network.
None of the remote DC's have DNS. The DHCP scope at the remote sites points remote clients to our primary DNS server, which is a virtual machine dedicated to only DNS that is located at the core site. The secondary DNS server is our Primary domain controller, which is a physical box, also at our core site. So as mentioned the clients at the remote sites get DNS numbers that are for DNS servers located at the core site, which is the way it was set up when I got here.
At one site, I checked the DHCP lease pool DNS options and they are not what dariusg recommended. Currently they are set to the following
-"enable dns dynamic updates according to the settings below" is checked and the radio button "dynamically update DNS A and PTR records only if requested by the DHCP clients" is selected.
- "Discard A and PTR records when lease is deleted is checked
- "Dynamically update DNS A and PTR records for DHCP clients that do not request updates (for example, clients running Windows NT 4.0" is UNchecked.
Not sure what the impact will be for changing those settings to what DariusG recommended. I will try to look that up, any additional advice is appreciated, thanks in advance.
None of the remote DC's have DNS. The DHCP scope at the remote sites points remote clients to our primary DNS server, which is a virtual machine dedicated to only DNS that is located at the core site. The secondary DNS server is our Primary domain controller, which is a physical box, also at our core site. So as mentioned the clients at the remote sites get DNS numbers that are for DNS servers located at the core site, which is the way it was set up when I got here.
At one site, I checked the DHCP lease pool DNS options and they are not what dariusg recommended. Currently they are set to the following
-"enable dns dynamic updates according to the settings below" is checked and the radio button "dynamically update DNS A and PTR records only if requested by the DHCP clients" is selected.
- "Discard A and PTR records when lease is deleted is checked
- "Dynamically update DNS A and PTR records for DHCP clients that do not request updates (for example, clients running Windows NT 4.0" is UNchecked.
Not sure what the impact will be for changing those settings to what DariusG recommended. I will try to look that up, any additional advice is appreciated, thanks in advance.
Featured Post
Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them.
Troubleshooting Steps:
Connect via h…
OfficeMate Freezes on login or does not load after login credentials are input.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility.
Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten.
The USB drive must be s…
Suggested Courses
Course of the Month9 days, 19 hours left to enroll
722 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.