Hey there everyone, I have two questions about domain pointers:
1. Why are domain pointers not listed at admin level under "DNS management"? I thought all domain names of all users were aggregated there, but it seems that for domain pointers I have to go into the user's account and choose "DNS management" there to see the DNS records associated with a domain pointer.
2. How can I redirect a domain pointer to a specific URL on the main domain when running NGINX? The problem is that I think that the domain pointer domain name will never trigger the config for the main domain in "Custom HTTPD Configurations". With Apache it was simple: I just made a directive in the main domain's .htaccess and it would apply to the domain pointer domain. On NGINX, you have to put your server-level routes in "Custom HTTPD Configurations", but somehow this will never trigger the rewrite:
But it may be a perfect forward secrecy issue, because that is what's configured on the "mydomain.com" domain. It seems my browser isn't even attempting to contact "mydomainpointer.com" because of this.
1. Why are domain pointers not listed at admin level under "DNS management"? I thought all domain names of all users were aggregated there, but it seems that for domain pointers I have to go into the user's account and choose "DNS management" there to see the DNS records associated with a domain pointer.
2. How can I redirect a domain pointer to a specific URL on the main domain when running NGINX? The problem is that I think that the domain pointer domain name will never trigger the config for the main domain in "Custom HTTPD Configurations". With Apache it was simple: I just made a directive in the main domain's .htaccess and it would apply to the domain pointer domain. On NGINX, you have to put your server-level routes in "Custom HTTPD Configurations", but somehow this will never trigger the rewrite:
Code:
if ($host = "mydomainpointer.com")
{
rewrite ^ https://mydomain/mypage.html permanent;
}But it may be a perfect forward secrecy issue, because that is what's configured on the "mydomain.com" domain. It seems my browser isn't even attempting to contact "mydomainpointer.com" because of this.