Re: dns cleanup - delete all PTR records refering to a certain hostname
- From: roman sommer <roman_dot_sommer_@_gmail_dot_com>
- Date: Wed, 19 Apr 2006 19:28:52 +0200
first of all thanks for your reply.
I guess I will just copy the windows client behaviour. Disregard old PTR
records and add/update new ones as applicable.
I do know because that someone was me. I believe Windows clients removeAs far as I can see Windows clients don't care about old PTR recordsYour first statement is true, the question can only be answered if
either. Or does it appear like that because they were added manually
for testing purposes?
you knew someone was actually doing this.
their last valid PTR upon ip changes. Probably before updating the
records they first check for the old A record and try to find the
matching PTR this way. If the corresponding pointer exists it is removed
and new A and PTR records are added. I will log some packets and verify
this tomorrow.
Kevin D. Goodknecht Sr. [MVP] wrote:
roman sommer wrote:.
hello everyone,
I am writing a perl script which is (securely) updating A and PTR
records of *nix clients in a Microsoft environment (Microsoft Windows
2003 R2 servers in native mode). I need to know how Windows clients
update their PTR record. As far as I can see I can only query for an
ip address and get a hostname in return. I want to make sure I delete
*all* PTR resource records refering to a specific hostname before
adding the new one. To cut a long story short: "my hostname is
samehost.example.domain.com, delete all my existing PTR records".
If PTR records where registered by hostname it might work, but PTRs are
registered by IP number, not the data it contains. Just like A records,
which can have many records with the same name but different IPs, you can
have many PTRs with the same name, with different hostnames.
It would be unfeasible to lookup an A record by it IP, and it is unfeasible
to lookup a PTR by its hostname.
The problem is when a host leaves its PTR behind when it gets a new IP, it
cannot update the previous PTR because it no longer has the IP and doesn't
know it had it. So, it creates another.
I think the real trick would be having the client remove the record before
it gets disconnected. Laptop users are notorious for this and it is
unenforceable on them.
Two ways to keep the reverse lookup zone clean are; 1, enable scavenging on
the zone which is going to have some outdated PTRs; 2, Make the DHCP server
owner of all records and responsible for all registration so it can remove
old records as the lease expires.
As far as I can see Windows clients don't care about old PTR recordsYour first statement is true, the question can only be answered if you knew
either. Or does it appear like that because they were added manually
for testing purposes?
someone was actually doing this.
- References:
- dns cleanup - delete all PTR records refering to a certain hostname
- From: roman sommer
- Re: dns cleanup - delete all PTR records refering to a certain hostname
- From: Kevin D. Goodknecht Sr. [MVP]
- dns cleanup - delete all PTR records refering to a certain hostname
- Prev by Date: Re: Secondary Default Gateway?
- Next by Date: Re: DNS and active directory
- Previous by thread: Re: dns cleanup - delete all PTR records refering to a certain hostname
- Next by thread: DNS Update problem
- Index(es):
Relevant Pages
|