Looks like a DNS propagation delay/issue. I think I have it handled. Thanks for your feedback.
For anyone following this thread; be sure to use the dig command to ensure your DNS is indeed, your HestiaCP! I.e.:
dig NS example.com
3 Likes