Thanks to the
now dns CLI command, managing existing DNS records with Now is simple.
However, this only applies to domains you bought via Now
or domains configured with our global DNS service
In the examples shown below, the placeholder
zeit.rocks represents a domain of your choice that was registered with
now domains or
now alias. Here are the main sub-commands you can use:
Lists all the DNS records available for this domain. The list doesn't include records generated automatically by the nameserver (like a default
SOA record or
A / AAAA records created automatically for
Adds a DNS record to a domain of your choice. The following record types are currently supported:
This is the syntax for the
now dns command.
now dns add <domain> <name> <record type> <value> [mx_priority]
<domain> is the domain name
<name> is the subdomain that will be prefixed to
@ refers to a domain without any prefix)
<record type> contains one of the supported record types shown above
<value> indicates the value for the record (like an IP address or a hostname)
[mx_priority] sets the priority of a certain MX record and can therefore only be used in conjunction with this record type
now dns add zeit.rocks ext A 127.0.0.1
Creates an A record that makes the subdomain
ext.zeit.rocks resolve to the server located at the IP address
now dns add zeit.rocks @ MX mail.awesome-now.us 10
Creates an MX record which makes the mail server located at
mail.awesome-now.us responsible for handling emails sent to an address suffixed with
now dns add zeit.rocks @ CAA '0 issue "comodo.com"'
Creates a CAA record
that allows to issue certificates using Comodo
and any sub domain under it.
In this case, you'll be in charge of certificate management for your domain.
Most probably, you'll need to use
CAA records to:
- use a custom certificate for your Now deployment with `now certs replace`
- run an app outside of Now with TLS for a sub domain
Removes a record by ID, which is shown in the
now dns ls listing. Note that it may take a couple of hours before the change is fully propagated across our infrastructure.
As of now-client
, it comes with API wrappers for managing the DNS records within your own application.
The endpoint is called
and is available in our REST API