reverse address resolution problems

[Mark Damrose]

"Aidan Mark Humphreys" <ahumphr at ZAPgmx.net.easynews.com> wrote in message
news:aiu5o5$ffq6$1 at isrv4.isc.org...
>
> This has to be something dumb, but I can't see it.
>
[snip]
> Here is db.
> ------------------------------------------------------
> $TTL    3600
>
> 123.168.192.in-addr.arpa.       IN      SOA     bornheim.xzy.de.
> boss.xyz.de. (
>                                 1       ; Serial
>                                 3h      ; Refresh
>                                 1h      ; Retry
>                                 1w      ; Expire
>                                 1h )    ; Minimum
> ;
> ; Name Servers
> ;
> 123.168.192.in-addr.arpa.       IN      NS      bornheim.xzy.de.
>
> ;
> ; Addresses point to canonical names
> ;
> 187.123.168.192.        IN      PTR     bornheim.xzy.de.
> 185.123.168.192.        IN      PTR     aachen.xzy.de.
> 130.123.168.192.        IN      PTR     rome.xzy.de.
> 254.123.168.192.        IN      PTR     soho.xzy.de.
>
> ------------------------------------------------------
These addresses are dot terminated, and are not in your current origin of
123.168.192.in-addr.arpa.  Are you sure they didn't generate messages?

They should be fully qualified or not qualified - i.e.
187 IN PTR bornheim.xzy.de.
or
187.123.168.192.in-addr.arpa. IN PTR bornheim.xzy.de.