Building redundant infrastructure that can withstand BGP and DNS configuration mistakes are not that simple but it can be done.
Building redundant infrastructure that can withstand BGP and DNS configuration mistakes are not that simple but it can be done.
Otherwise, 110MB would hint at a fascinating engineering culture at the motherboard manufacturer.
But if this guy is talking about a pentium 75 MHz (socket 5 CPU) that's a totally different generation of stuff several generations before that.
Ironically, denic still requires you to have two separate name servers with different IPs for your domain (which can be worked around by changing the IP of the registered name server afterwards lol), a requirement that all other registries I use have dropped or never had because enforcing such a policy at the registry level makes zero sense.
There isn't some magic reliability that everyone needs which just so happens to fall into "not achievable with a single authoritative name server" and "guaranteed with two servers". I'm not saying you should never have more than one, just that isn't the registry's business to decide what kind of availability guarantees you need for your domain.
That is not the ccTLD, that is an individual domain and its name servers. I recall being given that warning for early domain registrations.
Is it more or less than the F-root server run by ISC?
If you want, you can even request your own instance (a 1U Dell):
* https://www.isc.org/froot-process/
Or an instance of ICANN's L-root server, also 1U:
* https://www.dns.icann.org/imrs/
Would .de have more, or less, traffic than some of the root servers?
ns-cloud-c1.googledomains.com
ns-cloud-c2.googledomains.com
ns-cloud-c3.googledomains.com
ns-cloud-c4.googledomains.com
Would not make any sense to do four of them if it's a single AZ. Also, they are geo-aware and routed to your nearest region.