This message was deleted.
# _general
s
This message was deleted.
w
Yes, typically Aging & Scavenging not configured properly. If DHCP runs on a DC, then DHCP and DNS are also not integrated properly. You are finding duplicate DNS records. I have a script on my site to give you a list of DNS Dupes. https://carlwebster.com/downloads/download-info/find-duplicate-dns-records/
👀 1
t
Great script will try it shortly..
WARNING: This record has been parsed incorrectly: '3600 SOA http://MYdom02.net.mydomain.uk. admin. 60338102 900 600 86400 3600' WARNING: This record has been parsed incorrectly: 'More records remain to be enumerated!' WARNING: This record has been parsed incorrectly: 'To enumerate ALL reissue the command with the \/Continue\ option.' WARNING: This record has been parsed incorrectly: 'To enumerate remaining records serially, reissue the command'
Think I've run out of room need to export-csv ?
w
Try the -SkipRoot parameter
t
ok
@Carl Stalhood Saw the presentation you made about fixing AD, mentioned that scavenging simply doesn't work 50% of the time, anyway I'll mention the 5 places you're suppose to enable it to systems incase they didn't try the commandline, out of interest did MS or yourself figure out why it simply fails?
w
that would be this carl, not the other carl :)
The only thing I remember saying not working is the Mr. FixIt for Time Server. If DHCP runs on a MS DC and you use MS DNS AND you have DHCP and DNS configured correctly, which is very rare), then I have never seen Scavenging not work. The reason I recommend manually cleaning up DNS of stale and duplicate records in DNS before enabling A&S is that the ownership of the records in DNS is often messed up, which can prevent deleting and scavenging the dns records.