Reverse lookup of selected IP addresses without delegation agreement?

[Len Conrad]

>So if I stick to my own example of mail.sourceforge.net, I'd use these
>settings?
>
>    # named.conf
>    zone "206.250.35.66.in-addr.arpa" in {
>      type master;
>      file "206.250.35.66.zone";
>    };
>
>    # 206.250.35.66.zone
>    @  IN SOA  ns.mydomain.tld. hostmaster.mydomain.tld. ( ... )
>       IN NS   ns.mydomain.tld.
>    206.250.35.66.in-addr.arpa.  IN PTR  mail.sourceforge.net.

yep

>I want to make sure that I "intercept" only reverse lookups for the
>selected hosts I choose to define, but let all other lookups pass
>unmodified.

the above will do that for spoofed zone 206.250.35.66.in-addr.arpa

>BTW, this would require a .zone file for each host, right?

yep

>Or is it
>possible to use one "hijacked.zone" with multiple entries if I make
>use of $ORIGIN statements?

nope, named will bitch about "out of zone data"

>  > With RFC 2317, the child zone's PTR records must match the CNAME
>  > rdata fields in the parent zone.
>
>Can this cause any trouble for my users if I use the configuration
>shown above?

it could do, if your spoofing doesn't match official PTR over at the 
delegated DNS.

Len


_____________________________________________________________________
http://IMGate.MEIway.com : free anti-spam gateway, runs on 1000's of sites