15 Aug
2021
15 Aug
'21
3:29 p.m.
Well, in the spirit of "keeping the network in one piece" that some people seem
to want (and having it isolated from internet), I would like to see the network being as
self-contained as possible, i.e. we can all talk to each other without depending on
internet services.
When we have one DNS zone, that is easy to achieve. Make the servers that serve it
conforum to that.
When we have multiple DNS zones delegated to different people, their servers have to
conform to certain standards, including being on 44-net addresses that are reachable from
the internet as well (BGP routed, probably).
44.0.0.1 is, but unfortunately many of the delegated DNS servers are not. They are either
on internet addresses, or they are not accessible from internet.
Preferably the servers for the delegated zones would also allow zone transfer to addresses
within our network.
We have nothing to hide, right? And people may like to have a cached copy of the zones on
their local server for faster response.
The more delegations there are, the more difficult it will be to achieve and maintain that
goal.
Rob
On 8/14/21 10:52 PM, Af6ep via 44Net wrote:
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:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 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(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net