4 ms·
> the current fleet of IT workers don’t really grok anything beyond A and PTR. Part of this, though is also who is "in control" of the server. Most of the tim
by whartung 3y ago
> the current fleet of IT workers don’t really grok anything beyond A and PTR.
Part of this, though is also who is "in control" of the server.
Most of the times, DNS is on the other side of the bastion, managed by Network Ops, and out of reach of Joe Developer. Perhaps a reasonable situation, fat finger DNS and Bad Things can happen. However, Joe Developer has carte blanche access to things like HTTP servers and with that they were allowed to go hog wild.
So, the innovation in the HTTP space exploded as it was a safer place to dabble to the point that every solution was viewed through the lens of HTTP.
In the end, devs don't know DNS because they don't need to know DNS, and even if they did, the Powers in NetOps weren't going to let them have their grubby fingers on it anyway.
- runjake 3y agoYep. I was speaking from a netops/sysadmin standpoint. My belief is that TXT and HINFO saw declining use within an org as Microsoft Windows DNS Server usage grew[1][2][3]. 1. Windows DNS Server hides those records behind a sub-menu item. 2. Windows DNS Server attracted noobs (a good thing, I suppose). Heck, these days, we give low/middle-tier IT workers DNS server access (via DnsAdmins group), which is crazy in my mind, but nonetheless common. 3. Crusty, old admins were better at typing yy in vi and changing the record type when creating new records in BIND (old DNS software).
- toomuchtodo 3y ago> when creating new records in BIND (old DNS software). Takes me back to rendering zone files using perl. The times they have changed.