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
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
On 2021-08-14 11:06, Rob PE1CHL via 44Net wrote:
Yes of course it is for coordinators - those are the
people who are
supposed to assign and update the name-address mappings.
I think once it was an objective of the portal to enable users to
update the entries in their own subnet, but it never materialized.
Also I thing a web DNS editor (most of them anyway) is not a useful
tool for a coordinator, as they need to have an overview of the entire
subnet they manage. When someone asks for an address I have to look
what is already there, which subnet is for that area, what ranges are
free, and then assign an address or subnet to them as required.
That is easy when having the hosts file (which includes comments) in my
editor, and much more difficult when I have to browse around in a
webtool.
DNS delegation fragments the resource. There are several NS records
that point to internet addresses, making us dependent on internet for
address lookup. This even is the case for
ampr.org itself for which
only 1 of the 4 servers is on AMPRnet.
Also those servers are distributed around the world. This makes
ampr.org and 44-reverse lookups quite slow.
As we like things to work well, I have an hourly job that checks the
DNS serial for the
ampr.org zone and when it is newer than our local
copy, it retrieves the newest zone files from
ftp://gw.ampr.org/pub/ampr.tar.gz and loads them into our own DNS
resolver.
So anything that is directly in those zonefiles can be looked up
quickly on our network, the delegated parts of course remain slow.
It would of course be better when we could just IXFR the updates from
the master server, but it does not support it.
I also tried to do this with some of the delegated servers but most of
them refuse transfers.
Not very friendly I would say, but likely it is just the default setup
for most DNS servers these days.
I think they should at least support zone transfer, preferably IXFR,
from net-44 addresses.
Rob
On 8/14/21 7:52 PM, Af6ep via 44Net wrote: I'd be happy to use the
email robot to update my own dns...... But last I heard it was
available to coordinators only and I've never seen a description of
howto use it published at least widely enough that it was seen by the
amprnet masses. I can also see security issues with such. I've been
asking for DNS zone deligation both forward and reverse for years, and
I would fully support such a move. It seems that the case for
transfering the entire
ampr.org zone is over rated and could still be
done by crawling the DNS tree, but why? if you are off line and
disconnected you only need DNS for your subnet anyway as you won't be
able to reach anything else DNS or not.
eric
af6ep
On 2021-08-14 08:43, Rob PE1CHL via 44Net wrote:
This is already there. Some regions and amateurs do run their own DNS.
I don't think it is that great, because it makes it impossible to
simply transfer the entire DNS
zone to a local server and have faster DNS lookups independent of an
internet connection.
But it works, I guess...
IMHO it would be better to offer a DNS update API, where everyone can
update their own host
records in an easily automated way. It of course exists in the form of
the mail robot and also
the web DNS editor but apparently some people think it is not good
enough.
(I use the mail robot myself as part of an automated update)
Rob
On 8/14/21 5:32 PM, Bill Buhler via 44Net wrote:
Just thought of this this morning, and was wondering if we could have a
DNS delegation system for hams off of
ampr.org or another domain name?
Something like:
af7sj.ampr.org ns myprimary.dns.server
af7sj.ampr.org ns mysecondary.dns.server
In my ideal deal world there would be a .radio TLD... or a .44net
tld... But would it make sense to offer any ham out there a DNS
subdomain based on their call? For those that want to limit access that
could also become part of their checks, i.e. does the forward and
backward DNS resolve to a
subdomain.ampr.org domain?
73
Bill Buhler - AF7SJ
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org