Re: system/1877: Reverse DNS query code in /sbin/rtquery is broken

[Andre Lucas <lucas@ae-35.net>]

I couldn't reproduce this problem - I get the correct PTR queries. The
machine I tried it on is running 2.9 too.

It's strange that cca2-gw.nottingham.ac.uk (.128) resolved correctly,
even though the PTR query you show is clearly wrong. What's particularly
odd is that the query domain order is not only wrong, but it changes!
Where are you getting the query debug info from? That last entry looks a
bit scary.

Do you have yp or /etc/hosts configured _after_ bind in resolv.conf?
Otherwise, it makes no sense - where did the name come from? If it was
in /etc/networks, it wouldn't have invoked gethostbyaddr() for
128.138.243.128 at all. [ getnetbyaddr()/getnetent() never invoke the
resolver or YP, so rtquery sometimes calls gethostbyname(). ]

-Andre

Sean McCreary wrote:
> 
> >Number:         1877
> >Category:       system
> >Synopsis:       Reverse DNS query code in /sbin/rtquery is broken
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    bugs
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   net
> >Arrival-Date:   Thu Jun 14 20:00:01 MDT 2001
> >Last-Modified:
> >Originator:     Sean McCreary
> >Organization:
> --
> Sean McCreary                        mccreary@cs.Colorado.EDU
>       University of Colorado at Boulder, Department of Computer Science
> >Release:        OpenBSD 2.9
> >Environment:
> 
>         System      : OpenBSD 2.9
>         Architecture: OpenBSD.i386
>         Machine     : i386
> >Description:
> 
> 
> These entries in rtquery output:
> 
> localhost.cs.colorado.edu (127.0.0.1): RIPv2 224 bytes
>   128.138.192.192/26 metric  1
>   128.138.193.0/26   metric  2            nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.199.0/26   metric  2            nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.205.0/26   metric  2            nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.236.0/26   metric  2            nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.241.0/25   metric  2            nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.243.128/26 metric  2 cca2-gw.nottingham.ac.uk nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.243.0/25   metric  2            nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.242.0/24   metric  2 capp-net.cs.colorado.edu nhop=cs-gw3-csops.cs.colorado.edu
>   128.138.244.0/25   metric  2            nhop=cs-gw3-csops.cs.colorado.edu
>   0.0.0.0            metric  3 default    nhop=cs-gw3-csops.cs.colorado.edu
> 
> ====================================
>  produce the following DNS queries:
> 
>  PTR? 128.138.192.192.in-addr.arpa. (46)
>  PTR? 0.128.138.193.in-addr.arpa. (44)
>  PTR? 0.128.138.199.in-addr.arpa. (44)
>  PTR? 0.128.138.205.in-addr.arpa. (44)
>  PTR? 0.128.138.236.in-addr.arpa. (44)
>  PTR? 0.128.138.241.in-addr.arpa. (44)
>  PTR? 128.138.243.128.in-addr.arpa. (46)
>  PTR? 0.128.138.243.in-addr.arpa. (44)
>  PTR? 0.128.138.244.in-addr.arpa. (44)
>  PTR? <M-LM-?M-_<S^B. (25)
> 
> >How-To-Repeat:
> 
> 
> Run /sbin/rtquery against any router running RIP
> 
> >Fix:
> 
> 
> >Audit-Trail:
> >Unformatted: