Domain name not pointing to the correct ipv4 address

What is the name of the domain?

meije.xyz

What is the error number?

NS_ERROR_UNKOWN_HOST

What is the error message?

Hmm. We’re having trouble finding that site. We can’t connect to the server at www.meije.xyz. If you entered the right address, you can: Try again later Check your network connection Check that Firefox has permission to access the web (you might be connected but behind a firewall)

What is the issue you’re encountering

I cannot visit my website when typing the domain name in my browser

What steps have you taken to resolve the issue?

  1. I have bought my domain name on namecheap.
  2. I have changed the DNS setting on my namecheap account as advised by cloudflare (I have turned off DNSSEC and in nameservers section, I chose “Custom DNS” + I added the two nameservers provided by cloudflare: chance.ns.cloudflare.com and sloan.ns.cloudflare.com).
  3. I have waited more than 24 hours.
  4. I have added a DNS record on cloudflare:
    record type: A
    record name: @ (or meije.xyz)
    ipV4 address: 51.159.161.240
    proxy status: proxied
    TTL: auto
  5. I have waited several days (more than 24 hours).
  6. when I try “nslookup meije.xyz” or “dig meije.xyz” in my terminal, I get the following IP address: 127.0.0.53 or 104.21.87.8 or 172.67.139.30. But it does not seem to point to the IPV4 address I chose (51.159.161.240).

What feature, service or problem is this related to?

DNS records

This record is set to be proxied :orange: by Cloudflare. If you wish to connect to the IP directly instead you can set the record to DNS Only :grey: in DNS.

That record redirects to www.meije.xyz which does not exist in your DNS.

 curl -Ik https://meije.xyz
HTTP/2 301 
date: Wed, 23 Apr 2025 14:43:21 GMT
location: https://www.meije.xyz
server: cloudflare
cf-ray: 934e21fb792cc457-EWR
alt-svc: h3=":443"; ma=86400
2 Likes

Thank you VERY MUCH @cscharff ! I had just tried to remove cloudflare proxy and it now works: well, it works when I type the following url: https://meije.xyz and not https://www.meije.xyz. I suppose I now need to add a www.meije.xyz redirection to meije.xyz (using a CNAME DNS record, maybe?).

I still have a question, though. I somehow understood that setting the proxy status to “proxied” rather than “DNS only” was a better practice. What is your opinion on that? (I am going to dig further in the documentation to understand that point).

If you want to use Cloudflare to protect your site and Cloudflare’s other features, the record needs to be proxied.

If you want to see, or your host requires to see, the DNS record resolve pointing to the origin, then you have to use “DNS only”.

You can’t do both, see…

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.