New CF set up, all check god, but site is unreachable...? Help!


I have set up Cloudflare for this site:

solohappy . com

I changed the nameservers, from my host provider to Cloudflare’s nameservers, I got a confirmation from both that the nameserver change went fine.

When I check in whois, I also see the nameservers have changed. So it all looks good…

But when I go to my site, I can’t reach it.
I’ve tried this from different devices, mobiles, clearing cache, clearing cookies, restarting the whole device…but nothing, I can’t reach my site.

What can be the problem?
Could someone please help me?


Thank you for asking.

When I do the lookup, I cannot find any A records for your domain :thinking:

Did you configured your DNS tab and double-checked the DNS records?
Do you see some notice when navigating to the DNS tab at the top like on the below tutorial? :thinking:

Helpful articles:

Hello thank for your response.

I only followed the instructions I got from the CF set up.

Which DNS tab do you mean? CF of my host?

The DNS tab from the Cloudflare dashboard, here is the link:

You can manually add the missing DNS records, if any as it seems, however if you have an option to export the DNS records from your current web hosting provider interface, therefore you can easily import them to the Cloudflare (as a BIND formatted .txt file).

OK, and how do I know which records to add?

I’d suggest you to login into your web hosting interface / cPanel and navigate to the DNS zone or DNS management in one tab of your Web browser.
Also, login to Cloudflare dashboard and navigate to the DNS tab of your domain.

Therefrom, you can compare and check which one is missing and add a new one or edit the existing at Cloudflare DNS tab using above tutorials which I’ve linked.

OK, I will check this right now
One moment please

1 Like

Kindly, take your time as needed.
We’re here for further questions, troubleshooting and help :wink:

In the meantime, it seems like you’re doing it good :+1: responds, however it redirects to which is still missing.

So, you have to add another A (or also A @ - the at @ symbol just converts to the naked/root domain) pointed to the web hosting IP (usually it is the same as www) and make sure it’s proxied :orange: too.

I can see MX and TXT records are ok so far.

OK so I checked.

My Host’s DNS tab:
(I’ve added spaces in the urls as I cannot submit links)

A solohappy . com
AAAA solohappy . com
A www. solohappy . com
AAAA www. solohappy . com
A *.solohappy. com

Cloudflare DNS tab:

So if I understand currently, you are saying I should make the CF DNS tab look exactly my hosts’s DNS tab is this correct?

1 Like


However, from the best practices, I’d suggest you to use a real sub-domain/hostname like, or whatever else you’re really using, even like instead of the * wildcard DNS hostname (asterix symbol).

OK, so how should the whole entry line for these 2 records look when I type it in?

So what should I fiill in here?



From the above, should be like on the below picture:

Bravo! :slight_smile: now responds as redirect works too!

At least, on my end as far as I am testing it now.

In case it’s not working for you, it might be you’d have to wait a bit longer due to the DNS cache at your local ISP (and as you have recently changed your domain nameservers, the regular DNS propagation time usually takes up to 24-48 hours to complete).

In the meantime, you could try to:

  • Restart your router.
  • Try using a different Web browser, or try clearing your Web browser cache.
  • Try using a Private window (Incognito mode) or a VPN connection, if possible.
  • Try using your mobile phone (4G LTE, mobile data, cellular).

Otherwise, wait a bit longer as stated and it would propagate and work for you too :wink:

1 Like

OK thanks.
What about the 2 entries with “*”…do they need to be deleted?

You can ignore them for now, therefore as I mentioned if you’d have some kind of a sub-domain, you’d just add a new record and point it to the IP.
It’s more safer way than keeping a wildcard * hostname.

There is no need to add them to the DNS tab of Cloudflare dashboard.

OK great.

And what about email traffic, do I need to do something there?

As far as I can see, the MX records are good:

;ANSWER 300 IN MX 10 300 IN MX 10 300 IN MX 10 300 IN MX 10

Therefore, in your web app or e-mail client make sure you’re using the correct incoming/outgoing server with the assigned credentials for auth (or Webmail) from the “One” service provider.

In case you’ll encounter some issues, feel free to write back or create a new topic so we could troubleshoot and help you with it.

All clear, many thanks for your help!

Have a good day!

1 Like

I am happy to assist you! :wink: