12 Replies
not even ::1 works for AAAA records
i want to make redirect rules work
Use
100::
In the case a placeholder address is needed for “originless” setups, use the IPv6 reserved address 100:: or the IPv4 reserved address 192.0.2.0 in your Cloudflare DNS to create a proxied DNS record that can use Cloudflare Redirect Rules, Page Rules, or Cloudflare Workers.
but why did not others work?
100:: for IPv6 (recommended, it's discard address) or for IPv4 you can use 192.0.2.0
aaaa or a records cannot be proxied at all
They definitely can, some addresses are banned though. For example, if something went wrong with your redirect rule (or redirect rules in entirety), and people use 100:: the traffic would just be sinkholed. If everyone was using 1.1.1.1, it'd be like a DDoS Attack against it
oh
ok
thanks!
i think error should be clearer about it though
Also redirect rules dont seem to work
I think in part it's done to prevent people from doing really silly things like trying their Private IP Addresses or DNS Resolver, and "originless" setups are just more of an edge case, but yea it could say the issue is the IP rather then being so generic
getting 522
Means it isn't matching. What does your rule look like? Most of the time using
Hostname field works better/is simpler, or in combination with Hostname and Path, etc, seperating out your rule rather then trying to use the entire urii tried uri full, that did not work with https, but hostname worked. Thanks! Have a good day!