We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Private nameserver not working [namecheap] OVH server SOLVED
Private nameserver not working [namecheap] OVH server SOLVED
Hi
I´m trying to configure private nameservers and I´m not able to make them work following all the steps.
I registered my domain in namecheap and tryed 2 options (none of them worked):
First option:
------------------------------
Added glue records (register nameservers in namecheap) as:
ns1.mydomain.com xxx.xxx.xxx.xxx
ns2.mydomain.com xxx.xxx.xxx.xxx
and them I add A records:
ns1 A 91.121.183.76
ns2 A 91.121.183.76
Then in Vesta I did exactly this:
1. Add domain yourdomain.com (leave DNS Support mark checked)
2. Go to DNS menu
3. Click on edit under yourdomain.com
4. Change template to child-ns
5. Go to Packages menu
6. Edit package called default
7. Set ns1.mydomain.com and ns2.mydomain.com as nameservers
Second option:
------------------------------
The same, but in at namecheap, instead of adding the A records, I followed step 10 of the guide:
10. Change name servers for mydomain.com to ns1.mydomain.com and ns2.mydomain.com
(I didn´t follow this 10 step in any other panel, but did tried ot anyway)
Of course, when adding a domain in Vesta I also set in the registrar the DNS servers as:
ns1.mydomain.com
ns2.mydomain.com
Do you see something wrong? I waited for hours
Thanks
----------------------------------------
SOLVED!!
It´s related to this: viewtopic.php?f=13&t=5389
When you instal your OS, if you select the OVH kernel distribution for CentOS, it´s already configured with bind. You just need to delete it and its dependences: yum remove bind
Then install VestaCP
I´m trying to configure private nameservers and I´m not able to make them work following all the steps.
I registered my domain in namecheap and tryed 2 options (none of them worked):
First option:
------------------------------
Added glue records (register nameservers in namecheap) as:
ns1.mydomain.com xxx.xxx.xxx.xxx
ns2.mydomain.com xxx.xxx.xxx.xxx
and them I add A records:
ns1 A 91.121.183.76
ns2 A 91.121.183.76
Then in Vesta I did exactly this:
1. Add domain yourdomain.com (leave DNS Support mark checked)
2. Go to DNS menu
3. Click on edit under yourdomain.com
4. Change template to child-ns
5. Go to Packages menu
6. Edit package called default
7. Set ns1.mydomain.com and ns2.mydomain.com as nameservers
Second option:
------------------------------
The same, but in at namecheap, instead of adding the A records, I followed step 10 of the guide:
10. Change name servers for mydomain.com to ns1.mydomain.com and ns2.mydomain.com
(I didn´t follow this 10 step in any other panel, but did tried ot anyway)
Of course, when adding a domain in Vesta I also set in the registrar the DNS servers as:
ns1.mydomain.com
ns2.mydomain.com
Do you see something wrong? I waited for hours
Thanks
----------------------------------------
SOLVED!!
It´s related to this: viewtopic.php?f=13&t=5389
When you instal your OS, if you select the OVH kernel distribution for CentOS, it´s already configured with bind. You just need to delete it and its dependences: yum remove bind
Then install VestaCP