Subject: Re: [44net] Bad MX records in the ampr.org DNS From: Tom Hayward esarfl@gmail.com Date: 06/02/2015 10:01 PM

To: AMPRNet working group 44net@hamradio.ucsd.edu

...

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).

I think when you are responsible for some subnet and you have frequent updates, it would be trivial to get you registered as submitter of updates to the DNS robot.

Also, there should be DNS update functionality in the portal and it should be possible to be a regional coordinator there, so you can approve the updates for your network. However, that function is still not completed.

I think that when problems are encountered, solutions should be sought that result in a clear and workable solution for everyone, not a fork of the main system. Effort spent on running a DNS for a subdomain had better been spent on a usable update mechanism for the main DNS.

Rob