#112262 more than one PTR record is correct

#112262#5
Date:
2001-09-14 19:09:04 UTC
From:
To:
Hi

dlint produced this error:

ERROR: x.x.x.x.in-addr.arpa. has 3 PTR records, but there should be only
1.

This is not correct, from rfc2181:

   Confusion about canonical names has lead to a belief that a PTR
   record should have exactly one RR in its RRSet.  This is incorrect,
   the relevant section of RFC1034 (section 3.6.2) indicates that the
   value of a PTR record should be a canonical name.  That is, it should
   not be an alias.  There is no implication in that section that only
   one PTR record is permitted for a name.  No such restriction should
   be inferred.

Please inform upstream.

#112262#10
Date:
2001-10-07 22:08:28 UTC
From:
To:
Hello!


Upstream isn't reacheable currently. Homepage is
down and I don't get any answer to my emails to
the upstream author.

I will look at the changes which are necessary
by myself soon.


  bye
   Florian

#112262#15
Date:
2001-11-06 09:08:55 UTC
From:
To:
Hello!


Unfortunately this is a short status update only.

I have been unable to reach the upstream author for
some time now. Homepage is down and I don't get any answers
to my mails.

Any help appreciated.


I'd like to have a look at that bugs by myself, but I
might have time to do this next week at the best.

I'd highly appreciate patches or any other help here, too.


  Regards
       Florian

#112262#18
Date:
2001-11-13 23:11:39 UTC
From:
To:
Hello Paul!

And here comes the second bugreport.

  Greetings
      Florian
-----FW: <E15hyKm-0000zz-00@robol>----- Date: Fri, 14 Sep 2001 21:09:04 +0200 Sender: Piotr Krukowiecki <piotr@robol.ii.uj.edu.pl> From: Piotr Krukowiecki <piotr@pingu.ii.uj.edu.pl> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: Bug#112262: more than one PTR record is correct Package: dlint Version: 1.4.0-2 Severity: normal Hi dlint produced this error: ERROR: x.x.x.x.in-addr.arpa. has 3 PTR records, but there should be only 1. This is not correct, from rfc2181: Confusion about canonical names has lead to a belief that a PTR record should have exactly one RR in its RRSet. This is incorrect, the relevant section of RFC1034 (section 3.6.2) indicates that the value of a PTR record should be a canonical name. That is, it should not be an alias. There is no implication in that section that only one PTR record is permitted for a name. No such restriction should be inferred. Please inform upstream.
--------------End of forwarded message-------------------------