Nameserver setup questions

[brand_land]

Hello
I have a VPS, when I create accounts, I edit the dns zones to ns1.domainname.com and ns2.domainname.com.
what I want to know is do I have to use a different number every time I create a new domain as in ns3, ns4 etc or is it okay to use the same ns1 and ns2 for all accounts ?
I add A records, are there any important records that I should add ?
Thank you

 

[cPanelMichael]

Hello @brand_land,

The following document will walk you through all of the required name server setup steps:

How to Set Up Nameservers in a cPanel Environment - cPanel Knowledge Base - cPanel Documentation

You should not have to edit the DNS zones after each account is created as long as you configure the default name servers in WHM's Basic WebHost Manager Setup interface. It's acceptable to use NS1 and NS2 for multiple domains.

Thank you.

 

[brand_land]

Hello @brand_land,

The following document will walk you through all of the required name server setup steps:

How to Set Up Nameservers in a cPanel Environment - cPanel Knowledge Base - cPanel Documentation

You should not have to edit the DNS zones after each account is created as long as you configure the default name servers in WHM's Basic WebHost Manager Setup interface. It's acceptable to use NS1 and NS2 for multiple domains.

Thank you.

Hello and thank you for your reply,
I've checked the link that you gave me, but that means the DNS for each website will be the ones that I chose for my VPS right ? won't that cause a problem for email and SSL ? considering that the records don't match the domain name ?

The IP address that I have to use, I found 2 IP addresses, one in the server manage tab in godaddy and another one in the IP addresses in WHMm which one should I use ?

Another question, I followed all the instructions and I set up my server nameservers to ns1.mychosenname.com and ns2, when I add host names of the new account, they are added by ns1 and ns2 and the ip address but not the VPS nameservers, instead they are added as ns1.accountname.com and ns2.accountname.com
is that okay ?

 

[cPanelMichael]

I've checked the link that you gave me, but that means the DNS for each website will be the ones that I chose for my VPS right ? won't that cause a problem for email and SSL ? considering that the records don't match the domain name ?

No, the name servers assigned to a domain in it's DNS zone or at it's registrar do not have to match the domain name itself. The key is for the name servers assigned to the domain at it's domain registrar to match the name servers utilized in it's DNS zone on the cPanel & WHM server.

The IP address that I have to use, I found 2 IP addresses, one in the server manage tab in godaddy and another one in the IP addresses in WHMm which one should I use ?

You can use any IP address assigned to the cPanel & WHM server. NS1 and NS2 can share the same IP address, or you can use a different IP address for NS1 and NS2. One way to confirm an IP address is associated with your cPanel & WHM server is to enter it in your web browser with port 2087 and confirm access to WHM succeeds (e.g. https://IPHERE:2087).

Another question, I followed all the instructions and I set up my server nameservers to ns1.mychosenname.com and ns2, when I add host names of the new account, they are added by ns1 and ns2 and the ip address but not the VPS nameservers, instead they are added as ns1.accountname.com and ns2.accountname.com
is that okay ?

Are you creating accounts as "root" or are you logged into WHM as a reseller username?

Thank you.

 

[brand_land]

No, the name servers assigned to a domain in it's DNS zone or at it's registrar do not have to match the domain name itself. The key is for the name servers assigned to the domain at it's domain registrar to match the name servers utilized in it's DNS zone on the cPanel & WHM server.



You can use any IP address assigned to the cPanel & WHM server. NS1 and NS2 can share the same IP address, or you can use a different IP address for NS1 and NS2. One way to confirm an IP address is associated with your cPanel & WHM server is to enter it in your web browser with port 2087 and confirm access to WHM succeeds (e.g. https://IPHERE:2087).



Are you creating accounts as "root" or are you logged into WHM as a reseller username?

Thank you.

Thank you again for your reply.
I found out that I used the correct IP address, and the names That I'm talking about are in the domain dns management of the new account which propagate to my VPS name servers which means everything is correct as I believe, now I've faced another problem with SPF and DKIM, the SPF record in the new account cpanel states the other IP address that I found in the IP addresses in WHM.
I followed everything correctly, why is SPF and DKIM incorrect ?

 

[cPanelMichael]

ow I've faced another problem with SPF and DKIM, the SPF record in the new account cpanel states the other IP address that I found in the IP addresses in WHM.
I followed everything correctly, why is SPF and DKIM incorrect ?

Do you see errors reported in the cPanel >> Email Deliverability interface for this account, or are you asking why it's showing an IP address that doesn't match your name server IP addresses?

Thank you.

 

[brand_land]

Do you see errors reported in the cPanel >> Email Deliverability interface for this account, or are you asking why it's showing an IP address that doesn't match your name serve

r IP addresses?

Thank you.

No there are no errors, I ran an MX lookup tool and it showed these errors:



DO I tried to go to the account Cpanel and check everything and when I saw the SPF record, the other IP address was in the record.
Some accounts experienced some emails not being delivered and no mail delivery email is returned.
Thank you

 

[cPanelMichael]

It's by-design the SPF record makes use of the IP address associated with the account as opposed to the IP address utilized for your name servers. This is normal and should not result in any issues with remote mail servers detecting a valid SPF record.

The only MXToolBox warning you posted that is likely to result in deliverability issues is the lack of a RDNS record. You can contact your hosting provider to request they set up PTR records for your server's main IP address pointing to your server's hostname.

Thank you.