-
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lookup domain on ip: no such host #25
Comments
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? |
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. |
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. |
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) |
Hm maybe you need to have an A record for host But if you add a record for this same domain with the host |
How does it improve the security ? |
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
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> |
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. |
I just changed my code, you are right. It now tries to resolve |
thank you ! |
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 |
Hey there I've setup my domain with cloudflare and your ddns-updater in docker. Everything seems to work perfectly fine. it's updating my wildcard subdomain just fine but the docker container itself seems to "unhealthy" all the time and I get this log:
Any idea why this is happening ?
my config.json looks like this:
The text was updated successfully, but these errors were encountered: