BuddyNS is a free secondary DNS service. When you register a domain name and run the DNS yourself, you use BuddyNS to replicate your DNS service.

BuddyNS is the fastest-to-synchronize DNS service on the Internet. Whenever you add or modify records for your domain name, BuddyNS synchronizes within 10 minutes, or immediately with SyncNOW!. As a comparison, most alternative services synchronize in one to twelve hours.

BuddyNS is not a public DNS cache such as OpenDNS. BuddyNS is meant to assist domain name owners, not end users.

BuddyNS strives for ease of use and reliability. Here are the features in a nutshell:

• world's fastest synchronization of DNS changes (<10 minutes)
• highly-available, low-latency global DNS infrastructure
• full support for Internationalized Domain Names (IDN)
• outstanding security and reliability, 100% uptime since inception
• outstanding IPv6 support: AAAA records, DNS lookups, WWW, AXFR
• unlimited domains, records, and updates allowed
• free of charge up to 0.3 Million queries/month
• BuddyBoard for monitoring configuration and state of your zones
• responsive and competent support

BuddyNS's DNS replication service (secondary DNS) is free for all users, for both personal or commercial use. Users who require advanced features or produce high volumes of traffic (advanced users) are required to subscribe for a paid account.

Here's the details for each account type:

Free User

• free of charge for personal and commercial use
• up to 0.3 Million queries/month total traffic (per-account)
• cannot refer BuddyNS with custom names in NS records (no Vanity DNS)
• support requests deferred 24 hours

Advanced User

• 10x larger traffic quota
• priority zone updates
• present your domain names as served by your own infrastructure (Vanity DNS)
• access extra services like GeoStats
• priority e-mail support

For further information, see all benefits of Advanced User accounts.

External secondary DNS services sucked for decades. We keep our fundamental service free to make it available to as many users as possible and set a new standard in DNS.

Our revenues come from Advanced Users, who are professionals, companies or private individuals enjoying premium services or simply willing to support BuddyNS.

Better DNS consistency

BuddyNS dramatically improves the consistency of your domain data by ensuring your secondary DNS servers are always updated shortly after you perform any modification at the primary DNS.

Better geographical presence

BuddyNS runs a global DNS infrastructure, with locations strategically determined to serve your users' queries fastest across the globe. Don't settle for vendors with a beefy two-site infrastructure!

Easy to use

BuddyNS is built with the ease of use in mind. Check out the BuddyBoard for a taste.

Great support

All inquiries to support@buddyns.com get answered by people who know what they're talking about.

BuddyNS offers free accounts for all users, personal and commercial use, regardless of number of zones, records, or monthly updates.

Our free accounts are limited to 0.3 Million queries per month. If you operate an account totalling more than this traffic, we require you to open an advanced user account to support our operation.

BuddyNS is not designed for Dynamic DNS.

Because of its blazing fast syncs, some users choose to use BuddyNS for this purpose anyways; This use is not trivial and not supported.

They setup a script to run whenever their IP address is changed, and use our API to automatically update this data on BuddyNS. Don't do this unless the primary is always available on one address or the other.

Notice that while removing and re-adding a zone through our API, the zone might go unserved for a couple of minutes.

Also, notice that we may delay or cancel your account if you make unfair use of our resources, e.g. by sending hundreds of sync requests a day. We do so to prevent few careless users from spoiling service of many other users. See our Terms of Use.

We do not offer a web panel where you can edit the records of your domain, because our current focus is improving DNS replication (secondary DNS) over the Internet.

However, you can still use all-and-only BuddyNS servers to serve your domain: you just need to provide your zone to BuddyNS via AXFR.

Traditional service providers use software off-the-shelf. BuddyNS employs an ad-hoc infrastructure designed from scratch exclusively for fast zone synchronization. This tackles three improvements:

1. more efficient update checks
2. distributed system
3. separate DNS updaters, checkers, and publishers

Here's how it works. Inside BuddyNS, multiple checkers poll domains for updates. Each can issue hundreds of checks per second, so domains can be checked frequently. Checkers relay which domains need update to two transfer systems. These fetch up-to-date zone data and transfer such data to publishers. Publishers are only concerned with answering client queries about your zone.

BuddyNS splits a traditionally all-in-one system in three levels, and optimizes each individually. This dramatically improves robustness and performance.

Our infrastructure page will show you that BuddyNS is a global cluster with presence in all of these regions:

• Asia
• Canada
• Europe
• India
• Middle East
• Oceania
• Russia
• US

How do we select each location?

We manage geographical presence as a strategic asset, assessing factors including latency, peering, continuity, and political stability.

Latency is a crucial factor in the planning. Users have ephemeral patience for loading time, and all the time you save on DNS is more room for your web servers to generate valuable content: simple improvements on DNS save you otherwise substantial costs in development and infrastructure. It won't make much difference if DNS latency is 5, 10 or 25ms, but growing latency past 100ms surely does.

Most DNS resolvers today select the DNS server to query based on best response time, so having points of presence nearby can reduce latency substantially. Our locations are planned with the goal to offer sub-30ms response time to densely populated areas and sub-70ms to most of the world's connected areas.

Why haven't we deployed to South America and Africa? South America generally lacks intra-regional peering, so that most traffic between South American countries goes through Miami and back, making local deployments mostly useless. Africa's ring backbone has a similar challenge.

For users to whom jurisdictional borders are relevant, notice that BuddyNS provides you with this information explicitly.

Which locations should you use? We instruct users to delegate their zones to 3-5 BuddyNS servers. This improves reliability and resolution time, since most Internet resolvers pick their destination based on response time.

Our setup docs help you select which BuddyNS servers you should delegate to, based on your location.

SyncNOW! is your way to manually request immediate update for your zones.

Log into your BuddyBoard and push the SyncNOW! button. BuddyNS will start a synchronization procedure shortly for all zones configured in your account. If your account hosts many zones, push the little SyncNOW! icon next to the specific zone you want to update, so your update will go through more quickly!

With SyncNOW! BuddyNS cuts DNS synchronization habits from many hours to minutes or seconds! In its simplicity, this fixes a problem that annoyed DNS administrators for two decades.

Yes it does!

With NOTIFY, your master DNS server sends a special message to all secondary servers for zone X when you change zone data for X. This message informs all secondary servers that a change occured, inviting them to synchronize the new DNS data without waiting until the next polling.

BuddyNS supports NOTIFY notifications:

• All servers of the BuddyNS cluster understand NOTIFY requests. No constrains when choosing which ones to use as secondaries for your zones.
• Actual zone transfers are delayed up to 60 seconds after NOTIFY for security reasons.

For the geeks: some DNS implementations at your primary might report an error after sending NOTIFY requests to BuddyNS. You can safely ignore these: BuddyNS servers won't give an answer to these requests, but transfers will be initiated with the random delay.

Internationalized Domain Names (IDN)

BuddyNS supports IDNs natively.

DNS notify

BuddyNS supports NOTIFY invocations. Transfers are initiated with a random delay up to 60 seconds for improved security.

DNSSEC

BuddyNS does not support DNSSEC because it exposes to some vulnerabilities unsuited to a high-volume DNS service.

IPv6

BuddyNS has all-round support for IPv6: DNS AAAA records, DNS queries, AXFR transfers, NOTIFY, WWW — they all just work on BuddyNS.

Outward AXFR

Since BuddyNS is a secondary-only service (you cannot edit your zone from BuddyNS), you already have an AXFR in your control.

Anycast DNS

BuddyNS does not support anycast routing because it introduces major network complications to bring negligible performance improvements. Most DNS clients today pick the nearest server to query themselves anyway.

RFC2317-style classless reverse delegation

BuddyNS will reject domain names that contain '/' characters as recommended by RFC2317. Multiple articles ([1], [2], [3]) explain why that's a bad idea. We recommend you delegate individual addresses (as in [3]) or use the '-' symbol as range separator.

Sure thing. See our API documentation page.

Yes. In fact, we maintain a cPanel-BuddyNS integration plugin for you to replicate your DNS with BuddyNS while controlling your domains exclusively from your cPanel/WHM interface. No extra infrastructure or complexity.

BuddyNS strives for ease of use. If you understand basic DNS concepts, BuddyNS guides you through a copy/paste configuration procedure, and helps you troubleshoot and fix arising problems with the BuddyBoard. For several configuration mistakes at the primary, BuddyNS will send you automatic notification e-mails with a problem brief and fixing instructions.

If you have no idea what DNS is — e.g. you don't know that DNS is organized as a tree — BuddyNS will likely be a waste of time for you. Look for Managed DNS services.

All DNS services that support AXFR (standard DNS zone transfer) are compatible with BuddyNS. Services that do not support AXFR cannot be used with any secondary DNS service, because the service won't be able to get your DNS data to replicate.

Amazon's Route 53 does not support AXFR, so you are unable to use Route 53 with any secondary service. DynDNS lacks this feature as well.

Some providers that do support AXFR are:

• Conexim
• DNSMadeEasy
• GoDaddy
• Linode
• XName (contact support)
• Zerigo
• ZoneEdit

If your provider is not in this list, contact their support and inquire about AXFR. Since it's a standard DNS service, it's possible that they'll enable it just for you. And if you don't get it, at least they'll get to know that people care about it.

Always start as a free user by activating a domain on BuddyNS. If your traffic qualifies as advanced user, you will receive an automatic e-mail explaining you when and how to upgrade.

If you want to upgrade to Advanced spontaneously (e.g. because you want Vanity DNS), you can do so from the BuddyBoard, Account pane.

Advanced users contribute a monthly amount. This is paid via PayPal with 1, 2, 3, 6 or 12 months periodicity. BuddyNS uses PayPal subscriptions to make billing slick and convenient for the user.

Sure! Find the bulk activation form within your BuddyBoard. Paste as many zones as you wish in the text area, enter the master for them, and hit Add zones. BuddyNS will proceed to register each zone.

You need to have an account for this. If you're a new user, create one by registering the first zone manually.

You may also build a simple script to automate this operation from your server using our API. Here's an example for BIND on a UNIX system:

# extract blank-separated list of zones
zones=`ls /var/named/*.db | while read zf; do basename $zf .db ; done`
# address of master DNS server (replace yours)
master="192.168.100.200"
# authentication et al parameters (replace your API token)
curlpar="-XPOST -H 'Authorization: Token abc123abc' -Fmaster=$master"
# iterate to add each zone in list
for z in $zones ; do
    echo "Adding zone '$z'..."
    eval curl $curlpar -Fname=$z https://www.buddyns.com/api/v2/zone/
done

Some users asked us if they can add IP addresses for multiple primary DNS servers in their BuddyNS account, so that if their "primary primary" dies, BuddyNS can still retrieve their zones from other ones.

We do not support this and warn you of the conceptual and technical risks that such architecture introduces.

Here's a simple, healthy way to handle the problem. If your master fails for a short time, relax about BuddyNS: your downtime can stretch 30 straight days (or more, contact us) and BuddyNS will keep running your zones undisturbed.

The case where you must unavoidably edit your zones during downtime of your primary are hard to imagine. Assuming they happen, just enter your BuddyNS account and update the IP of your primary to your intended "backup" server. BuddyNS will re-sync with the new primary within 2 minutes.

Downtimes of your primary long enough to justify such handling should be more unique than rare.

Our general policy is to minimize e-mails.

Our systems contact you automatically only about events essentials to your service. For example, you're e-mailed when your traffic quota is close to running out or when major issues are detected at your primary server.

Our team sends you e-mails relevant to your account. For example, we may e-mail you if your account mostly runs brazilian domain names and we launched a new Point of Presence in South America. These occur with minimal frequency.

We never e-mail you, for example, about new offers or new services.

Opt-out — your zone replication relies on automated notifications: to stop receiving them, log into your BuddyBoard and press the big red "DELETE ACCOUNT" button (this terminates DNS replication for your zones). If you forgot your password, find it in your account creation e-mail (Subject: "Hello from BuddyNS: your BuddyBoard account"), or use password recovery if you changed it.

We get out of our way to emphasise the importance of a reliable contact. Take a minute to trace back why this happened and how you can prevent it from happening again. Did you choose a disposable e-mail contact? Did you use a personal contact for a role?

You have 2 options for recovering your account:

• if you need to recover access from an admin who left your company, contact her and ask to log into the BuddyBoard and replace her e-mail address with yours. If you have this option, this is the simplest and quickest way. Once the account is associated with your e-mail address, you can use password recovery to set a new password.
• if you no longer have access to the former account, we can forcibly set the e-mail address for you only after we could authenticate you as owner of the zones hosted in the account. In order to do this, add a record "bdns-YYYYDDMM.yourzone.com" (replace with current date) for each of the zones you want to reclaim access for. Then write to our support: include the list of zones to take over, and the new email address you want to access them with. We'll send you the relevant login data.

Domain names are sensible assets. The cumbersomeness of this process is what it takes to protect them for you.

Vanity DNS allows you to use BuddyNS servers to secure your DNS, but display them to the public with your own names (e.g. ns2.yourdomain.com as opposed to b.ns.buddyns.com), so that your DNS appears to be run entirely by your own infrastructure.

Vanity DNS is a feature for Advanced Users only. To get Vanity DNS, create an account at BuddyNS, then upgrade it with the Subscribe button on the BuddyBoard.

Once your Vanity DNS option is enabled for your account, BuddyNS provides you with instructions and tips to setup Vanity DNS.

Vanity DNS requires an extra maintenance burden on your side: only enable it if you're ready to take it.

BuddyNS automatically generates invoices for each payment incoming if your billing data is available, and lists them in your BuddyBoard. If you need invoices, be sure to enter your billing data in the BuddyBoard (see "Settings") prior to activating your subscription.

If your organization is based in the European Union, we encourage you to enter your VAT number in VIES-compatible format, e.g. FR12345 as opposed to 12345.

Custom payment schedule

The BuddyBoard allows you to pay monthly or yearly. If your subscription is < 9 $/month, BuddyNS automatically increases the periodicity to 2 or 3 months until this value is reached. If you wish to pay with different schedules, e-mail us at support@buddyns.com and mention your BuddyNS username and desired schedule. We'll prepare the schedule for you; it will appear as a Custom Offer in your BuddyBoard, when you press the Subscribe button.

Paying without PayPal

We accept payments via bank transfer for amounts over $100 or € 80. They are normally free of charge within the European Union (ask your bank for SEPA), and expensive from the rest of the world. If your bank charges anything, such costs are up to you, so make sure to correct the transfer amount correspondingly. E-mail us at support@buddyns.com with your BuddyNS username and your payment needs for further details. We do not accept payments via cheques as they are overly complex to handle internationally.

Payments in € / EUR / CHF

We accept payments in Euros and CHF for amounts over $100 / € 80 / CHF 100. These can occur via bank transfer only. Contact us at support@buddyns.com with your BuddyNS username, your desired service parameters (number of zones, traffic, and optionally GeoStats), and periodicity. We will provide you with an invoice with the amount to pay. We refer to the European Central Bank's data for the exchange rate.

Log into your PayPal account and cancel the subscription you created for BuddyNS.

BuddyNS will downgrade your account to Free User after the expiration of your last payment period. Notice that Vanity DNS is not available for Free Users, so you need to reconfigure the delegation of your zones with BuddyNS own names. If not, BuddyNS will keep stop fetching new versions of your zones until this is fixed.

If you wish to terminate your account altogether, log into the BuddyBoard and use the Delete account button.

To change your service options, simply click the Subscribe button inside your BuddyBoard, choose your new options, and proceed to checkout. This will create a new recurring payment profile at PayPal, and BuddyNS will take care of blocking the old one (do verify this from your PayPal account).

You can both upgrade and downgrade your options. Changes take effect immediately. For example, if you upgrade because you ran out of traffic, your traffic will be restored within seconds.

BuddyNS helps you with that in two ways:

• with traffic consumption notifications;
• with BuddyBoard's Estimated traffic predictor;

The former just hit your specified e-mail automatically when 60%, 90%, 100% of your traffic quota is reached.

For the latter, just set up your zones and keep an eye on the Estimated traffic predictor in your BuddyBoard, "Account" pane.

This predictor gives you a linear projection of your latest traffic onto the whole month. Because DNS traffic floats (lower overnight and in week-ends), longer periods give a more accurate estimation. Two weeks is usually good.

After you accurately determined your estimated traffic, get a traffic quota that's between 1.5x and 2x that value.

You can change your quota anytime, just re-subscribe for the new value. The change takes effect immediately.

Here's some hints if your DNS traffic looks suspiciously high:

• Check if one of your domains just got a publicity exposure (slashdotting).
• Most DNS caches pick destination servers based on best response time.
• DNS resolvers first contact destinations given by the parent's glue.
• You may trade traffic with longer TTL values, especially on NS records.
• You may trade traffic with reliability by delegating less BuddyNS servers.

If you have reasons to exclude these, you have probably been targeted by a network scan or spam attack. These last few hours to a few days, and generate many tens of thousands of traffic.

BuddyNS implements logic to curb traffic incurred by scans and attacks, but since they are extremely hard to distinguish from regular traffic, some do get through.

If your normal traffic is well beneath your quota, these are unlikely to deplete it. If your normal traffic is over half your quota, and you want to prevent these from making you deplete it, you need to subscribe for a larger quota.

GeoStats help you early detect these cases. On exceptional need such as forensics, you can request us your traffic logs for your own analysis (availability is not guaranteed). We restrict these requests to Advanced Users as the volumes of traffic we deal with make the operation extremely time-consuming on our side.

As it's designed, the DNS system treats all nameservers a zone is delegating to as peers: equivalent and indistinguishable. So DNS doesn't give you a way to control priority or failover of nameservers: all nameservers get some DNS traffic all the time. However, these technical tweaks may get you some results:

• Change your TTL (time-to-live) values to affect the total amount of DNS traffic for your domains. Increase TTLs of all your DNS records, especially NS records, to reduce DNS traffic. This will cost you longer propagation times for future DNS changes. We recommend to avoid TTLs longer than 1 day (86400 seconds). In some cases, depending on your traffic patterns, changing TTLs will not significantly affect your traffic.
• Change the ratio of BuddyNS servers you delegate to. If you delegate your zones to 6 servers, 3 of which from BuddyNS, then statistically BuddyNS gets 50% of your total traffic (3 out of 6). Give up one BuddyNS server and BuddyNS gets 40% only (2 out of 5). Several factors can skew this, e.g. many DNS resolvers choose servers by performance instead of randomly.

With billions of queries each day scattered across many servers, the information on individual zones' behavior dives deep into our archiving systems in a matter of hours. Extracting this answer would require transferring, expanding and processing terabytes out of the archives.

This makes it extremely time consuming a task (hours). We reserve this procedure for forensic cases only, please do not ask us to do this.

In exceptional cases, we can made a short-time sample of real-time traffic, which is typically enough to show how much each zone generally contributes to your account's traffic. This requires quite some time from our Level 3 team, so we reserve the service to Enterprise users. We may exceptionally serve Advanced users too, if you can provide substantial motivation for having this information. If you got DDoSed, or you have many zones and need to select which ones to track for GeoStats, we'd come to help.

BuddyNS stops responding to incoming queries for your zones once your traffic quota is used up. Depending on your setup, this results in:

• Delays or timeouts when accessing services associated with your domains.
• Global unreachability of associated services if your primary DNS becomes unavailable.
• Global unreachability for domains delegating exclusively to BuddyNS.

BuddyNS takes great care in keeping you informed on traffic consumption. You receive notifications when your traffic reaches certain relevant thresholds, and you additionally receive a free notification via SMS as well if you do run our of quota (that's why we recommend registering a mobile phone number in your BuddyBoard).

Your traffic gets automatically unlocked as soon as you upgrade to a suitable traffic quota.

We have an additional process for outstanding circumstances of DNS abuse. If you ignore all notifications, run out of your quota, and your account continues to produre traffic past 250% of your quota, we send you a final abuse notification, with instructions and a few days time to address the problem. If no action is taken before the deadline, and you don't establish contact with our support, we initiate a case of Internet abuse and null-route your zones, answering all queries for them with 127.0.0.1 and making associated services appear as unavailable.

Yes, the plug-in installs and runs fine on both cPanel/WHM full and cPanel DNSONLY.

Yes. Starting with v2016060601 of our integration plug-in, you can point multiple cPanel servers to the same BuddyNS accounts, which serves all their zones collectively.

You can also run "mixed" BuddyNS accounts with some zones being controlled by cPanel/WHM servers, and some controlled manually.

You can tell your cPanel integration plug-in to exclude some zones from synchronization. These zones will be not removed if only found at BuddyNS, and not be added if only found on cPanel.

See Selecting which zones to synchronize for more details.