Adding sub-domain creates a whole new dns record

Is this normal for Hestia? When I’ve managed servers in the past I would just added sub-domains to the domain’s record. Did I do something incorrect when adding this sub-domain? I am new to Hestia, but I’m trying to learn to do everything the Hestia way and not make this server a big roll-my-own / manual config headache like I normally do, haha. That said, this feels wrong to me, as it even added a www cname entry (as well as all the others from the template).

I set up a site before noticing this, so it works fine… but I’d like to fix this unless it’s just the way Hestia needs to do it for automating LE and stuff. Just looking for some advice on how to fix this, or if I should fix this (pretty sure I should, ha), and also what the proper way to add a sub-domain would be for future reference.

Thanks!

You selected DNS support when creating the new sub-domain so Hestia is adding the new zone.

imagen

Just don’t select DNS support when creating the sub-domain and add manually the new dns record to the base domain’s zone.

2 Likes

Thanks, I deleted the sub-domain’s DNS and added the A record to the domain’s DNS. Is there anything else I need to do? Will the Let’s Encrypt cert just renew like normal for the sub-domain still?

As always, thank you for all the help @sahsanu ! I can already tell you’re a legend on here! haha

1 Like

You don’t need to do anything else. Unless you’re looking to get a wildcard certificate (*.sub-domain.example.net, there’s no need for any additional steps. The Let’s Encrypt certificate will renew without any issues for the sub-domain.

You’re welcome :wink:

1 Like