NS records are not properly created
-
- Posts: 88
- Joined: Thu Mar 06, 2014 7:52 pm
- Contact:
NS records are not properly created
Don't know if it's a bug or something, but I have domain.com added to package A.
In package A, I have the following name servers:
- ns1.mydomain.com
- ns2.mydomain.com
- ns3.mydomain.com
I add website domain.com to package A and when I create a website or DNS domain on that account I see that only 2 NS records are created (1 NS record is missing: ns3.mydomain.com).
Is this known? Does anybody else use 3 NS records and have the same issue?
Thanks in advance for your reply :)
edit: I also tried with creating a few other packages and domains, but the issue persists.
In package A, I have the following name servers:
- ns1.mydomain.com
- ns2.mydomain.com
- ns3.mydomain.com
I add website domain.com to package A and when I create a website or DNS domain on that account I see that only 2 NS records are created (1 NS record is missing: ns3.mydomain.com).
Is this known? Does anybody else use 3 NS records and have the same issue?
Thanks in advance for your reply :)
edit: I also tried with creating a few other packages and domains, but the issue persists.
-
- Posts: 139
- Joined: Thu Jan 07, 2016 12:01 am
Re: NS records are not properly created
If your using a single IP or server, having more than 2 is just a waste. Should your server fail, then all 3 ns's will fail. And TBH, you only need a min. of 2 ns's to function.drMacFaulty wrote:Don't know if it's a bug or something, but I have domain.com added to package A.
In package A, I have the following name servers:
- ns1.mydomain.com
- ns2.mydomain.com
- ns3.mydomain.com
I add website domain.com to package A and when I create a website or DNS domain on that account I see that only 2 NS records are created (1 NS record is missing: ns3.mydomain.com).
Is this known? Does anybody else use 3 NS records and have the same issue?
Thanks in advance for your reply :)
edit: I also tried with creating a few other packages and domains, but the issue persists.
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: NS records are not properly created
This is a little bug in vestaCP. There are some lines missing in the DNS templates for centos 6, .... I will create a pull request.
Quick fix:
/usr/local/vesta/data/templates/dns/default.tpl
Add this lines:
Quick fix:
/usr/local/vesta/data/templates/dns/default.tpl
Add this lines:
Code: Select all
ID='10' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns3%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='11' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns4%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='12' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns5%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='13' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns6%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='14' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns7%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='15' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns8%.' SUSPENDED='no' TIME='%time%' DATE='%date%'