Discuss mailing list

[Nicholson-Goult Hayden <hang AT hng.ovh>]

The interesting thing is, I don't control the authentication via bind, it is controlled via a database connected to a whois server (whois.hn.fyi - only one domain is on it - test.co.hn.fyi). Yes, It's functionality can grow.

 

That's sad, but I do see more opportunities with .code

 

14.10.2020, 18:35, "Erich Eckner" <opennic AT eckner.net>:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 14 Oct 2020, Nicholson-Goult Hayden wrote:
 

 I was not aware of that no, thankyou for pointing it out, like I say, these
 are all theories of what can be done. And with the api, I wrote some sparse
 documentation:
 https://documenter.getpostman.com/view/13027629/TVRkaTtd#aee01ec7-085a-484e
 -bfc6-303229c5b722
  
 Now looking at the big picture, a lot needs to be added, but even if there
 is a structure for domain registration API's, I won't end up following it
 anyway.

This looks interesting. I guess, at some point, your api will also allow
to set AAAA, MX, CNAME, TXT and so on?

I wonder, if bind's rndc can have fine-grained access control, so that one
user (identified by key/ip/whatever) can only change their domains. This
might suffice for the "change my dns entries" part, so the only thing left
for an api would be the "register my account" part.
 

  
 And thankyou for your feedback, it's just one of the possibilities of uses
 for this TLD, Who knows? messy.code, Actually, I quite like that.

yeah, messy.code is also a good one :-)

btw: Originally, you also spoke of ".codes" tld. I just had a look at
icann's list of tlds (https://data.iana.org/TLD/tlds-alpha-by-domain.txt)
and it appears, that this one already exists.

regards,
Erich

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl+HNqwACgkQCu7JB1Xa
e1ozqQ//fNKYn+YHvJ+R63Au6TJgbiktaYqfbEfZRIW82tWk4d9MdvFHrnfuZExQ
y3Tg2Ft4GPUTA7WiVRxdZpuhe4RF+vgOA6y7uIgIcmQva1d47EN95ChPmooIcr6y
v3SxPJfxW121audTvrnR+oirF+OiR33IwkcQ1xzKM55TJxaSejV81uYDRyKt9dqv
jlYLbF6xuCnoH0lahKpj7QvbI2UpOObnzQ3ARt75fBxiKfFM5+lrhEE7gVPPpxma
nEZZHuNpr+DJHQnkPH6opIq0X3Pup+Cfa4Iv20ZwyW8MPc+u0nYZlX4he1RLJZBv
QT7Ohrc09gThCaeanLc7j5y39CoNfJGOwj/dkVanUx7V0P1PpMELrxepGtTfBVhb
7bij58H0b13f+gIa7UtluAMUji+LnOeD+3zDlRFzA8Dfx6oYghXIIgsa0LkZL8PO
M6c2hitXsUZGHGfHgKvHhvHu4TT7z7Px87RHmU1cdapee5GyTnpYV6yDTsI02D1s
HWAycl1suB0mzmBq3ovcdg97edN13q1k1nSRg3dw2SfYc7KNDwElZeB7A/HRT3AI
dVbhAN8gc1Fi312/tm0Zif1nhh8WzMpaw2rtV90A82OorEummok09XROvVrXyke2
3sDClotE1muBcK8cq3d49GsAzxduf4QaoI+ODPSWqDL2fgF9ZMA=
=6jDW
-----END PGP SIGNATURE-----

,

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

 

 

-- 

Best Wishes,

Hayden NG.