struggling to get my root domain website to resolve through a tunnel in certain browsers
PING IF YOU WANT TO ALERT ME TO YOUR REPLY
hello, i've been overhauling my website this last little while and i'm finally moving everything to my web server. everything works good locally, but when i set up the public hostname on the tunnel to point to my root domain, it fails to resolve in the browser (NS_ERROR_UNKNOWN_HOST in floorp, ERR_NAME_NOT_RESOLVED in chromium). strangely enough, the website seems to resolve just fine in vanilla firefox (both desktop and mobile), though it's slow in doing so; a LOT slower than when i was using a testing subdomain. dunno what's up with that.
anyways, are there any fixes for root domains that refuse to resolve/resolve slowly through tunnels? maybe i just need to set up and install a new tunnel and see if that works?
2 Replies
Support AI
PING
Based on the provided documentation, I'd like to suggest a few potential causes and solutions for the issue you're experiencing.
1. Mistyped domain or subdomain: Double-check that the domain or subdomain was correctly spelled in the request URL. (Source: https://developers.cloudflare.com/dns/troubleshooting/dns-issues/)
2. Missing DNS records: Ensure that you have the necessary DNS records in the DNS app of your Cloudflare dashboard, including existing subdomains records. (Source: https://developers.cloudflare.com/dns/troubleshooting/dns-issues/)
3. DNSSEC was not disabled before the domain was added to Cloudflare: If you haven't already, disable DNSSEC at your domain provider before adding the domain to Cloudflare. (Source: https://developers.cloudflare.com/dns/troubleshooting/dns-issues/)
4. Nameservers no longer point to Cloudflare: Verify that your domain's nameservers still point to Cloudflare's nameservers. (Source: https://developers.cloudflare.com/dns/troubleshooting/dns-issues/)
5. Unresolved IP address: Try reloading the page after a short wait to see if the problem disappears. You can also consider using Cloudflare's DNS resolver. (Source: https://developers.cloudflare.com/dns/troubleshooting/dns-issues/)
Regarding the slow resolution in Firefox, it's possible that it's related to the DNS resolution process. You can try testing the A record using multiple DNS resolvers with DNSSEC validation, as described in the documentation. (Source: https://developers.cloudflare.com/dns/dnssec/troubleshooting/#test-dnssec-with-dig)
As for setting up a new tunnel, it's worth trying, but I'd recommend checking the above potential causes first. If you're still experiencing issues, you may want to investigate further or try alternative solutions.
Sources
Feedback
Feedback has been submitted! Thank you :)
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
sorry, resolved. ended up being that i still had old A and AAAA records on my domain registrar's site when i was still using the domain for neocities hosting. all good now!
check your registrars everybody