#13 reverse dns ok doesn't like multiple AAAA records
Hi,
a friend just had this issue:
[OFTC] !irc6.oftc.net *** Your forward and reverse DNS do not
match, ignoring hostname.
He came from an address that has a correct reverse DNS, only the
forward has multiple AAAA records (which is ok).
weasel@valiant:~$ host 2001:6f8:989:17::3
3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.1.0.0.9.8.9.0.8.f.6.0.1.0.0.2.ip6.arpa
domain name pointer frell.theremailer.net.
weasel@valiant:~$ host -t aaaa frell.theremailer.net
frell.theremailer.net has AAAA address 3ffe:80ee:65:17::3
frell.theremailer.net has AAAA address 2001:6f8:989:17::3
About half the time it would accept his reverse, half the time it
wouldn't. Looks like the check only uses the first AAAA response
and compares that to the IP.
Happened on both plasma and neutron.
Same might apply to ipv4, I didn't check.
Logged In: YES
user_id=1525
(and stupid sf forgets I'm logged in all the time (probably
binding sessions to IPs))
Summary =~ s/ok/ok check/.
Logged In: YES
user_id=561663
this isnt really a bug.. the resolver is designed to work this
way. It only takes the first record returned. It works this
way as it is more efficient.