Solved Changed app to use bare domain, stuck Waiting for DNS propagation

[ryan]

I had Nextcloud set up as a subdomain. Since that's the most common app I use I changed it location to use the bare domain but it's been stuck ever since.

Feb 15 22:25:41 box:dns/waitfordns isChangeSynced: mydomain.tld (A) was resolved to 192.64.119.68,68.183.16.247 at NS dns1.registrar-servers.com (156.154.132.200). Expecting 68.183.16.247. Match false

So instead of just 68.183.16.247 it's getting back 2 IP addresses separated by a comma. As fas as I can tell DNS is configured correctly. Any ideas?

At this point I can't access the app and I can't change it back to the old subdomain. When I ping mydomain.tld from the command line it works. I'm not sure where the 192.64.119.68 address is coming from.

[ryan]

Ahh there was a "URL Redirect" record in Namecheap that was causing the problem. It wasn't obvious because it didn't have the IP address in the record but once I deleted that it worked. Thanks!

[robi]

log into your DNS management and remove the 192. record.

[ryan]

Ahh there was a "URL Redirect" record in Namecheap that was causing the problem. It wasn't obvious because it didn't have the IP address in the record but once I deleted that it worked. Thanks!

[jdaviescoates]

@ryan I just had almost the exact same issue using Gandi too. Thankfully the solution suggested by @robi worked immediately.

In my case I was adding a www redirect to a domain, but Gandi had already auto-created a www CNAME redirect.

I wonder if there is something @staff can do to automate this? I would expect it to find the existing www entry and to ask if I want to overwrite it (I did get a warning when first adding the domain and said it was OK to overwrite, so not sure why the pre-existing www CNAME survived and blocked the app from running)

[girish]

@jdaviescoates mm, good idea. We should probably look for CNAME records as well when looking for "existing record" instead of just A records.

[girish]

Added this check in the next release - https://git.cloudron.io/cloudron/box/-/commit/3f633c9779455c38df1223495974afbf2b1fe074

[caleno]

@girish After update I get error when propagating DNS. Or at least I thinks it is related because it worked before.

It is a subdomain pointing to a CNAME (duckdns) and it complains on all nsX.hyp.net.

Apr 09 11:33:38 box:dns/waitfordns resolveIp: Checking if xxx has A record at xxxx
Apr 09 11:33:38 box:dns/waitfordns resolveIp: Checking if xxx has CNAME record at xxxx
Apr 09 11:33:38 box:dns/waitfordns resolveIp: Resolving xxx CNAME record xxx
Apr 09 11:33:38 box:dns/waitfordns isChangeSynced: NS ns1.hyp.net (151.249.124.1) errored when resolve xxx (A): Error: queryA EREFUSED xxx
Apr 09 11:33:38 box:dns/waitfordns waitForDns: xxx at ns ns1.hyp.net: not done
Apr 09 11:33:38 box:dns/waitfordns Attempt 7 failed. Will retry: ETRYAGAIN

Final error message

An error occurred during the install operation: DNS Error: DNS A Record is not synced yet: ETRYAGAIN

[girish]

@caleno said in Changed app to use bare domain, stuck Waiting for DNS propagation:

After update

Do you mean you patched the server manually? We have not pushed an update with the code changes yet.

[caleno]

@girish No I've not patched manually, I have assumed sorry
I assumed the latest update was with the CNAME/A-record fix was live.

The thing was that my home server has been offline for a while and when I started it up it updated to from v7.0.4 to v7.1.3 then v7.1.3 to v7.1.4.

After that the DNS propagation didnt work any longer, as it had done before.