lookup domain on ip: no such host

[qdm12]

lookup domain on ip: no such host

[qdm12]

The Docker healthcheck basically runs a DNS lookup of the hostname, on this line.

Is it a new hostname with a new IP address? If so, it might work in a few minutes so that it has time to be published on your DNS server (ISP or i.e. Google/Cloudflare etc.).

Otherwise, can you try

docker run -it --rm alpine:3.10 nslookup <your-domain>

and report back the (redact your IP address etc.) output?

[v0idp]

nslookup: can't resolve '(null)': Name does not resolve nslookup: can't resolve 'domain.me': Name does not resolve

I mean my domain isn't redirecting anything. It's not supposed to do so. I only use the wildcards subdomain for my services in docker with traefik.

[qdm12]

Can you try with https://mxtoolbox.com/DNSLookup just to be sure it's not a LAN DNS server issue?

You can try by setting to i.e. 127.0.0.1 (localhost) on the Cloudflare website, then restart the ddns-updater container (or wait 5 minutes) and see if the IP address is changed on their website. If it is, then it may be a Cloudflare issue (I had the case with Namecheap not publishing my updated record for 6 hours).

[v0idp]

Like I said I have no dns record for the domain itself. Only for the * subdomain wildcard. but the healthcheck checks for the domain. Not sure if I'm correct here.

Also the healthcheck with the IP (it's showing an LAN ip anyways)
{"node_id": 0, "error": "lookup domain.me on 192.168.178.1:53: no such host"}

[qdm12]

Hm maybe you need to have an A record for host @ as well as host * (wildcard). I had to this on Namecheap to have a wildcard record. I personally don't use Cloudflare so I am not sure, and I tend to not use wildcards either, so I might not be the best person to ask 😆

But if you add a record for this same domain with the host @ the healthcheck will not complain anymore I guess. Or you can use subdomains instead of wildcard (what I do, it's better security wise as well).

[v0idp]

How does it improve the security ?

[qdm12]

Actually I think if you use Traefik you need a wildcard record not to go crazy! I have seen bots trying to access strange subdomains in my logs so I prefer to keep it restricted to what I need. On the other hand, having a wildcard record may make it harder for bots to know what subdomains you actually use which is nice.

Anyway, from the Namecheap website

NOTE: A wildcard DNS record does not cover a root domain (e.g. yourdomain.tld), thus you will need to create a record for @ host additionally.

However my code might be wrong, would you mind trying resolving a.yourdomain.com? That should work with the wildcard.

docker run -it --rm alpine:3.10 nslookup a.<your-domain>

[v0idp]

it resolved something. seems to work with subdomain just fine. I am using Namecheap but my DNS is cloudflare.

healthcheck seems to make no sense if I don't use my root domain.

[qdm12]

I just changed my code, you are right. It now tries to resolve any.domain.tld instead of domain.tld if you use a wildcard record. So the Failure message (in the UI, logs, healthcheck.. and Gotify) should not show anymore. Thanks again for pointing this out.

[v0idp]

thank you !

[qdm12]

It's still building the Docker image on Travis. It will probably take another 20-30 minutes (compiling for all CPU architectures is slow...). You can then try restarting the container with the latest image you can pull with

docker pull qmcgaw/ddns-updater