• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 239
  • Last Modified:

2003 DNS Server issues

We have a 2003 server running dns for the AD intergrated zone, we have multiple A host records for different workstations for the same ip address:

example

pc102 10.0.5.10
pc180 10.0.5.10
pc43   10.0.5.10

pc11   10.0.5.43
pc17   10.0.5.43

As you can imagine this is causing a problem, clients are issued via dhcp without reservations, releasing and renew on the client machine has no affect.

We are running 2 other windows 2000 dns servers within the domain at different site, with the replicated zone

Any ideas on the best way to resolve?

Thanks
0
premierpc
Asked:
premierpc
  • 3
  • 2
2 Solutions
 
premierpcAuthor Commented:
the A host records were created automatically, even when deleted they reappear.
0
 
Netman66Commented:
You need to enable Scavenging on the DNS server, then on the Zones.

This is a common problem.

If you look at one of the PCs that show up by IP more than once, you should see DNSAPI errors in their Event Logs stating that the couldn't reregister properly with DNS.

0
 
jss1199Commented:
Hi premierpc,

Do you have DNS scavenging enabled?  If not, enable it and set the expiration to match your DHCP lease expiration.  This will not clean up the old records as aging starts only once DNS scavenging is enabled....

1.  Open DNS MMC
2.  Right click on your DNS server
3.  Click on Set Aging/Scavenging for all zones.

This will alleviate your problem in the future.  To clean up the duplicate IPs now, delete the record and then run a ipconfig /registerdns on the client(s)
jss
0
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 
premierpcAuthor Commented:
Thanks for the replys,

DNS scavenging is not enabled currently, I will enable as suggested then clean up the duplicates, would it be wise to add ipconfig /registerdns to the logon script as there are a number of machines affected?

Thanks
0
 
jss1199Commented:
For a very brief period just so your techs can go around, reboot and logon, sure....I would not put it in a logon script except for a strict duration that equals the time it would take me and my techs to remotely or manually reboot each machine and have the users log on.
0
 
premierpcAuthor Commented:
runnning ipconfig /registerdns did not create an A host record, although a workstation restart seemed to solve the issue.

Thanks for the speedy replies, points given
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now