15 Aug
2021
15 Aug
'21
3:37 a.m.
the reverse delegation I'm speaking of is z.y.x.44.in-addr.arpa and
possibly b.c.a.callsign.e164.arpa. for that, dns needs to be delegated.
True, names to addresses it's a bit easier, but still if I want to
manage subdomain.ampr.org, ampr.org must delegate that authority,
otherwise when dns goes to crawl the tree subdomain.ampr.org is not
found because there is no pointer from the ampr.org server to the server
which authoritatively resolves subdomain.ampr.org.
eric
AF6EP
On 2021-08-14 13:15, K7VE - John via 44Net wrote:
DNS pointing to 44 net addresses can be done by any
using any domain.
RDNS
(PTR Records) can be either AMPR.ORG or delegated.
On Sat, Aug 14, 2021 at 12:51 PM Rob PE1CHL via 44Net <
44net(a)mailman.ampr.org> 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(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net