Running your application
DNS records
How to read and change the records of your domains at Bunny DNS or Scaleway DNS, from the console or the command line.
When the DNS of a domain is at Bunny DNS in your own bunny.net account, or at Scaleway DNS in one of your connected Scaleway projects, you can read and change its records in Brewless: on the DNS page of the console, or with the dns: commands of the command line client. Both work the same way, and every zone says which of the two it lives at. A change goes straight to that provider. Brewless keeps no copy of your zones; every page and every command reads the zone as the provider has it at that moment.
Which zones
Brewless shows and changes only the zones it manages for one of your environments. Take a zone over on the Resources page of the environment it is for; it then appears on the DNS page, and on the organisation's Resources page with a link to its records. Adding a domain whose zone sits in a connected account takes that zone over too, and says so. Other zones in the same accounts are never read or changed.
At Scaleway DNS a zone is named by its full domain, such as example.eu or shop.example.eu for a subzone. The zone Scaleway keeps for the private networks of your project is not a domain and is never offered. A Scaleway key without access to Domains and DNS simply shows no zones there.
In the console
Open DNS in the sidebar. Each zone shows its provider, Bunny DNS or Scaleway DNS; pick one. The records are listed with their full name, type, value and TTL.
- Add a record with the form below the list. Write the name as
www, aswww.example.eu, or as@for the domain itself. - Change a record: its values move into the form; save the change.
- Remove a record: Brewless asks first. Brewless keeps no copy to put back.
Members of your organisation can read the records. Adding, changing and removing take the owner or admin role, the same as adding a domain.
From the command line
brewless dns:list # the zones Brewless manages, with their provider
brewless dns:list example.eu # the records of one zone, with their ids
brewless dns:add example.eu a www 203.0.113.7 --ttl=300 # add a record
brewless dns:add example.eu mx @ mx.example.eu --priority=10
brewless dns:update example.eu 1234 --value=203.0.113.8 # change what you give, keep the rest
brewless dns:remove example.eu 1234 # asks first; --force does not
A record is named by its id at the provider: a number at Bunny DNS, a UUID at Scaleway DNS. dns:list shows it.
dns:remove asks before it removes a record. With --no-interaction it cannot ask and fails unless you pass --force.
Record types
You can add and change A, AAAA, CNAME, TXT, MX, SRV, CAA and NS records. An MX record takes a priority; an SRV record a priority, a weight and a port; a CAA record flags and a tag (issue, issuewild or iodef). The TTL is between 15 and 604800 seconds.
Records of other types, such as a redirect or a script at Bunny DNS, or an ALIAS at Scaleway DNS, are shown and changed at the provider. A record that leads one of your domains to the pull zone of an environment belongs to that domain: it is made when you add the domain. At Bunny DNS it is not changed from the DNS page.
At Scaleway DNS, host names are written with a closing dot and TXT values in quotes. Brewless shows and takes them without, as at Bunny DNS, and writes them the way Scaleway wants.
Note
Adding a record that is already there, with the same type, name and value, adds nothing: you get the record that is there. A change the provider refuses, such as a
CNAMEnext to other records on the same name, comes back in the provider's own words and changes nothing. Brewless never makes a zone at Scaleway DNS by changing a record: only zones that exist are changed.
The audit trail
Every record that is added, changed or removed is written to the audit trail of the organisation, with who did it and the record as it was and as it became.