>would this be in the reverse setup ?
the CNAME of course should pose no problem, since CNAMEs are recommended in RFC 2317 for classless reverse delegation for smaller-than-ClassC subnets. So it was probalby just a temporary DNS lookup failure. The chain of delegation is: tx1# dig 118.89.156.68.in-addr.arpa. +trace ; <<>> DiG 9.2.3rc3 <<>> 118.89.156.68.in-addr.arpa. +trace ;; global options: printcmd . 486548 IN NS I.ROOT-SERVERS.NET. . 486548 IN NS J.ROOT-SERVERS.NET. . 486548 IN NS K.ROOT-SERVERS.NET. . 486548 IN NS L.ROOT-SERVERS.NET. . 486548 IN NS M.ROOT-SERVERS.NET. . 486548 IN NS A.ROOT-SERVERS.NET. . 486548 IN NS B.ROOT-SERVERS.NET. . 486548 IN NS C.ROOT-SERVERS.NET. . 486548 IN NS D.ROOT-SERVERS.NET. . 486548 IN NS E.ROOT-SERVERS.NET. . 486548 IN NS F.ROOT-SERVERS.NET. . 486548 IN NS G.ROOT-SERVERS.NET. . 486548 IN NS H.ROOT-SERVERS.NET. ;; Received 308 bytes from 127.0.0.1#53(127.0.0.1) in 13 ms 68.in-addr.arpa. 86400 IN NS chia.ARIN.NET. 68.in-addr.arpa. 86400 IN NS dill.ARIN.NET. 68.in-addr.arpa. 86400 IN NS henna.ARIN.NET. 68.in-addr.arpa. 86400 IN NS indigo.ARIN.NET. 68.in-addr.arpa. 86400 IN NS epazote.ARIN.NET. 68.in-addr.arpa. 86400 IN NS figwort.ARIN.NET. 68.in-addr.arpa. 86400 IN NS ginseng.ARIN.NET. ;; Received 197 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 166 ms 156.68.in-addr.arpa. 86400 IN NS NS.ATL.BELLSOUTH.net. 156.68.in-addr.arpa. 86400 IN NS NS.BELLSOUTH.net. ;; Received 95 bytes from 192.5.6.32#53(chia.ARIN.NET) in 64 ms 118.89.156.68.in-addr.arpa. 10800 IN CNAME 118.0.89.156.68.in-addr.arpa. 0.89.156.68.in-addr.arpa. 10800 IN NS charizard.s-wit.net. 0.89.156.68.in-addr.arpa. 10800 IN NS ns2.cl.bellSouth.net. 0.89.156.68.in-addr.arpa. 10800 IN NS ns3.cl.bellSouth.net. ;; Received 194 bytes from 205.152.0.20#53(NS.ATL.BELLSOUTH.net) in 61 ms Len
