On 16/10/2010 21:48, Kevin Oberman wrote: > To be completely clear, unless there is special software on the client > to deal with PTRs, you really only want ONE PTR for each address. Most > standard network tools tend to assume only one PTR per address and some > get very confused when multiple PTRs are returned.
I'm intrigued as to what software it is that gets confused by having
multiple PTRs for IPs? Given I've been running with exactly that
configuration for many years, and never noticed any problems nor had any
complaints.
Still, I hope this whole argument will be rendered moot with the advent
of IPv6, where addresses are available in such enormous bounty that the
sensible admin would not only assign an IP per network interface, but
pretty much an IP per service too. No more fiddling about with TTLs or
waiting for changes to propagate should you need to shuffle things
about, and a natural consequence is that only one PTR would be needed
per AAAA.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
_______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
