BuddyNS logo

Answer client queries with BuddyNS

You need to update your DNS information in both (1) your zone and (2) your registry.

Each Internet domain is required to specify at least 2 'NS records', but BuddyNS gives you multiple, globally distributed servers for best speed and reliability. Here they are:

DNS Server Name Location
j.ns.buddyns.com Netherlands, Europe
d.ns.buddyns.com USA, New York
g.ns.buddyns.com Canada, Vancouver
e.ns.buddyns.com St. Petersburg, Russia
i.ns.buddyns.com USA, California
k.ns.buddyns.com Romania, Europe
f.ns.buddyns.com Asia, India
h.ns.buddyns.com Australia, Adelaide
c.ns.buddyns.com Europe, Germany
b.ns.buddyns.com USA, Texas
Press 'Recommend' to determine the best servers for your location.
Locations of BuddyNS servers
Careful! Cuidado! Vorsicht! Ă“cio! — It's buddyNS.com, NOT buddyDns.com !

Take the following steps to replicate your domain name with BuddyNS:

  1. Choose which BuddyNS nameservers you want to use from the list above. We recommend using 5 nameservers in your delegation, 3 or more from the BuddyNS backbone. Avoid delegating to more than 6 servers! — this would blow up your packet size and force clients to query your zones via TCP, for massively worse performance and reliability. Which BuddyNS servers? Pick them based on geographical proximity to your users, or randomly if you have no clue. For more inspiration, check out this post from our blog.
  2. Update your DNS information at the registry! This is the most important step. Log into the website of your domain name vendor and reach the Nameservers section (also called Registry, Authority, DNS settings etc). Type in the entries for your BuddyNS servers. Refer BuddyNS servers with their own names: If you need to rebrand them as ns4.yourcompany.com (Vanity DNS), you need to become an Advanced User.
  3. Enter the same server entries in your zone configuration. Here are syntax examples for the common DNS server BIND:
    zone "example.com" {
        example.com.   IN  NS   d.ns.buddyns.com.     # mind trailing dots!
        example.com.   IN  NS   e.ns.buddyns.com.
        example.com.   IN  NS   f.ns.buddyns.com.
        ...
  4. Verify your new settings with the BuddyBoard (see below).

Many DNS servers require restart to reflect configuration changes, so remember to do that to make sure your domain is functional!

Validating your delegation setup

BuddyBoard delegation checks

The BuddyBoard gives you 3 indicators for your domain's Delegation Status:

Master declares BuddyNS
Whether the primary server for this zone responds with any BuddyNS server to NS queries
Authority declares BuddyNS
Whether a nameserver delegated for this zone responds with any BuddyNS server to NS queries
Registry declares BuddyNS
Whether the registry for this zone responds with any BuddyNS server to NS queries

Declares BuddyNS here means that, when queried for NS, one of the records in the response contains at least one *.ns.buddyns.com entry. For Advanced Users, this also tests if any of the declared NS servers eventually points to a BuddyNS address.

Getting No response anywhere? The server being contacted has sent no response. If this is master, you may have a stealth master configuration that restricts which clients can make queries, or your AXFR server is not meant to do DNS; This is unusual, but perfectly fine. If this is registry or authority, this is unexpected, and you may use the Delegation Lab for further troublethoosing.

What's the difference between Master declares BuddyNS and Authority declares BuddyNS? In most of the cases, the declared master is also one of the delegated NS servers (Authorities) for the zone, and there are some cases when their values can mismatch. Here's what this indicates:

  • you updated delegation data at the primary, and that's not propagated to all other NS delegates yet. In this case, Master declares BuddyNS tells you upfront what's going to happen to the Authority after they sync.
  • your primary DNS server is transfer-only. Some ISPs, such as GoDaddy, use this setup. Here, the primary DNS server is used for serving AXFR (zone transfers) only, and does not respond to NS queries. In this case, BuddyNS tells you about the error and you can safely ignore this parameter.
Done!