3 ms·
Well an actual DNS server, Whats wrong with authoritative DNS? just use DNS NOTIFY to update slaves on record change. That way TTL is not a problem, unless you
by KaiserPro 11y ago
Well an actual DNS server, Whats wrong with authoritative DNS? just use DNS NOTIFY to update slaves on record change.
That way TTL is not a problem, unless you have SSSD or nslcd doing caching on the client.
It'll remove a massive layer of complication, and will mean that you can have redundant service discovery even if your ETCD/skydns fails.
It'll certainly scale much, much higher than skydns. if you don't want to create your own DNS, Use Dyn. It has a REST interface, a very nice SLA. if you query the servers directly you also don't have to worry about TTLs
- threeseed 11y agoCan the SRV record be pushed via DNS Notify as well ? This is the main issue with DNS. That you need to get the port information from somewhere.
- KaiserPro 11y agoDNS NOTIFY is a mechanism to update slave servers. if you switch allow-notify on in bind it'll push updates from the master server to n slaves. This updates all records, TXT, AAAA, A, SRV, etc
- errordeveloper 11y agoRight, if you know how to set it up or have infrastructure in place... But most developers don't have time to read 600+ pages on how to run bind server OR simply have ops team that is very conservative at what goes in the DNS land.
- KaiserPro 11y agojust buy it in? dyn have a REST API. failing that, bind is not difficult to learn. If you have an artificial divide between your devs and you, then you have far bigger issue. If you can't convince them of the merit of using DNS then there really is no hope. the whole point of DNS is that you can delegate subdomains, so you can neatly isolate zones from each other Plus saying something looks hard is a terrible justification for not trying something. I know bind isn't trendy, but it works and is simple. Failing that, there are at least 3 companies out there with REST APIs and 100% uptime SLAs. prototype all the things!