Wildcards in reverse DNS

[Steve K.]

I am curious, why are you using ipv6 in the first place? Aside from it's 
eye appearance (I frankly find it difiuclt to make any sence of show 
it's structured, where as ipv4 a.b.c.d is so easy to understand), why 
would anyone want to use it? I really am curious.

Joseph S D Yao wrote:
> I should add that you need those also for subdomains leading up to
> f.e.e.b and d.a.e.d:
>
> $ORIGIN 4.c.f.f.8.d.6.1.1.0.0.2.ip6.arpa.
> * IN PTR out-of-bounds.ipv6.cmd.nu.
> *.b IN PTR out-of-bounds.ipv6.cmd.nu.
> *.e.b IN PTR out-of-bounds.ipv6.cmd.nu.
> *.e.e.b IN PTR out-of-bounds.ipv6.cmd.nu.
> *.d IN PTR out-of-bounds.ipv6.cmd.nu.
> *.e.d IN PTR out-of-bounds.ipv6.cmd.nu.
> *.a.e.d IN PTR out-of-bounds.ipv6.cmd.nu.
>
> If you want to worry about all the little subdomains, then you need to
> add the following:
>
> $ORIGIN 4.c.f.f.8.d.6.1.1.0.0.2.ip6.arpa.
>
> b IN PTR out-of-bounds.ipv6.cmd.nu.
> d IN PTR out-of-bounds.ipv6.cmd.nu.
>
> $ORIGIN f.e.e.b.4.c.f.f.8.d.6.1.1.0.0.2.ip6.arpa.
>
> 0 IN PTR not-active.ipv6.cmd.nu.
> 2 IN PTR not-active.ipv6.cmd.nu.
> 0.0 IN PTR not-active.ipv6.cmd.nu.
> 2.0 IN PTR not-active.ipv6.cmd.nu.
> e.2 IN PTR not-active.ipv6.cmd.nu.
> ....
>
> $ORIGIN d.a.e.d.4.c.f.f.8.d.6.1.1.0.0.2.ip6.arpa.
>
> 0 IN PTR tunnel.ipv6.cmd.nu.
> 0.0 IN PTR tunnel.ipv6.cmd.nu.
> ....
>
> --
> Joe Yao
> -----------------------------------------------------------------------
>   This message is not an official statement of OSIS Center policies.