Hello folks I m having trouble getting a
Hello folks, I'm having trouble getting a subdomain to redirect to a subdirectory. I'm sorry if this is a noob question.
I have account.mastersofscale.com as a CNAME, pointing to some outdated server that I do not control. I want it to point to the same server that handles https://mastersofscale.com -- more specifically, to https://mastersofscale.com/my-account
When I redirect, I need to capture the query string so things like $_GET variables still work.
I tried...
- removing the CNAME record for this subdomain
- adding page rules for handling the above desired end result.
See screenshots.
Ultimately, this did not seem to work. account.mastersofscale.com just totally failed to load.
I'm sorry if this is a noob question. Does anyone know the correct way to handle this scenario?
![](https://utfs.io/f/f68f04c1-43ca-4248-8b54-14626a26a234-gyfwwf.21.21_PM.png)
![](https://utfs.io/f/7c916fed-5153-4b95-8cb9-3f9d33bc3e31-gyfwwf.19.57_PM.png)
![](https://utfs.io/f/50e552f3-cafb-44a5-98f3-7b39ef34e795-gyfwwg.52.33_PM.png)
6 Replies
You need to have the DNS record
for the Page rules to be able to hit. You can make it an AAAA record of
![cloudflare](https://cdn.discordapp.com/emojis/1026272852900581496.png)
100::
instead of the CNAMEmaking it orange cloud makes 100% sense to me, thank you for pointing that out
however I'm not sure I understand what you mean by
100::
would you be willing to flesh that out into a more complete example so I can understand?
interesting, from their docs:
"and in the case a placeholder IP address is needed for “originless” setups, use the IPv6 reserved address 100::"100::
is just a filter IP address that allows you to have a valid ![cloudflare](https://cdn.discordapp.com/emojis/1026272852900581496.png)
account.mastersofscale.com
and replace it with a AAAA record and have 100::
as the value.is that basically just a sort of dummy value?
Yeah
100::
is a part of a TESTNET so it is a valid IP but won't be routed anywherevery interesting, I'll try it