mishcondereya
asked on
DNS cleanup - removing old forward and reverse lookup entries
hi all
im looking at cleaning up our dns records (2003 DNS server) at work as they are full of old entries... for whatever reason scavenging has not been turned on...
before i go down the process of enabling scavenging id like to do a manual clean up.
obviously ill be removing the forward lookup entries but im curious as to the reverse lookup entries.. should i remove these as well? what is the implications of leaving the reverse lookup entries?
just wondering what everybodies experience with this is and how i should approach a manual clean up..
cheers!
im looking at cleaning up our dns records (2003 DNS server) at work as they are full of old entries... for whatever reason scavenging has not been turned on...
before i go down the process of enabling scavenging id like to do a manual clean up.
obviously ill be removing the forward lookup entries but im curious as to the reverse lookup entries.. should i remove these as well? what is the implications of leaving the reverse lookup entries?
just wondering what everybodies experience with this is and how i should approach a manual clean up..
cheers!
ASKER
sorry i meant to update this post and say its actually a 2008 dns server.. my bad on that one.
to answer your question..
im new at my current workplace and from what ive been told, few years back they enabled scavenging and it caused a lot of problems with dns entries being deleted etc. ... this begs the question why didnt they leave it on once it was turned on and they resolved all the dns issues...?
but for whatever reason it was turned off again.. no idea what the reasoning behind this was.
so reason id like to do this manually is to get familiar with the dns entries, whats live whats not, what can be deleted etc...
its also to ease their mind that we are in control of our entries in regards to whats being removed.. once everything has been cleaned up i intend on turning scavenging on so we dont have to go through this tedious process.
I should also add that i havent done much work before with cleaning up DNS entries so its a bit of a learning curve for me as well..
thank you for the link, i will give it a read and post back when i have more questions about what im doing...
to answer your question..
im new at my current workplace and from what ive been told, few years back they enabled scavenging and it caused a lot of problems with dns entries being deleted etc. ... this begs the question why didnt they leave it on once it was turned on and they resolved all the dns issues...?
but for whatever reason it was turned off again.. no idea what the reasoning behind this was.
so reason id like to do this manually is to get familiar with the dns entries, whats live whats not, what can be deleted etc...
its also to ease their mind that we are in control of our entries in regards to whats being removed.. once everything has been cleaned up i intend on turning scavenging on so we dont have to go through this tedious process.
I should also add that i havent done much work before with cleaning up DNS entries so its a bit of a learning curve for me as well..
thank you for the link, i will give it a read and post back when i have more questions about what im doing...
ASKER
i am going to check out this link as its for 2008 dns servers
http://technet.microsoft.com/en-gb/library/cc771677.aspx
http://technet.microsoft.com/en-gb/library/cc771677.aspx
That's OK, there's not too much of a difference between 2003 and 2008 concept-wise.
If you really want to do it the proper way then I suggest you log into each IP address (be it a server, workstation, networking device, etc.) then confirm the computer name or device name matches the corresponding entry in DNS. It will be a time consuming process but it's the only way to be 100% sure you don't delete an entry for an active device.
If you really want to do it the proper way then I suggest you log into each IP address (be it a server, workstation, networking device, etc.) then confirm the computer name or device name matches the corresponding entry in DNS. It will be a time consuming process but it's the only way to be 100% sure you don't delete an entry for an active device.
ASKER
yeah.. ive actually got a powershell script that does that for me.
it pings the servers and finds the dns entries and notifies me if it matches the server or not.
if it does not match it shows me what server name its referencing... quite handy and has saved me a lot of time..
its not fool proof as it doesnt always return a entry.. just says it doesnt match, so those ones we have to investigate.
theres no major rush with this which is why i want to do it right so parts of it will be manual.
ive found a powershell script here https://www.experts-exchange.com/questions/28472243/Powershell-script-to-read-txt-file-and-remove-DNS-entries.html
that will read a csv file and delete the records that i specify.... i just need to test this before running it on our live environment.
in regards to my query about forward and reverse lookup entries.. anything i need to be mindful off when removing them?
it pings the servers and finds the dns entries and notifies me if it matches the server or not.
if it does not match it shows me what server name its referencing... quite handy and has saved me a lot of time..
its not fool proof as it doesnt always return a entry.. just says it doesnt match, so those ones we have to investigate.
theres no major rush with this which is why i want to do it right so parts of it will be manual.
ive found a powershell script here https://www.experts-exchange.com/questions/28472243/Powershell-script-to-read-txt-file-and-remove-DNS-entries.html
that will read a csv file and delete the records that i specify.... i just need to test this before running it on our live environment.
in regards to my query about forward and reverse lookup entries.. anything i need to be mindful off when removing them?
in regards to my query about forward and reverse lookup entries.. anything i need to be mindful off when removing them?Apart from what's already covered above, not really.
Actually, I think the PTR records even get deleted automatically when you delete the corresponding A host record. Try this on your end with a known stale DNS record to confirm.
ASKER
ok will do
thanks for your help... youve definitely helped me out and sent me on the right path..
will post back later if i have any more questions.
thanks for your help... youve definitely helped me out and sent me on the right path..
will post back later if i have any more questions.
One thing you might consider to help with manual cleanup is to enable scavenging on the zone (but don't enable the server to perform scavenging so it doesn't actually delete any records). With it enabled on the zone you can see which records are getting their timestamp updated and so those records don't need to be modified.
Some of my favorite links for scavenging.
http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx
http://blogs.technet.com/b/networking/archive/2009/02/09/optimizing-your-network-to-keep-your-dns-squeaky-clean.aspx
http://blogs.msmvps.com/acefekay/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group/
Some of my favorite links for scavenging.
http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx
http://blogs.technet.com/b/networking/archive/2009/02/09/optimizing-your-network-to-keep-your-dns-squeaky-clean.aspx
http://blogs.msmvps.com/acefekay/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group/
ASKER
Footech
can you explain a bit more on how that feature works ?
so my understanding from what you said... that if its enabled on the zone but not on the server it will show which entries can be deleted?
can you explain a bit more on how that feature works ?
so my understanding from what you said... that if its enabled on the zone but not on the server it will show which entries can be deleted?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I also recommend you have a read of this article to give you a better understanding DNS scavenging: http://technet.microsoft.com/en-us/library/cc759204(v=ws.10).aspx