I set up a free CF zone for one reason: I have a domain registered with another company, and I need to forward all traffic to another website. I changed the nameservers. Then I added the URL that I want to drive traffic to, but when I enter my domain name into a browser, I get the “Hm. Having trouble finding that” error message.
I saw that “Page Rules” do not work for zones that are being used for DNS only. Is that my problem? What does that mean? And how do I fix this?
Please note: I am not good at this. None of this stuff is familiar to me. Please be kind.
You will know a DNS record is DNS Only by the next to it. Page Rules only work with Proxied names. They will have next to them.
It is a lot easier for the Community to provide you with specific answers when you share your domain name. That will allow us to look things up on our own.
Wow - that was quick! Thanks. My domain name is lerissapatrickvoicedot com. The target URL is apps.voiceoverviewdocom/lerissa_patrick (with https: slash slash in front).
I couldn’t figure out the “preformatted text” option.
You can use the </> button in the message composition menu, or just type a backtick before an after the word or words. If you type `example.com` it will appear as example.com.
You appear to have not created any DNS record for your apex name, proxied or otherwise.
You will want to add an AAAA record for the name @ with the special discard IP of 100:: and make sure to leave it . Once saved, the @ record will appear as your apex name in the list. That is normal.
Type - AAAA
Name - </lerissapatrickvoice.com> (I typed @ and it filled in the rest)
Content - 100::
Proxy status - Proxied (orange cloud, but with a gray line behind it)
TTL - Auto
But when I typed </lerissapatrickvoice.com> into the browser, I got Error code 522 (“initial connection between Cloudflare’s network and the origin web server timed out”) and something about the host “is not completing requests.” That means </voiceoverview.com> isn’t working - right?
That rule matches www.lerissapatrickvoice.com not lerissapatrickvoice.com. You don’t have any DNS records for www. Repeat the earlier step for adding the AAAA record of 100:: using www as your hostname this time. If you want both www and the apex name to redirect, you can update your Page Rule to match *lerissapatrickvoice.com. That will match both the apex and any subdomain.
In Redirect Rules you are seeing uri.path which is the part to the right of the domain name. You will only want to redirect with Page Rules or Redirect Rules, not both. You can stick with the Page Rules for now since you are already using them.
Try using a backtick ` instead of a backslash \ and you will actually wind up with preformatted text.
You won’t have a zone for www.lerissapatrickvoice.com. The zone is lerissapatrickvoice.com. You need to create a hostname for www just like you did for @.
Anything is certainly going to be easier if you already know what you are doing. That’s one reason people hire experienced professionals so they can spend their time on things they find more valuable.
You can definitely delete that one. It’s not going to do you any good. Try adding a AAAA record with only www as the name.
The page lists required steps to complete zone setup, and the first one is to add an AAA record for www so that </www.lerissapatrickvoice.com> will resolve.
Then it says </www.lerissapatrickvoice.com> points to 100:: and has its traffic proxied through Cloudflare.
So doesn’t that mean I already have an AAAA record for the www URL? no?
When I type www in the Name (required) field and 100:: in the IPV6 address field and then hit Save, the result is
next to it. Page Rules only work with Proxied names. They will have 
next to them.