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!