Cname error
Michael Voight
mvoight at cisco.com
Thu Aug 5 23:43:59 UTC 1999
OK, but it's a CNAME error, show us the CNAME records.
It seems to say address 88 in this zone doesn't have a matching record.
And you don't list an 88 record in the domain below.
So, it looks like you created a CNAME for 88, and then didn't create a
PTR for it.
Michael
Benjamin John wrote:
>
> Aug 5 18:33:33 omega named[322]: dangling CNAME pointer
> (88.88/29.92.220.209.in
> -addr.arpa)
>
> what does this mean ?
>
> here's the conf file
>
> zone "88/29.92.220.209.in-addr.arpa" in { <- whats subnetted to me
> (209.220.92.88 - 95)
> type master;
> also-notify {
> 209.220.92.94; <- my primary DNS
> 207.155.183.72; <- my secondary
> };
> file "db.209.220.92";
> };
>
> and here's db.209.220.92.
>
> 88/29.92.220.209.in-addr.arpa. IN SOA ns.firstconsulting.net.
> root.firstconsulting.net.
> (
> 1999033030 ;
> Serial
> 10800 ; Refresh after 3
> hours
> 3600 ; Retry after 1
> hour
> 604800 ) ; Expire after 1
> week
>
> IN NS
> ns.firstconsulting.net.
> IN NS
> nameserver.concentric.net.
>
> 90 IN PTR
> alpha.firstconsulting.net.
> 91 IN PTR
> genesis.firstconsulting.net.
> 94 IN PTR
> omega.firstconsulting.net.
> 89 IN PTR
> router.firstconsulting.net.
More information about the bind-users
mailing list