Hello all.
I came across the following problem today: A reseller of ours tried to add an alias domain and the system was whining about the action not being allowed as the nameservers were not pointing at our server. This reseller has his own set of nameservers (2 hostnames under his domain) that point to a secondary IP on our server. I had to add this secondary IP in the Remote Service IPs configuration, in order to be able to add the alias domain.
Based on the above, I have concluded that the check for allowing/denying domain additions only takes the root account's nameservers into consideration. So, given that I can't think of a reason it shouldn't also consider all the rest of the nameservers (per case, of course, to avoid a user/reseller adding a domain they don't own), I think this should be changed/fixed.
What say you?
I came across the following problem today: A reseller of ours tried to add an alias domain and the system was whining about the action not being allowed as the nameservers were not pointing at our server. This reseller has his own set of nameservers (2 hostnames under his domain) that point to a secondary IP on our server. I had to add this secondary IP in the Remote Service IPs configuration, in order to be able to add the alias domain.
Based on the above, I have concluded that the check for allowing/denying domain additions only takes the root account's nameservers into consideration. So, given that I can't think of a reason it shouldn't also consider all the rest of the nameservers (per case, of course, to avoid a user/reseller adding a domain they don't own), I think this should be changed/fixed.
What say you?