Answer the question
In order to leave comments, you need to log in
Is it worth buying a domain a separate domain for the main server?
The backend structure will be as follows: 1 powerful server on which there is a database and background scripts, and several servers already for client-server communication. So, is it worth buying a separate domain for https for this backend, or allocating a subdomain.
If it is easier to select a subdomain, then is it possible to find out what subdomains a domain has (for security reasons)?
Answer the question
In order to leave comments, you need to log in
Domain-subdomains do not affect security in any way, it is affected by the server setting. And the division "domain-subdomains" is more about the organization of work, etc.
Let's just say I allocated 1 IP address for a host with "doubtful" content.
Doubtfulness actually in the hysteria of the target audience.
Otherwise, everything is spinning on 1 machine.
By the way, in your case, the database and scripts should not be visible at all. Hide them in a local grid, and let your web snouts knock on it over the local network.
I got the feeling that backend calls will not be via HTTP/HTTPS, but via completely different protocols. Accordingly, a domain is not needed there - you can refer to it by the name "backend.local", which will resolve to an address like "192.168.xy" (here I repeat the second paragraph of Vladimir Korotenko 's answer ).
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question