On Tue, Dec 09, 2003 at 08:36:21PM +0000, Jon Kyme wrote:
dig mwinf0502.wanadoo.fr
;; ANSWER SECTION:
mwinf0502.wanadoo.fr. 86302 IN CNAME smtp5.wanadoo.fr.
smtp5.wanadoo.fr. 3486 IN A 193.252.22.26
what's wrong with this? it's a FQDN. or is it that you think they shouldn't
use something with a CNAME? Is that not right?
Ok, my error.
But look at
datatracker.ietf.org:132.151.6.22 HELO optimus.ietf.org
datatracker.ietf.org -> 132.151.6.22
22.6.151.132.in-addr.arpa -> datatracker.ietf.org
optimus.ietf.org -> 132.151.1.19
19.1.151.132.in-addr.arpa. -> ietf.org.
ietf.org. -> 132.151.1.19
problem is, IP 1---n Name, I think. And these are all "legit", which just
No that is not the problem, there is no problem having multiple PTR
records. Look at e.g. pop.gmx.net:
pop.gmx.net -> 213.165.64.20
20.64.165.213.in-addr.arpa. -> mail.gmx.net.
20.64.165.213.in-addr.arpa. -> pop.gmx.de.
20.64.165.213.in-addr.arpa. -> pop.gmx.net.
20.64.165.213.in-addr.arpa. -> imap.gmx.net.
20.64.165.213.in-addr.arpa. -> mail.gmx.de.
goes to show that "paranoid reverse lookups" don't work.
Or have I misunderstood?
No you have exactly support my point of view ;-)
They can't get revDNS, forward DNS and HELO consistent. How should they
manage to get a PKI structure to work.
\Maex
--
SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
proportional to the amount of vacuity between the ears of the admin"
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg