Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I do not really understand what you see as a problem.
For the simplest cases you can often use the built in solution of the service you use to publish the website.
For any more than z simple a, cname an mx record you probably need more knowledge to know what you need, or you need to hire someone to plan that out.
And also, DNS actually changes, new features being added, so a very hold your had gui would need to change regularly and I have so far not seen any one making a good enough one for anything but the very simplest problems. -
Well...
DNS is extensible.
And Zonefiles are very cumbersome.
https://tools.ietf.org/html/rfc1035
The updates alone are ... hard.
NSD sums it up in an honest way:
https://nlnetlabs.nl/documentation/...
With the misusage of DNS as a general purpose configuration storage it became worse imho.
Writing a layer on top of that is always messy, as there are lot's of internals that need to be known depending on what you have and what you want.
Writing a clean zone file... Possible. Though TXT and IPv6 and DNS name validation can be tricky (TXT - encoding/parsing).
Parsing Zonefiles... Oh boy. It will end in suicide depending on age and system(s).
I literally laughed out loud
Turkish protesters against government trying shutting down social networks
Why do we still speak in direct DNS?
I don't know about you, but I have observed so many DNS mishaps in my day, and also have observed that developers and non-devs consistently fail to have a succinct mental model of how to set DNS properly for a website.
There are lots of services that make setting DNS easier than ever, but I'm kind of surprised so many people still have to think directly in terms of CNAMES, APEX DOMAINS, and all the direct domain knowledge of DNS.
Can't we have a higher level abstraction that compiles to DNS with more safety guards? Sure, let me dip into DNS when I need to, but why are DNS settings tables still such a normal thing?
I write Ruby code so I don't have to write C code. I'm sure there are attempts in DNS abstraction, but the fact that I haven't come across them means they are probably still too leaky or just not mainstream.
Thoughts on the matter?
question
dns