https://www.fiscaltransparency.net works fine, however, https://fiscaltransparency.net (without www) isn’t working and going to a 404 page.
I have set the A records as shown here:
It’s been a day and the site (non-www) is still not loading properly. 
Can someone check what settings might be wrong?
Thank you!
Welcome to the Cloudlfare Community. 
I am curious as to what the visible warnings 
are informing us about.
Your screenshot shows your hostnames as proxied, but DNS lookups return the IP shown in your host records. Are you using a partner integration from Blueshost (or another Newfold Digital/EIG brand)? I am wondering if that may be causing their settings to override yours.
You have a couple of things off in your redirect. You may want to review the Community Tutorial.
A post was merged into an existing topic: DNS Record disappears again
Thanks for the response @epic.network!
This is what the sign shows:
Yes, the host is Bluehost.
The non-www site which doesn’t work, returns this IP: 162.241.225.23.
The www site which works, returns this IP: 162.241.225.33.
So trying to set both in DNS to 162.241.225.33. That is correct, right?
Do you have other suggestions? Should I talk to Bluehost again and see if they have some settings that are overriding Cloudflare settings?
I have followed the tutorial for the redirect, thank you!
Possibly. I would read their articles first.
@epic.network, thanks! Unfortunately, I can’t get further help from Bluehost. They said they can’t enable Cloudflare and install the SSL certificate because the IP address is not pointing to Bluehost.
I was trying to update the A record in Cloudflare to use the IP address that should point to Bluehost, but I’m getting SSL issue.
So I am in the loop.
I also try to set the nameservers to use Bluehost:
Not sure if I am even doing this correctly.
192.168.2.1 is part of a reserved IP range. It is unassigned ergo does not resolve to anywhere. See RFC 1166: Internet numbers
I don’believe the NS records are incorrect too — Cloudflare is your NS.
Bluehost likely can’t tell the domain is pointing to their servers because it is proxied.
@anon9246926 thanks for the response! I followed the tutorial that was shared previously for redirection, that’s why I used the dummy IP 192.0.2.1. 
So should I remove the NS records I added?
The A records I added aren’t taking effect, it’s still showing the wrong IP address 162.241.225.23, which should be 162.241.225.33.
Is my setup correct?
Not sure what I should do next.
Thanks for the help!
There is no RFC 1918 address in that zone. 192.0.2.1 is from TEST-NET-1 as described in RFC 3330. It is referenced in Cloudflare documentation for use as a dummy IP when a placeholder is needed for a proxied hostname that will only be used by a redirect.
That is the odd part. Despite showing as proxied, DNS is resolving as an IP in a Bluehost allocation.
Probably. What NS records did you add? Can you show the entire entry for context?
What nameserver names appear in your Cloudflare dashboard for this zone?
Force of habit typing 192.168... instead of 192.0...
Is it possible @epic.network that the Bluehost network is seeing the Cloudflare IPs? Are you able to see in the Bluehost settings, or ask Bluehost support, that IP address(es) they are seeing the domain pointing to @mvtaguilaso ?
The domain does still show in ns1.bluehost.com
% dig @ns1.bluehost.com fiscaltransparency.net
fiscaltransparency.net. 14400 IN A 162.241.225.33
# AND
% dig @ns1.bluehost.com www.fiscaltransparency.net
www.fiscaltransparency.net. 14400 IN CNAME fiscaltransparency.net.
fiscaltransparency.net. 14400 IN A 162.241.225.33
@epic.network, is this what you want to see?
@anon9246926 , I am seeing this notice in the Bluehost settings:
They are also just asking me to check on these sites:
https://dnschecker.org/#A/fiscaltransparency.net
https://www.site24x7.com/tools/dns-propagation.html
which shows the IP address is 162.241.225.23.
If you check the IP address for the www-version of the site: https://www.fiscaltransparency.net, it points to this IP address: 162.241.225.33, which is what they are asking me to do, to update the A records, for the non-www version of the site.
This explains a lot! You should not have those Bluehost NS records in your zone. You also have the wrong Cloudflare nameservers assigned at your registrar. You can clearly see eve and santino in your screenshot, but emerson and savanna are set at the registrar.
@epic.network , unfortunately, we are having trouble accessing the account in the domain registrar. We are trying to reach out to the person who purchased the domain, but I don’t we can successfully get access to that. I have tried contacting the registrar (which is DomainSite, currently name.com), however, they are unable to change the records on their end without the account owner’s consent.
Would it be possible to change the nameservers to emerson and savanna here in Cloudflare settings instead?
That nameserver pair is already in use with this domain in another Cloudflare account. It is not possible to make your Cloudflare account use those nameservers. The purpose of the unique nameserver combinations is to prove domain ownership. You aren’t going to be able to resolve your difficulties until you have access to the domain management at the registrar.
Thank you @epic.network , I will ask who has already set this up in Cloudflare.
I learned a lot, thank you!!
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
