Hi, @sanjitchak. I don’t show this domain configured for any Netlify sites.
For example, the URL doesn’t below work. It would if a) someone is logged in as a member of the team where is is configured and b) the configuration existed (but, again, it doesn’t).
Hi, @edwardnewton. I’m showing cleanily.com and www.cleanily.com both returning the same site and both have a working SSL certificate (the same SSL certificate with a start date of Jan 12 13:28:33 2020 GMT).
If you are still seeing issues would you please send us the x-nf-request-id header for the non-working response?
Note, if this header is unavailable for any reason, would you please send us the data it replaces? That information being:
the complete URL requested
the IP address for the system making the request
the IP address for the CDN node that responded
the day of the request
the time of the request
the timezone the time is in
Also, if there are any questions about this reply, please let us know.
I’m showing the opposite configuration under custom domains, which is that www.cleanily.com is set to be the primary domain and, because of this, cleanily.com redirects to the www subdomain above.
If you want www.cleanily.com to redirect to cleanily.com, please go to the site’s “Custom domain” settings in Netlify. Then click the “…” to the right of cleanily.com and then choose “Set as primary domain” in the dropdown menu. This should cause www to redirect the the apex/root domain.
If this doesn’t work (or there are other questions), please let us know.
Chrome hides the www in the browser address bar, but it is still there. We cannot control what Chrome shows though. Chrome also hides the https://. There are many things about Chrome I love but hiding the actual URL used isn’t one of them.
We are also experiencing the same issue with our apex domain – aceanalytical.com. The client manages the DNS through JustHost. The CNAME record we created for the ‘www’ subdomain works and was Verified in the Netlify dashboard. However, we tried a CNAME (Alias) record the apex domain and is didn’t work. Currently we’ve configured an A record for the apex domain pointing the Netlify server IP and it’s not working/propagating either. Any suggestions?
I’m showing both the www subdomain and the apex domain (aceanalytical.com) working for the Netlify site when I test now.
Why didn’t it work before? My best guess is that the previous records were being cached due to time to live (TTL) values in the DNS records themselves:
The only solution for this is usually to wait for the TTL to expire. There is more information about minimizing the impact of TTL values when making DNS changes here:
Please let us know if there are other questions and/or if it still doesn’t work for you when you test.
@luke The same is happening to me now. My apex domain doesn’t load or redirect and I have a “Check DNS Configuration” warning, but the DNS records are the default Netlify ones.
Hi, @AAA, and welcome to our Netlify community site.
What domain name (or names) is this happening for?
You can private message (PM) that information to one of our support staff and I’ve confirmed that PMs are enabled for your community login. Note, that only one person can see the PM and this will likely mean a slower reply than posting the information publicly. Please feel free to reply to however you prefer though.
Hi, @AAA, thanks for sending us the domain name. There was an issue on our side which has been corrected now. Both domain names (the www subdomain and the apex domain) work now when I test.
Would you please confirm the issue is resolved when you test now as well?