# Cloudflare DDNS bug

**URL:** <https://forum.alta.inc/t/cloudflare-ddns-bug/6405>\
**Category:** Routers\
**Tags:** bug-report, route10\
**Created:** [January 17, 2026, 7:51am UTC](https://forum.alta.inc/t/cloudflare-ddns-bug/6405 "2026-01-17T07:51:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![iker.saint](https://forum.alta.inc/user_avatar/forum.alta.inc/iker.saint/32/5112_2.png) [@iker.saint](https://forum.alta.inc/u/iker.saint)\
**Post date:** [January 17, 2026, 7:51am UTC](https://forum.alta.inc/t/cloudflare-ddns-bug/6405/1 "2026-01-17T07:51:25Z")

</div>

Hi, I want to report a bug in the DDNS config generated for Cloudflare. Currently, if you configure DDNS with Cloudflare, you have to provide a hostname with the following format `<record>@<zone>`, which creates a DDNS config like the following:

```auto
config ddns 'global'
        ....

config service
        option enabled '1'
        option service_name 'cloudflare.com-v4'
        option domain 'sub@domain.example'
        option username 'Bearer'
        option password 'MyUltraSecureToken'
        option use_https '1'
        option lookup_host 'sub@domain.example'
        option interface 'wan'
        option ip_network 'wan'
        option ip_source 'web'
        option ip_url 'https://manage.alta.inc/api/ip'
        option force_ipversion '1'

```

However, if you look closely, the “ **lookup\_host** ” also includes the @ symbol, which causes problems in the DNS query performed to resolve the current IP addr configured in Cloudflare, generating the following logs:

```auto
WARN : Get registered/public IP for 'sub@domain.example' failed - retry 3/0 in 60 seconds
     : #> /usr/bin/drill -V0 -4 -u sub@domain.example A >/var/run/ddns/cfg025996.dat 2>/var/run/ddns/cfg025996.err
WARN : NO valid IP found
WARN : Get registered/public IP for 'sub@domain.example' failed - retry 4/0 in 60 seconds
     : #> /usr/bin/drill -V0 -4 -u sub@domain.example A >/var/run/ddns/cfg025996.dat 2>/var/run/ddns/cfg025996.err
WARN : NO valid IP found

```

It’s pretty clear that the error is due to the **lookup\_host**  **field** , which is incompatible with the drill command, which expects a traditional hostname; if you modify the `/etc/config/ddns` file with the correct hostname for the field, the update works as expected.

Hopefully, this will help others and get fixed in the upcoming firmware.

---

<div class="post-metadata">

**Author:** ![Alta-cmb](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-cmb/32/5404_2.png) [@Alta-cmb](https://forum.alta.inc/u/Alta-cmb)\
**Post date:** [January 17, 2026, 8:03pm UTC](https://forum.alta.inc/t/cloudflare-ddns-bug/6405/2 "2026-01-17T20:03:33Z")

</div>

That’s correct, I fixed it so firmware will replace the @ with . for the lookup\_host field for Cloudflare.

Thanks for the report!

---

<div class="post-metadata">

**Author:** ![system](https://forum.alta.inc/uploads/default/original/1X/087669c3d7c0a6495087b41d6f385a6771f2231c.png) [@system](https://forum.alta.inc/u/system)\
**Post date:** [July 16, 2026, 8:03pm UTC](https://forum.alta.inc/t/cloudflare-ddns-bug/6405/3 "2026-07-16T20:03:40Z")

</div>

This thread has been automatically closed due to inactivity. If you believe you have the same issue, please create a new post describing your issue. Feel free to link to this post for context if desired.