BWEZE Docs

DNS

Host a zone on BWEZE's nameservers and manage its records from the dashboard or the API.

BWEZE runs authoritative DNS (PowerDNS) on ns1.bweze.com and ns2.bweze.com. Domains you buy through BWEZE are delegated to them and wired to your project automatically. You can also host any other zone there and manage its records yourself.

Nameservers not public yet

ns1.bweze.com and ns2.bweze.com do not answer on the public internet yet. You can create zones and records now; don't point a live domain's nameservers at them until this notice is gone. To use a domain you own today, connect it with records at your current DNS provider.

Zones

# Add a zone
curl -X POST https://api.bweze.com/v1/dns/zones \
  -H "authorization: Bearer bw_sk_..." -H "content-type: application/json" \
  -d '{ "zone": "example.com" }'

# List zones, read one
curl https://api.bweze.com/v1/dns/zones -H "authorization: Bearer bw_sk_..."
curl https://api.bweze.com/v1/dns/zones/example.com -H "authorization: Bearer bw_sk_..."

Reading a zone returns its serial, whether it is signed (dnssec), and its record sets (rrsets), without the SOA. Adding a zone that exists is 409 zone_exists. Delete one with DELETE /v1/dns/zones/{zone}.

Records

Records are managed as record sets: every record with one name and one type. Setting a record set replaces all of its records at once.

curl -X POST https://api.bweze.com/v1/dns/zones/example.com/records \
  -H "authorization: Bearer bw_sk_..." -H "content-type: application/json" \
  -d '{ "name": "@", "type": "MX", "ttl": 3600, "records": ["10 mx1.mailhost.com.", "20 mx2.mailhost.com."] }'
FieldValue
nameThe name in the zone; @ is the zone's apex
typeA, AAAA, CNAME, TXT, MX, SRV or NS
ttlSeconds, 60 to 86,400; default 300
recordsThe values, one string per record

Delete a record set with DELETE /v1/dns/zones/{zone}/records and a body of { "name": "...", "type": "..." }.

The dashboard's DNS page does the same, and exports a zone as a BIND zone file.

Permissions

ActionPermission
List and read zonesdns:read
Add a zonedns:create (not for tokens limited to some zones)
Set recordsdns:update
Delete records or a zonedns:delete

A token limited to some zones sees and changes only those. See API tokens.

On this page