On Tuesday, May 7, 2013 12:04:10 PM UTC-4, Justin T Pryzby wrote: > I recommend "dig +trace -x" on one of your assigned IPs. Compare with > > the result from a known-good sub-24 rev dns delegation. The ISP > > should be returning something like: > > > > 162.48.168.205.in-addr.arpa. 43200 IN CNAME > 162.160-175.48.168.205.in-addr.arpa. > > 160-175.48.168.205.in-addr.arpa. 43200 IN NS ns.norchemlab.com. > > 160-175.48.168.205.in-addr.arpa. 43200 IN NS ns1.norchemlab.com. > > > > and your NS should respond for the 160-175 zone. The particular > > naming convention doesn't matter, but has to be consistent between you > > and your ISP. The filename of the zone doesn't need to match the zone > > name, although that seems to be a popular misconception.. Slashes (as > > in 160/28.48.168.205.in-addr.arpa) are mildly inconvenient convention > > since, if the filename and zone DO match, they imply use of a > > subdirectory. > > > > Good luck, > > Justin
Thanks Justin, I've been testing with dig and that's how I got the failed results posted previously. My digs lead me to believe their zones are named the same as mine, with -'s instead of /'s. dig -x 1.1.1.90 +trace ----snipped---- ;; Received 180 bytes from 199.253.183.183#53(b.in-addr-servers.arpa) in 89 ms 1.1.1.in-addr.arpa. 86400 IN NS NS1.myisp.COM. 1.1.1.in-addr.arpa. 86400 IN NS NS2.myisp.COM. ;; Received 89 bytes from 199.180.180.63#53(r.arin.net) in 55 ms 90.1.1.1.in-addr.arpa. 3600 IN NS dns1.myns.com. ;; Received 75 bytes from 13.13.13.13#53(NS1.myisp.COM) in 84 ms ;; Received 44 bytes from 1.1.1.90#53(dns1.myns.com) in 80 ms <end> I've requested they confirm their setup, but I don't know how forthcoming they'll be. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users