Freeapplied

Customize »


Advancedapplied

Customize »


Astronautapplied

Customize »

Answer client queries with BuddyNS

You need to update your DNS information in both your zone and your registry.

The Internet wants you to use at least 2 DNS servers per zone, but BuddyNS gives you multiple, globally distributed servers for best speed and reliability.

1. Select your servers

Locations of BuddyNS servers
DNS Server Name Location

2. Add NS records

Proceed as follows:

  1. Choose which BuddyNS nameservers you want to use from the list above. (3+ BuddyNS servers).
  2. Add these servers at your 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).
  3. Setup the same servers in your zone configuration at your primary server. See examples below for the concrete syntax in various DNS server types.
  4. Restart your DNS server to apply the changes. Changes to your registry may take 5 to 30 minutes to go public.
  5. Verify your new settings with the BuddyBoard (see below).
Configuration snippets for various DNS server types
Click any frame with code snippets to copy its content!
  1. Open your zone file, e.g.
    sudo nano /var/cache/bind/db.foo.com
  2. Add the NS records for your selected BuddyNS servers:
    # important: Append "." to all server names!
    zone "foo.com" {
    %%server_conf%%}
  3. Restart the server:
    sudo service bind9 reload
  1. Edit your TinyDNS data file:
    sudo nano /var/tinydns/root/data
  2. Add the NS records for your selected BuddyNS servers:
    # add NS records to all your zones, as follows
    %%server_conf%%
  3. Compile & send live your new DNS data:
    cd /var/tinydns/root && sudo make
  1. Open your zone file, e.g.
    sudo nano /etc/maradns/db.foo.com
  2. Add the NS records for your selected BuddyNS servers:
    # important: Append "." to all server names!
    %%server_conf%%
  3. Restart the server:
    sudo service maradns restart
  1. Open your zone file, e.g.
    sudo nano /etc/nsd/foo.com.zone
  2. Add the NS records for your selected BuddyNS servers:
    # important: Append "." to all server names!
    zone "foo.com" {
    %%server_conf%%}
  3. Restart the server:
    sudo service nsd reload

Simply copy-paste configuration entries for existing NS records, adapt them to contain the BuddyNS server you chose, and restart the server to apply the new configuration.

3. Validate your delegation setup

Log into your BuddyBoard. You see 3 indicators for your domain's Delegation Status:

Test Situation
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
BuddyBoard delegation checks

Other potential issues

Issue Description
Declares BuddyNS ERROR Cause: When queried for NS, none of the responses given by the server refers any *.buddyns.com entry. This means that, at this server, the zone is not delegated to BuddyNS.

Action: Repeat delegation setup.
No response Cause: 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.

Action: If this is registry or authority, this is unexpected, and you may use the Delegation Lab for further troublethoosing.
Difference Master and Authority Cause: In most of the cases, the declared master is also one of the delegated NS servers (Authorities) for the zone. In some cases their values can mismatch. Here's what this indicates:
  1. 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.
  2. 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.
Action: determine which case applies to you. In case #1, double check that master has correct delegation, then check your BuddyNS after a few minutes wait. In case #2, use the Target tool to ensure that your master does not serve DNS data. If so, you're OK.