3 ms·
How many of those are due to companies trying to do weird things with DNS, though? DNS itself is quite well-designed for its age. It is decentralized, so there
by crote 3y ago
How many of those are due to companies trying to do weird things with DNS, though?
DNS itself is quite well-designed for its age. It is decentralized, so there is no single-point-of-failure. A request can fit in a single UDP package, so load balancing is trivial. A response can contain multiple records, making it possible to use it for load balancing or failover. The format is designed to be extensible, so it can be used for more than just the original few applications. It is definitely showing its age when it comes to privacy and security, though.
Can a failure of an authoritative DNS server bring down a website? Absolutely! Set a short TTL and bring down the servers due to fatfingering a config, and your website will go offline. But you can hardly blame DNS itself for that.
- nvarsj 3y agoWhat do you mean it's decentralised? It's a central service you have to query for name->IP lookup, with authoritative name servers for every domain. It's the very definition of centralised. Just because it's hierarchical doesn't mean it's not centralised. A decentralised DNS system would be more like a p2p network where you can perform name lookups from any participant in the system. Companies aren't trying to do anything weird with DNS. It's just how most things work in service architectures. Every network query will start with a DNS query. You might depend on 50 services, with circuit breakers and all kinds of great logic so a single service won't bring you down - but there is that DNS lookup which will break everything if it fails.