DNS A record not redirect to the given external IP

Hello everybody, excuse me if my question is not directly related with HestiaCP or is a noob question.

I have installed the panel since one month ago, everything is working fine Let’s encrypt SSL, I had configured the mail service with Amazon SES, DNS records works fine… Anyway, I have tested the basic configuration of the panel with two domain names and all works fine.

PROBLEM (or maybe not):
I has created an A type DNS record, that points to an external public IP, example:
my HestiaCP public IP is: 1. 1. 1. 1
My A record: vps. mydomain. com is pointing to IP: 2. 2. 2. 2

ping to vps. mydomain. com resolves to my HestiaCP public IP: 1. 1. 1. 1, as I know that a simple ping is not the right tool for test, I tested the same with the mxtoolbox with the same result.
I expected that it should resolve to IP: 2. 2. 2. 2

Is something wrong there?, or is the correct way how the DNS server works?. I mean, the DNS server
can point to external IPs or only to the main Panel/server IP(s)?.


  • HestiaCP versión: v1.6.14
  • host OS: Ubuntu server 22.04
  • Running on a VPS
  • I’m not getting DNS errors, not at least in the main log.

I’m very glad with HestiaCP, is very fast, have a pretty UX/UI and is easy of deploy and configure!. I’m very grateful that people as the panel developers dedicate time to do amazing things like this.

I really apreciate your help guys, thanks in advace.


It was a DNS record problem not HestiaCP problem.

In my registrar DNS (google domains) i had an A dns record like:

vps.mydomain. com pointing to my HestiaCP IP: 1. 1. 1. 1

In my HestiaCP i had an A dns record like:
vps. mydomain. com pointing to an external server IP: 2. 2. 2. 2

Thinking that the HestiaCP overrides my registrar DNS but I was wrong.


In my DNS registrar I changed the A dns record to NS record:

NS vps. mydomain. com pointing to my HestiaCP nameserver: ns1. mydomain .com

I hope that this can help to someone else, thanks!!!