DNS zones
Manage DNS zones served by runlot's nameservers from the CLI and the dashboard.
runlot dns create example.com --org me
runlot dns zones --org meDNS zones belong to an organization, not a project. That's why you pass --org instead of working from a project directory.
When you create a zone, we show you the nameserver addresses to register with your registrar: ns1.runlot.app and ns2.runlot.app. Domains bought through runlot are delegated to them from the start.
Records
runlot dns records example.comrunlot dns set example.com www CNAME app.example.com
runlot dns set example.com @ A 203.0.113.1 203.0.113.2
runlot dns set example.com @ MX "10 mail.example.com"
runlot dns rm example.com www CNAMEdns set replaces the entire record set for the given name and type. It does not add a record. To keep the existing values, list all of them along with the new value.The supported record types are A, AAAA, CNAME, MX, TXT, SRV, CAA, and NS.
runlot dns set example.com www CNAME app.example.com --ttl 5m--ttl takes a value in seconds or a time unit (300, 5m, 1h). The default is 300 seconds, and you can set anything from 30 seconds to 1 day.
Records we manage
You cannot edit the records used for custom domain connections and certificate issuance; editing them raises a managed_rrset error. Conversely, runlot never overwrites records you created.
Deleting a zone
runlot dns delete example.comTo proceed with deletion you have to retype the full zone name. This cannot be undone, so a simple y confirmation isn't enough.
Propagation time
Saved records reach the public nameservers within a few seconds. How long DNS caches take to refresh after that depends on your --ttl value.