4 ms·
I read this as just "actual DNS". An actual DNS server, that serves the records you need, like SRV records. Eg. djbdns[1]. It's not like using DNS SRV for servi
by e12e 11y ago
I read this as just "actual DNS". An actual DNS server, that serves the records you need, like SRV records. Eg. djbdns[1]. It's not like using DNS SRV for service discovery is some crazy thing; Kerberos uses it, and by extension Windows AD[2].
Other "recent" uses of SRV is XMPP server discovery.
Anyway, SkyDNS might be great -- but is it tested/aimed at being better/faster than other battle-tested DNS servers? Everyone needs to host DNS in some way -- can they standardize on one server, and just use SkyDNS? Should they?
Or is the main thing just wrapping a REST api around DNS? [ed: like [3,4]]
Even if I need/should use a non-standard (non-authorative, not connected to the Internet root) DNS infrastructure for service discovery, do I need to turn off caching if I want to use SkyDNS for it?
A lot of these kind of questions leap to mind.
To draw a parallel, one can use nginx for TLS termination, reverse-proxy and as a host for static assets -- often it'd be good to set them up as different services, even if they run the same software. It a) allows easy switch if needed (maybe HAProxy turned out to be a better load balancer), and easy scalability. But all else being equal, without any major differences in performance (order of magnitude), or feature set -- having two instances of one piece of software is likely simpler than having one instance each of two pieces of software.
So, in that light, "What's wrong with actual DNS"? :-)
[1] http://anders.com/projects/sysadmin/djbdnsRecordBuilder/ http://anders.com/projects/sysadmin/djbdnsRecordBuilder/
[2] https://technet.microsoft.com/en-us/library/cc961719.aspx https://technet.microsoft.com/en-us/library/cc961719.aspx
[3] https://github.com/ajclark/bind-restapi https://github.com/ajclark/bind-restapi
[4] https://doc.powerdns.com/md/httpapi/README/ https://doc.powerdns.com/md/httpapi/README/