Vultr offers free DNS hosting for customers' domains. The nameservers are on an AnyCAST network and ensure fast DNS resolution. You are not required to use Vultr DNS when using other Vultr services, but it's fast, free, and easy to use. Here's how.
Click the Add Domain menu.
Enter the domain name and default IP address. Click Add.
The created domain has default A, MX, and NS records, and a wildcard CNAME for the domain.
To add DNS records, use the fields at the top of the DNS record list.
Fill in the appropriate values, as described below, then click the + icon in the Actions column. All records use the TTL value, which is is the "time to live" value, or the amount of time other DNS servers cache the DNS record. You do not usually need to modify this value.
Change your domain's nameserver (NS) records, at the domain registrar where your domain name was purchased, to Vultr's primary and secondary name servers:
Only these two nameservers should be listed for your domain at your registrar. Delete any other nameservers to prevent conflicts. The specific instructions vary depending on your registrar, we recommend searching for "register nameserver ns records at YOUR_REGISTRAR_NAME" to locate step-by-step instructions for your registrar. Some registrars refer to this setting as your "personal nameservers, "custom nameservers", or "authoritative nameservers".
👉 When you change your domain's NS records to Vultr's name servers, all domain services are affected. Make sure your Vultr DNS records are correct before updating the NS records at your registrar.
An A (Address) record points the domain or subdomain to an IPv4 address.
AAAA (Quad A) records works the same as A records, except for IPv6.
The CAA (Certification Authority Authorization) record specifies which certificate authorities can issue certificates for the domain.
CNAME (Canonical Name) records create aliases that point to A or AAA records. They can also point to CNAME records, but this results in multiple, inefficient DNS lookups.
foo.example.org is now an alias for bar.example.org.
MX (Mail Exchanger) records direct email to a mail server. MX records always point to a fully-qualified domain name, never to an IP address.
Multiple MX records, pointing to multiple mail servers, may exist for example:
SMTP servers will attempt delivery to mail.example.org (priority 10) first. Then, if delivery fails, mail2.example.org.
The NS (Name Server) record specifies the authoritative nameservers for a domain or a subdomain.
Vultr correctly sets the NS records to the default name servers when you create a DNS zone. The default name servers are:
Do not change these records unless creating a "vanity nameserver". If you create vanity nameservers, there is no guarantee that the IP addresses for
ns2.vultr.com won't change in the future.
SRV (Service) records assist with service discovery for protocols such as VoIP and LDAP.
An SSHFP (Secure Shell fingerprint) record identifies SSH keys that are associated with a hostname. You should secure SSHFP records with DNSSEC.
There are four different algorithms, each represented by an integer:
There are two fingerprint types, represented by an integer:
You can use ssh-keygen to generate SSHFP records with the -r parameter, followed by the hostname.
$ ssh-keygen -r test.example.org test.example.org IN SSHFP 1 1 65809317c6510920be418551eb9978b830f82935
TXT (Text) records can store arbitrary string attributes for various purposes.
Use the Zone Settings tab of the Manage DNS Domain page to modify SOA information.
The following limitations apply to Vultr DNS:
Vultr allows you to enable DNSSEC for any domain on your account. Navigate to the Zone Settings tab within the Vultr DNS control panel and toggle the DNSSEC switch on.
You will have to provide your domain's registrar with the DS records listed on the Zone Settings page to finish DNSSEC setup. These records are unique to each domain, and cannot be recovered in the event you disable DNSSEC.
Once the records are set with your registrar, verify the DNSSEC setup with a tool like DNSViz.
Vultr DNS cannot be used with cPanel in an automated fashion. If you run a cPanel server and plan on using Vultr DNS, you will need to manually add/edit your DNS zones and records. cPanel DNS clustering does not support Vultr's API.
The Vultr API offers several endpoints to manage DNS.