14 Aug
2021
14 Aug
'21
12:13 p.m.
Not to mention what the commercial side of domains do, EPP (Extensible
Provisioning Protocol).
The following are the RFCs for EPP that are listed on the Wikipedia page
for EPP:
* RFC 3375 - Generic Registry-Registrar Protocol Requirements
* RFC 3735 - Guidelines for Extending EPP
* RFC 3915 - Domain Registry Grace Period Mapping (e.g. Add Grace
Period
<https://en.wikipedia.org/w/index.php?title=Add_Grace_Period&action=edit&redlink=1>,
Redemption Grace Period
<https://en.wikipedia.org/wiki/Redemption_Grace_Period>)
* RFC 4114 - Using EPP for ENUM <https://en.wikipedia.org/wiki/ENUM>
addresses
* RFC 5910 - Domain Name System (DNS) Security Extensions Mapping for
the Extensible Provisioning Protocol (EPP) (obsoletes RFC 4310,
DNSSEC <https://en.wikipedia.org/wiki/DNSSEC>)
* RFC 5730 - Extensible Provisioning Protocol (EPP) (obsoletes RFC
4930, which obsoleted RFC 3730)
* RFC 5731 - Extensible Provisioning Protocol (EPP) Domain Name
Mapping (obsoletes RFC 4931)
* RFC 5732 - Extensible Provisioning Protocol (EPP) Host Mapping
(obsoletes RFC 4932)
* RFC 5733 - Extensible Provisioning Protocol (EPP) Contact Mapping
(obsoletes RFC 4933)
* RFC 5734 - Extensible Provisioning Protocol (EPP) Transport over TCP
(obsoletes RFC 4934)
* RFC 8543 - Extensible Provisioning Protocol (EPP) Organization Mapping
* RFC 8544 - Organization Extension for the Extensible Provisioning
Protocol (EPP)
Sincerely,
Keaton VE5LPL
A Saskatchewian ham who does stuff and things
https://kagl.me me(a)kagl.me
On 2021-08-14 10:07 a.m., Darcy Buskermolen via 44Net wrote:
There is a whole RFC 2136
<https://datatracker.ietf.org/doc/html/rfc2136> dedicated
as an "API" for DNS updates.
On Sat, Aug 14, 2021 at 8:44 AM Rob PE1CHL via 44Net <44net(a)mailman.ampr.org>
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:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 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