-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, On 14/10/18 23:21, Russell Coker via luv-talk wrote:
On Sunday, 14 October 2018 5:01:41 PM AEDT Andrew McGlashan via luv-talk wrote:
On 03/10/18 14:28, Rick Moen via luv-talk wrote:
RFC2182 section 5 recommends minimum 3, maximum 7 authoritative nameservers for a domain, so five is pretty good.
RECOMMEND ....
Minimum is two, I've never seen any problems having just two with both being on different Internet links at different locations. It wouldn't
daisee.com. 21599 IN NS ns-1221.awsdns-24.org. daisee.com. 21599 IN NS ns-2000.awsdns-58.co.uk. daisee.com. 21599 IN NS ns-912.awsdns-50.net. daisee.com. 21599 IN NS ns-420.awsdns-52.com.
If you use "Route 53" (the DNS service from Amazon) then by default you get 4 authoritative name servers such as the above from different regions and different TLDs.
It's not unusual for businesses with one domain name, to have lots more covering all sorts of combinations in a similar manner to protecting trade marks. example.com example.net example.com.au .... ... This can easily get out of hand as well. Of course, "example" above could go with other options that suit the business without having just one base domain name to work from with a bunch of TLDs for each one as they make sense. There are long version domain names and short versions too; all of which are like "holding" real estate to some degree, protecting the brands and products on offer from the business. Given that I manage a number of my own domains and a bunch of others that I manage rely upon my name servers, I will put in place a third authoritative name server at some stage, hopefully fairly soon too. It wont hurt, but as I've got so many domains to manage, I won't palm this off to anyone, I'll handle it myself on a friend's machine (I manage his servers anyway). He has always said that I could put a name server there, but I never thought it was necessary, nor useful enough to worry about. Cheers A. -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCW8NN9gAKCRCoFmvLt+/i +8JMAPsEBB7VLMU9heWI6/MzibwO54CKJaXAaOfvaZKLjXJCYAD7B77I8dGhzyXM V+7n6ktEHxgpZIQMwZivQOvYgx+RDGk= =tLkh -----END PGP SIGNATURE-----