How to bind a domain to a VPS that does not have a dedicated IP?

Question

Apache HTTP Server

The hoster issued a VPS (with root rights, of course), but without a dedicated IP. Apache is installed on the VPS. I directed the domain via A-record to a common IP. Another hoster provided his domain, the third level, to which the site is currently linked. In principle, I used to always bind only to a dedicated IP through the command sudo hostname -b domain.name
. Now this thing does not work and there is a redirect to the hoster's website. Please direct me to the necessary tutorials or tell me how you can control the linked domains. I am using Ubuntu 14.04.

Answer 1

Based on the comments:
1) first open nslookup and check which IP address your domain NOW resolves to, the one you need. If it resolves to an IP that has nothing to do with yours, then most likely it is a parking server that redirects to the hosting site
2) you already decide whether you have a white IP or not. The fact that you connect via ssh does not mean at all that your IP is white, you most likely just set up port forwarding, since you specify a non-standard port for connection (2006, standard - 22). You probably rented a server at a cheap rate that does not include issuing a white IP. Of course, it is possible to direct an A-record to a public IP, and it may even be necessary, but it depends on the network configuration of your hoster. Theoretically, it can send traffic through a proxy, which then knocks on your server.
3) in general, usually in such cases they give out a white IP, and a person does what he wants with it, binds dns and connects via standard ports. if you do not have an external address, deal with the hosting provider, what specific opportunities it provides and how it can host services on such a VPS. Throw a link or something to the tariff that you have chosen.
PS And yes, what does sudo hostname have to do with it, it’s also not clear to me, the entry in the hostname file has nothing to do with the dns configuration.

Answer 2

So it is. Is there NAT on the VPS? I draw this conclusion by how you connect via SHH. Namely:
I don't think this is a concern about the security of your system.
If port 80 is busy, and it is busy on this IP and it is obvious, you need to find out from the service provider exactly how you set up the web server. And I assume that if there is NAT, then you yourself will not be able to do this, because. It's not about the server, it's about the VPS organization. Contact support.

Answer 3

Whoa!
How do you get on the VPS server? What IP? gray too? =)

Answer 4

Can cname be used?