I’m trying to set up a reverse proxy for my Hubspot account. I followed the instructions to find the proxy_pass destination and it comes out to be <my-hub-id>.sites-proxy.hscoscdn02-na2.net since my account is hosted in the US-West region. This CNAME however does not resolve. I used this document to arrive at the proxy destination: Accounts Dashboard | HubSpot
In fact, I don’t get an NS record on the domain the domain sites-proxy.hscoscdn00-na2.net. I get an NS record when I try sites-proxy.hscoscdn00.net. I also get an answer when I try to resolve <my-hub-id>.sites-proxy.hscoscdn00.net.
I tried creating a reverse proxy setup using the US East region address and I get a 421 Misdirected response when I proxy to this destination. I cannot use the US West address which is the correct one since it doesn’t resolve.
Is there a mistake in how I have created the proxy URL for my account? Am I referring to documentation that is outdated?
After probing around a bit, I found that name servers are configured without the HubID suffix for regions outsude US East. So hscoscdn00-na2.net does not resolve but hscoscdn-na2.net does. Without the zone suffix, the numeric suffix is required as shown in the documentation. I tried setting up the proxy with the na2 suffix, without the numeric suffix, but I still get a 421 Misdirected Request response.
$ dig +noall +answer -t A test.sites-proxy.hscoscdn00-na2.net$ dig +noall +answer -t A test.sites-proxy.hscoscdn-na2.nettest.sites-proxy.hscoscdn-na2.net. 285 IN A 199.60.103.2test.sites-proxy.hscoscdn-na2.net. 285 IN A 199.60.103.254$ dig +noall +answer -t A test.sites-proxy.hscoscdn.net$ dig +noall +answer -t A test.sites-proxy.hscoscdn00.nettest.sites-proxy.hscoscdn00.net. 377 IN A 199.60.103.30test.sites-proxy.hscoscdn00.net. 377 IN A 199.60.103.226$ dig +noall +answer -t A test.sites-proxy.hscoscdn10.nettest.sites-proxy.hscoscdn10.net. 377 IN A 199.60.103.225test.sites-proxy.hscoscdn10.net. 377 IN A 199.60.103.31
You need a HubSpot enterprise account to setup a reverse proxy.