DNS not resolving even after 48 hrs

[bhavilajain68]

Hi everyone,

This is my first time using Vesta CP so please forgive my noob-ness. I'm a intermediate php developer, but network stuff is very much my Achilles heel.
Up until now I've only had experience with shared servers with cPanel. It was easy as everything was pretty much set up and all i had to do were the PHP things.

So signed up for AWS Lightsail-> Fired up an Ubuntu 18.04 instance -> Updated Ubuntu -> Installed Vesta CP -> Followed the official instructions from https://vestacp.com/docs/#how-to-setup- ... ameservers

I changed my name servers on 13th may at around 2 in the noon(IST). Now its been above 48hrs, but the DNS is still not resolved. I'm attaching images of my setup

GoDaddy Nameservers Setup




VestaCP->Web (domain setup)




VestaCP->DNS




dnschecker.org




I, not having next to no experience with "networking" & following the official instructions, am not able to understand whats wrong and why I cant access my site.

I could really use help with this. I tried to get help from friends and better developers in my circle, but none of them have used VestaCP.

Please let me know if you need any other information about my setup.

There's another question regarding sub-domains. Do i need to set their template as child-ns as well?

Thanking in advance for any help. :)

[bhavilajain68]

No One??

[lotnomore]

No One??

Your settings at Godaddy seem to be OK.

Does the DNS zone of the hostname root domain have these records?

_domainkey TXT "t=y; o=~;"
_dmarc TXT "v=DMARC1; p=none"

For sub-domains and all additonal domains to be added, you do not need to use the child-ns DNS template, just use the default one.

BTW, I have just finished writing up tutorials for fresh installation of HestiaCP (a fork of VestaCP), maybe you can learn something about the fresh install, setup and DNS template usage there.

[bhavilajain68]

No One??

Your settings at Godaddy seem to be OK.

Does the DNS zone of the hostname root domain have these records?

_domainkey TXT "t=y; o=~;"
_dmarc TXT "v=DMARC1; p=none"

For sub-domains and all additonal domains to be added, you do not need to use the child-ns DNS template, just use the default one.

BTW, I have just finished writing up tutorials for fresh installation of HestiaCP (a fork of VestaCP), maybe you can learn something about the fresh install, setup and DNS template usage there.

Hi there Mate... Thank you for the help.

I ended up using godaddy as my DNS management instead of using vestaCP. started working instantly.
I'll have a look at your guide. Though I'm skeptical if I'll try to switch back. as the about of headache the process gave me is unbearable..

Would like to know though. What am I loosing if I keep godaddy as my DNS manager?

Does the DNS zone of the hostname root domain have these records?

I did not understand this. Where should I be looking for this?

[lotnomore]

If it is working, stick to Godaddy' settings, however...

I had similar problem before. Since I needed to host more than one domain site on the server, I could use their DNS Power Tools to register ns1 and ns2.myprimarydomain.com nameservers to point to the server IP and use them for myprimarydomain.com (and for other domains to be added) at the same time at my domain registrar Onlinenic, but I had to use Vesta to generate all the needed records. But if want to use my domain registrar to handle all the DNS records, then I have to use their name servers for myprimarydomain.com and stick to this routine for all the other domains to be added, which I did not like as a hosting reseller.

I find this one problem with most domain registars though: they provide limited types for DNS records. For example, at eNom they do not even allow me to enter a MX record (I had to use CNAME). At Onlinenic, they allow me to enter only these six types: A, AAAA, MX, CNAME, TXT and NS records, nothing else. I do not know about Godday as I have no domain there any more.

I am not the expert on this. so use your own judgment on this or sort experts opinions.