Hot answers tagged nameserver
The warning is about the redundancy of your name servers, which are controlled by your provider. Maybe check with them about their redundancy, but they probably use some kind of anycasting scheme to ensure the availability of the name servers. You can probably just ignore that warning.
you have to log onto your registrar site: $ whois tullamoretoastmasters.org|grep NS Name Server:NS1.YOURDOTSER.COM Name Server:NS2.YOURDOTSER.COM and change the above to: $ dig @NS2.YOURDOTSER.COM tullamoretoastmasters.org ns +short ns2.tullamoretoastmasters.org. ns1.tullamoretoastmasters.org. EDIT: your registrar is not claiming or ...
I'll answer the question in 2 stages: 1. What is setting the DNS “A” record the "A" record usually maps ip address to hostname For example your servers ip address is: 10.10.10.10 your domain name is: yoursite.com so your A record will be yoursite.com IN A 10.10.10.10 From the A record you can branch out prt and c names For example a ...
Several problems (which may not actually fix your issue). Your IP addresses for NS3 and NS4 don't match, they're .4 in one block, .116 in the next block. You need two ip addresses, one for each name server (or find a 3rd party solution for backup DNS). It may work, but it's absolutely the wrong way to do it. If your name server is down clients will have ...
I suspect this is referring to the fact despite being separate physical or virtual servers they are both on the same subnet/ physical network, if a network specific issue occures then both name servers will be unreachable. It is good practice to have name servers in physically different networks/locations.
Only top voted, non community-wiki answers of a minimum length are eligible