Is this even valid??
;; ANSWER SECTION:
5.131.80.194.in-addr.arpa. 7200 IN PTR ezproxy2.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR uwrz46.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR *.ezproxy2.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR uwrz05.cymru.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR uwrz15.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR ezproxy.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR *.ezproxy.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR cymru.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR *.test.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR test.wales.ac.uk.
5.131.80.194.in-addr.arpa. 7200 IN PTR uwrz46.cymru.ac.uk.
Multiple records are ok, but the * contain records? That really doesn't
seem right. Almost like someone forgot to take into account those kind
of records in the forward lookup zone when writing a script to
automatically create the reverse zone.
All the DNS tools are perfectly fine resolving it but it still seems
bonkers. Ah, but Exim can't .. at least in any test I can throw at it in
a couple of minutes.
Exim shouldn't bug out or error on this - perhaps it should be ignoring
garbage results and just be happy the rest being ok .. except apparently
these aren't garbage results. :/ I can't for the life of me find an RFC
past 1035 (wasn't it deprecated? Or was that the email one) that allows
a * to be part of a valid hostname and hence listed as PTR data.
I'd shoot the person who put all that cruft in the in-addr.arpa zone
file ;) Remove it and Exim should be happy again. I really don't know if
we should consider it a bug in Exim though.
