On Tue, Jun 2, 2015 at 12:16 PM, Rob Janssen pe1chl@amsat.org wrote:
Indeed... I don't see a reason to have a private nameserver for a subdomain either. The ampr.org nameserver works well, it allows updates, maybe the only thing that could be nice is the ability to set TXT and other records. Having a subdomain just makes things more complex.
I'm not sure if this is how everyone does it, but we (HamWAN) had to make DNS changes via our regional coordinator. We would construct an email in AMPR DNS robot format and send it to him, then he would forward it to the robot. This added quite a bit of latency (half day plus) to our updates and quite a workload for our regional coordinator (our network is growing fast).
Now we use our own domain for forward records and have reverse delegation to our nameservers . When we deploy new systems, they get documented in our portal and DNS records are created automatically in a SQL-backed zonefile. This is near instant and requires no human intervention beyond the original portal entry. This works a lot better for us and will scale as our network grows.
Tom KD7LXL