Hi Vadim, > What about e.g. people who have no choice? I would argue for the choice to pretty much always be there. I am a small operator and as such, share your concern for ability to do certain things on the Internet. But managing a zone is not one of those things.
If you want to “do public DNS”, you purchase a domain name or request one for free (though the issuers of the latter have varying track records). Then you can manage it through the registrar’s web UI if it’s something simple (e.g. A, AAAA, MX, peppered with a bit of SPF/DKIM/DMARC) and unlikely to change over time, or tell it to point to your own DNS servers if your needs are more complex than that. In terms of limitations of the latter, you do need a server with good availability, ideally 2 or more of them, and they have to have static IP addresses. But that’s not exactly hard to come by — any hosting provider that allows you to rent a VPS can hook you up with that. When designing for DNS, I would argue that we should design *only* for DNS. What people (read: registrars) build on top of that is their problem to solve. Not wishing to give them a hard time, but they can also pitch in if they have valid concerns. Met vriendelijke groet, Michael De Roover Mail: [email protected] Web: michael.de.roover.eu.org _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
