Non Existent Domain

[Danny Mayer]

At 12:16 PM 4/21/02, phn at icke-reklam.ipsec.nu wrote:

>Danny Mayer <mayer at gis.net> wrote:
>
> > At 01:24 AM 4/20/02, phn at icke-reklam.ipsec.nu wrote:
>
> >>Kevin Darcy <kcd at daimlerchrysler.com> wrote:
> >>
> >> > Unless you're using PTR records for some strange purpose, I'd get 
> them ou=
> >> > t of
> >> > your sinfor.net zone file. Normally PTR records are only found in the
> >> > in-addr.arpa namespace.
> >>
> >>There is one case where PTR is used in the "forward-zone file" and that
> >>is when the ISP has delegated a number of ip's to a customer,
> >>and CNAMES the PTR to "ip.customers-forward-zone"
> >>
> >>This way the customer only needs one file where both forward
> >>and reverse entries is kept. In fact, those who have used
> >>it may say "there is no better way".
>
> > In this case, the PTR records are not even correct.  It's supposed to be
>
> > rev.add.in-addr.arpa. IN PTR host.name.
>
> > instead of looking like A records.
>
>If you see the whole picture you willunderstand :

I did see the whole picture.  That was not what he was doing.

>ISP makes a CNAME for (45) in 66.123.22.45 in their 22.123.66.in-addr.arpa :
>
>45      IN      CNAME   45.customer.net.
>
>And the cuetomer in his zonefile for "customer.net" does
>
>customer.net.   IN      SOA ...
>                 IN      NS
>                 IN      NS
>www             IN      A       66.123.22.45
>
>
>45              IN      PTR     www.customer.net.
>

Right, if that what he had done.  Instead he had something like

www.customer.net        IN      PTR     66.123.22.45

which IS wrong.

>Works with bind, all versions, works with ( if anyone should care about it)
>w2k, does not work with NT ( but again, who cares)

BIND runs on all of those platforms and WXP.

         Danny