Security issues when create subdmain without main domain
Hi!,
I have a client who wants this setup: point a domain to a server from another hosting provider, and create a subdomain and point it to my server. Example:
domain.com -> Another server that I do not manage and do not know
subdmain.domain.com -> To my server
However I have read that this can create security issues:
-
Hey there! You'd have to have the Allow Remote Domains option on in order for this to work since you don't control the DNS. It's not so much a security issue, but a "confusion" issue as many Shared hosts don't want users creating domains and then getting a support ticket when the DNS doesn't work. If the DNS is hosted locally, that isn't an issue. 0 -
Hey there! You'd have to have the Allow Remote Domains option on in order for this to work since you don't control the DNS. It's not so much a security issue, but a "confusion" issue as many Shared hosts don't want users creating domains and then getting a support ticket when the DNS doesn't work. If the DNS is hosted locally, that isn't an issue.
Hi, Thank you very much. However in your documentation you says literally: "Do not enable this option. It can cause serious security issues". When I read "Serious security issues" I understand that can have a very big problem. Sorry my bad english. Please, check attached image. Thank you again.0 -
Yeah, it's always said that. Is there technically a risk? Sure - you could have some user create google.com and come up with some brilliant way to route local google traffic to their domain. But is it likely? Probably not. For a one-time use while you create a domain for your intended setup, or on a server where you personally manage all the accounts, it's likely fine. I wouldn't enable this on a Shared machine, though. 0
Please sign in to leave a comment.
Comments
3 comments