Troubleshooting: badauth, notfqdn, abuse and more
November 19, 2026
What the answers of the update address mean and how to fix each one.
The update address answers with a short text. Most routers show it in their log. These are the answers you may see:
| Answer | Meaning and fix |
|---|---|
| good <ip> | The address was changed to <ip>. Everything works. |
| nochg <ip> | The address was already <ip>. Nothing to do. |
| badauth | The token is wrong, expired or revoked, or the token has no UPDATE or RECORDS permission. Check that the token is in the Password field without spaces, or create a new one. |
| notfqdn | The hostname is missing or is not a full name. Use the complete hostname, for example your-hostname.<shared domain>, in the hostname parameter. |
| nohost | This hostname does not exist in your account. Check the spelling. |
| !yours | The hostname exists, but this token is not allowed to use it. Create a token for this hostname or for all hostnames. |
| numhost | Too many hostnames in one request (the limit is 5). Split the update into several requests. |
| invalid_ip | The address is not a valid public IPv4 or IPv6 address. Private addresses (192.168.x.x, 10.x.x.x) are not accepted. Send the public address or omit myip. |
| abuse | Too many requests or too many changes. Wait as long as the Retry-After header says (or a few minutes) and make the device update only when the address changes. See the article about limits. |
| suspended | The hostname is paused, for example because it was not confirmed in time. Sign in to the dashboard and confirm it. |
| conflict_cname | The hostname itself is set as a CNAME record, so it cannot also hold an IP address. Remove the CNAME in the dashboard. |
| dnserr | A temporary error on our side. Try again in a few minutes. |
| badagent | The program that sent the request is blocked. Use a standard client (see the router guides). |
If the router reports success but the address is wrong
- Behind a second router or carrier-grade NAT, the address your router sees is not public. Let the device send the public address or omit myip.
- Open the hostname in the dashboard and compare the IP address with the one on a "what is my IP" page. Changes can take up to the record's TTL to reach every resolver (120 seconds by default).
- Check that the update runs at all: look at the log of your router or script.