Page 1 of 1

Use VestaCP DNS, to point to internal IP?

Posted: Fri Nov 30, 2018 1:41 pm
by brafi

Is it possible to create a domain, via my VestaCP DNS-management, pointing to an internal IP (port 443), via external IP?

I only have 1 global IP, on my internet connection, but would like to add more servers on my internal network:
- 1 "main-server" with vestacp, running mail, web and so on. (Port 80 an 443)
- via subdomain, to add a second dedicated server, only running Nextcloud for family-files. (only port 443)

Is this possible via VestaCP?
What should I look for, for having more servers on the same IP, using the same ports?

Global IP:

Internal servers:
server1.domain.xx - (port 80, 443)
server2.domain.xx - (port 443)

Re: Use VestaCP DNS, to point to internal IP?

Posted: Sun Jan 13, 2019 2:03 pm
by Felix
Yes it can be done.

If your VESTA Server is an authoritative NS server for your domain (domain.xx), then you can add A records for:
server1.domain.xx to point to
server2.domain.xx to point to
and so on.

When someone queries the DNS for server1.domain.xx they will get the reply of IP

Re: Use VestaCP DNS, to point to internal IP?

Posted: Wed Apr 08, 2020 9:14 am
by Vegas10128
Could you please explain how to set this up exactly?

I have been having a hard time trying to get something (exactly as this post question) to work and have no luck.

One time ive had luck was involving an haproxy server which came with soo much complications when involving ssl.
I had to just tank the HAProxy server and away with it.