+ 1 Votes What is wrong with giving each NS an A record? seanferd 2 years ago Reverse is the same. 0.168.192.in-addr.arpa 0.10.10.in-addr.arpa Just for example, look at the NS records here: http://www.robtex.com/dns/robtex.com.html#records (To avoid any potential confusion, note that I used the service to look up its own domain name.) None of the NS IPs share an octet at all. + 0 Votes Reponse To Answer seanferd 2 years ago No problem. I'm lucky enough to be not too deeply immersed in this stuff. :^0 Sometimes, this actually helps. But I do know what you mean about the given examples. A lot of texts tend to unnecessarily narrow the perceived range of possibilities by providing lowest common denominator sort of examples. Just an FYI: Correct practice, in fact, suggests you should have your public authoritative nameservers in at least two different Class C networks. So you're good to go on that count (assuming these are NS with IPs in public address space, and used over the internet as opposed to in a LAN). Hey, don't forget SOA for you main. + 0 Votes Thank you seanferd. lastchip 2 years ago When you stop and think about it away from all the documentation, tutorials and textbooks, the answer is almost obvious. This is an area that is brand new to me and getting my head around, I have to admit was not easy! Thank you for pointing me in the right direction.