I guess I am missing exactly why it is so important to keep dns in one piece (centralized to one server) as you suggest. What is so bad about dns acting as a tree that is crawled to resolve an address? if it's connectivity that's the issue then the same issue exists generally getting from your network to mine and mine to yours. If latency is the issue, that's what caching is for. What issue do you wish to address by keeping all ampr dns on a small set of servers.
Eric
AF6EP
On 2021-08-14 12:50, Rob PE1CHL via 44Net wrote:
Note that "being able to manage ones own subnet" does not imply that DNS will have to be delegated. It could just as well be a possibility to edit DNS records on the central DNS with some authorization method that allows you only to edit records within your own range and with your registered callsign. It still keeps the DNS in once piece.
Rob
On 8/14/21 9:42 PM, Af6ep via 44Net wrote:
Agreed, Zone transfers SHOULD be supported at least to Amprnet address space...... and deligations to run one's own forward and reverse dns SHOULD be allowed/maybe even encouraged. If I have a /24 or larger which is bgp announced (which I do), I ought be able to fully manage the Forward and Reverse DNS for it and subdomain.mycallsigns.ampr.org without having to go my coordinator. effectively by request I ought be able to be deligated those duties by my coordinator so they don't have to.
Eric
AF6EP
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net