BuddyNS logo

Setup Vanity DNS on your zones

Vanity DNS allows you to use BuddyNS infrastructure and present it to the Internet as your own.

With Vanity DNS, your domain names appear to the DNS hierarchy as served by ns3.your-company.com (or any personalized name), but these names are actually backed by fast, reliable servers from the BuddyNS Backbone.

Applicability and Extra Maintenance

Vanity DNS is an account-wide options. It is enabled for Advanced Users only: free users are required to use BuddyNS with their original names x.ns.buddyns.com.

Once an account has been upgraded to Advanced User, all of its zones can be optionally configured for Vanity DNS.

Warning! — Vanity DNS requires you an extra maintenance burden.

Most of our technical advances take place transparently for you. Occasionally instead they require a change of IP address. When this happens, you must update your delegation data with the new addresses. Here's the summary:

If you do not want to take on this duty, stick with the standard delegation form.

How to set up Vanity DNS for your BuddyNS zones

Setting up Vanity DNS is easy and only involves a few naming steps on your side. Here's the general steps you take to Vanity-enable your zone mydomain.com:

  1. BuddyNS offers you 5 servers; choose the names you want to give them in your zone.
    E.g. ns2.mydomain.com, ns3.mydomain.com, ns4.... See naming notes below.
  2. add new A entries to your zones mapping these names to BuddyNS server addresses.
    E.g. ns2 →, ns3 → etc. See naming notes below.
  3. update the NS records of your zone adding the new server names.
    E.g. mydomain.com IN NS ns2, mydomain.com IN NS ns3, etc.
  4. reflect the nameservers you set at step #3 at your registry (domain name vendor).

Notes on naming your new servers

Pick which BuddyNS servers to use for replication:

Vanity with many domains

If you are hosting many domain names, you may be tempted to delegate each one of them with its own Vanity servers. Don't!

Instead, follow this best practice: delegate your "host" domain name with a vanity mapping to BuddyNS. Then, delegate all your other domains to your "host" domain nameservers.

For example: say your primary ("host") domain is coolhosting.com, and you host domains c1.com through c1000.com for your clients. Delegate with vanity only coolhosting.com, e.g. defining ns{2,3,4,5}.coolhosting.com to point to your favorite BuddyNS servers. Then, delegate all other c*.com domain names to your host nameservers (e.g. ns{2,3,4,5}.coolhosting.com), as opposed to defining and delegating new ns{2,3,4,5}.c*.com for all clients.

So, this is good:

coolhosting.com → {ns2,ns3,...}.coolhosting.com   # vanity-delegated to BuddyNS
c1.com → {ns2,ns3,...}.coolhosting.com            # vanity-delegated to your host domain
c2.com → {ns2,ns3,...}.coolhosting.com

... while this is bad:

coolhosting.com → {ns2,ns3,...}.coolhosting.com
c1.com → {ns2,ns3,...}.c1.com
c2.com → {ns2,ns3,...}.c2.com

Why? Besides giving better visibility to your host domain, this setup makes your life much simpler when you need to change the Vanity destination, e.g. because you decided to switch to another BuddyNS server, or because we migrated one and instructed you to update its address.

IPv6 and Vanity DNS

As part of BuddyNS's outstanding support for IPv6, you can use BuddyNS's IPv6 nameservers to make DNS for your zones available over IPv6 without having IPv6 infrastructure at your side.

To add IPv6 support to your DNS, map each of the new NS entries you just defined to BuddyNS' IPv6 server addresses, using AAAA record types. Make sure to point each name to the IPv4 and IPv6 address of the same BuddyNS server.

For example, assume you associated ns2.mydomain.com to BuddyNS server c.ns. This means you just added to zone mydomain.com an A record mapping ns2 to address To have IPv6 reachability, add a new AAAA record mapping ns2 to address 2a00:dcc7:d3ff:88b2::1.

You end up with 2 records for each vanity name: one (type A) mapping the name to an IPv4 address, plus one (AAAA type) mapping the name to an IPv6 address.

Make sure to reflect this change at your registry.

When clients will query the DNS tree for NameServers of mydomain.com, they be given the list of your ns*.mydomain.com names, and the IPv4 and IPv6 addresses for each. IPv6-enabled clients will therefore be able to proceed resolving your domain names over IPv6 talking to BuddyNS servers.

BuddyNS server addresses

Locations of BuddyNS servers
BuddyNS name Location Addresses
b.ns.buddyns.com USA, Texas
c.ns.buddyns.com Europe, Germany
d.ns.buddyns.com USA, New York
e.ns.buddyns.com Russia, St. Petersburg
f.ns.buddyns.com Asia, India
g.ns.buddyns.com Canada, Vancouver
h.ns.buddyns.com Australia, Adelaide
i.ns.buddyns.com USA, California
j.ns.buddyns.com Europe, Netherlands
k.ns.buddyns.com Europe, Romania
l.ns.buddyns.com Asia, Japan

A Vanity DNS setup example

Say you want to setup zone mydomain.com with Vanity DNS.

Let's pick the BuddyNS servers to use: we use servers f, j, i.

Let's pick the vanity names to refer these servers with: we can use anything, and we choose us-ns, eu-ns, as-ns.mydomain.com.

We can assign any name to any BuddyNS server: we make these combinations:

eu-ns.mydomain.com.     IN A      # j.ns.buddyns.com
as-ns.mydomain.com.     IN A        # f.ns.buddyns.com
us-ns.mydomain.com.     IN A     # i.ns.buddyns.com

We then refer these new names as nameservers for mydomain.com:

mydomain.com            IN NS       eu-ns.mydomain.com
mydomain.com            IN NS       as-ns.mydomain.com
mydomain.com            IN NS       us-ns.mydomain.com

This setup is sound and complete if we only want IPv4 support.

If we want to add IPv6 DNS reachability, we proceed by adding AAAA entries for the same names:

eu-ns.mydomain.com.     IN AAAA    2a00:dcc7:d3ff:88b2::1   # j.ns.buddyns.com
as-ns.mydomain.com.     IN AAAA    2403:2500:4000::f3e      # f.ns.buddyns.com
us-ns.mydomain.com.     IN AAAA    2607:f7a0:a:23::3        # i.ns.buddyns.com

Any question or feedback? Contact support.