nameserver setting drive me crazy

crliuh

• June 17, 2014 06:28

Hi, recently i just setup my whm in aws micro instance (my first time to set up server). all the installation and setting was fine except for setting up the nameserver. i've few questions, 1. can i use one ip for two nameservers? In my whm only appears with one ip. when adding new nameserver in nameserver registration im using the following values, ns1.example.com 54.255.196.150 ns2.example.com 54.255.196.150 both same ip. 2. in my whm's NS record report, there is no ip resolved for both domain name. Nameserver Resolved IP Zones Actions ns1.example.com No IP 7 Edit ns2.example.com No IP 7 Edit 3. im not able to ping my nameserver. ns1.example.com please help. when im trying to change my .org domain NS pointing to ns1.example.com. it won't resolve, whereas no problem for .com domain to resolve.

• 

  cPanelMichael

  • June 17, 2014 14:45

  Hello :) Yes, it's acceptable to use the same IP address for multiple name servers. The "NS record report" page is not relevant to the propagation or configuration of your name servers. It's just listing which zones use which name servers. Make sure the "A" record for your NS entries are added in the DNS zone of the domain name they are associated with, and that the domain name points to your server from the registrar. Thank you.

  0
• 

  crliuh

  • June 17, 2014 15:55

  Thanks micheal! i got this weird situation whereby all the .com domain looks fine in the DNS health check but the rest of the TLD doesn't look fine. this looks fine both hosted under my whm and both of them have the same setting in WHM's DNS zone .vB.vB

  0
• 

  cPanelMichael

  • June 17, 2014 18:24

  Please check with the domain registrar for the .my domain name. It looks like the name servers configured at the registrar are not reporting correctly. Thank you.

  0
• 

  crliuh

  • June 18, 2014 00:32

  below is the jaycar.my nameserver setting, Primary Name Server Hostname : ns1.eatplayfun.com Primary Name Server Netaddress : 54.255.196.150 Secondary Name Server Hostname : ns2.eatplayfun.com Secondary Name Server Netaddress : 54.255.196.151 is exactly the same as what i have done for .com domain. i've another .org domain is facing the same issue as .my domain too

  0
• 

  cPanelMichael

  • June 18, 2014 13:36

  Could you verify if the issue has been resolved? I see both of those domain names are now resolving well and reporting as such through "dig" and websites such as IntoDNS. Thank you.

  0
• 

  crliuh

  • June 18, 2014 13:55

  Thanks micheal. It's resolved. The issue happened because the domain was not resolved completely. Thanks alot! [COLOR="silver">- - - Updated - - - One more question, what about the email issue that i just mentioned?

  0
• 

  cPanelMichael

  • June 18, 2014 18:30

  Please ensure you open a separate thread for issues not related to the original problem. Thank you.

  0
• 

  crliuh

  • June 19, 2014 01:53

  Sure. And thanks again!

  0
• 

  Harlequin

  • July 13, 2014 13:28

  [quote="crliuh, post: 1666372">Hi, recently i just setup my whm in aws micro instance (my first time to set up server). all the installation and setting was fine except for setting up the nameserver. i've few questions, 1. can i use one ip for two nameservers? In my whm only appears with one ip. when adding new nameserver in nameserver registration im using the following values, ns1.example.com 54.255.196.150 ns2.example.com 54.255.196.150 both same ip. 2. in my whm's NS record report, there is no ip resolved for both domain name. Nameserver Resolved IP Zones Actions ns1.example.com No IP 7 Edit ns2.example.com No IP 7 Edit 3. im not able to ping my nameserver. ns1.example.com please help. when im trying to change my .org domain NS pointing to ns1.example.com. it won't resolve, whereas no problem for .com domain to resolve.
  I have the same issue: .vB And need to know how to change this.

  0
• 

  cPanelMichael

  • July 18, 2014 18:26

  [quote="Harlequin, post: 1684491">I have the same issue: 22392 And need to know how to change this.
  Please see my earlier response on this thread: [QUOTE]The "NS record report" page is not relevant to the propagation or configuration of your name servers. It's just listing which zones use which name servers. Make sure the "A" record for your NS entries are added in the DNS zone of the domain name they are associated with, and that the domain name points to your server from the registrar.
  Thank you.

  0

Please sign in to leave a comment.