Migrate from DNS-O-Matic¶

DNSbun is compatible with the DNS-O-Matic update API. Clients that already send DynDNS-style updates to DNS-O-Matic can use the same request format with DNSbun by changing the update endpoint and credentials.

Compatible request behavior¶

DNSbun supports the DNS-O-Matic conventions used by existing update clients:

HTTPS requests using HTTP Basic authentication.
GET and form-encoded POST requests to /nic/update.
The DNSbun all.dnsbun.com hostname target for all configured destinations.
The DNS-O-Matic all.dnsomatic.com hostname target as a backwards-compatible alias.
An omitted hostname as another way to target all configured destinations.
A comma-separated hostname list for clients that update specific records.
DynDNS-compatible response codes.

Settings to change¶

Keep the existing DNS-O-Matic request format and replace its connection settings with the following values:

Setting	DNSbun value
Update endpoint	`https://update.dnsbun.com/nic/update`
Hostname for all destinations	`all.dnsbun.com`
Username	Your DNSbun username
Password	Your DNSbun password

Some clients have separate server and path fields, while others require the path and parameter placeholders in a single field. See the router guides for the exact fields supported by your device.

Existing clients configured with all.dnsomatic.com do not need to change that value. DNSbun treats it as an alias for all.dnsbun.com.

Verify compatibility¶

Send a test update and check the client's status. A successfully parsed request receives a DynDNS-compatible response such as:

nochg <address>

This confirms that DNSbun accepted the credentials, target, and IP address.

Roll back¶

Keep the original DNS-O-Matic settings recorded during migration. To roll back, restore the previous update server and DNS-O-Matic credentials in your client.