Christopher.Vance@adfa.oz.au (Christopher JS Vance) (06/25/91)
When configuring the name servers under my care, I have for years put a zone at 127.IN-ADDR.ARPA, on the grounds that this was a class A network. I have not bothered putting any records at levels between here and 1.0.0.127.IN-ADDR.ARPA. Having recently done a zone transfer of the ARPA zone (okay, so I was curious) I discovered that my main server had inherited an NS record at 0.0.127.IN-ADDR.ARPA pointing to one of the root name servers (presumably the one which gave me ARPA). This also meant my own record for 1.0.0.127.IN-ADDR.ARPA was never visible. Questions: Should my own zone be at 0.0.127.IN-ADDR.ARPA, or was I right all along? Does it really matter? Is this yet another reason to leave the root-administered zones alone? I know it's not nice to do zone transfers on big zones, but it shouldn't cause things to break now, should it?... Restarting my server (without ARPA) has cured the symptom, but it looks to me like a problem waiting to recur. I suppose these bonus records are a matter of `BIND does it again'? -- Christopher