Hi there,
Suddenly wildcard stopped being proxied for new entries. I still see old entries being proxied (orange). Because of this not able to use ssl and cache for the root domain. Any idea what’s going on? Is the policy changed recently?
Thanks,
ST
Do you really mean a wildcard record? These can only be proxied on Enterprise plans.
However, the naked domain (@) should work.
What’s the domain name?
Sorry I mean a wildcard record. But it was working until a few days ago. 
we were pointing a wildcard CNAME to a Load balancer. Also, why the load balancer returning the origin IP when it’s set to proxied mode? the domain is samespace.co.
As @MarkMeyer said, that’s an Enterprise feature. Once in a while, the Dashboard has a glitch that lets others proxy it. You can still manually add A and CNAME hostname records that you can proxy.
Got it, thanks. But why load balancer returns origin ip in proxy mode when it receives traffic sent via CNAME?
It’s confusing when the LB says “Traffic to this host will go thru Cloudflare” but it actually exposes the origin ip". Pls check this Dropbox - File Deleted - Simplify your life
@MarkMeyer LB is a paid service.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
