Skip to main content

Setting up nameservers

Comments

5 comments

  • Hays Sleiman
    Hello, Thank you for the guides. I've gone through all the steps and still not sure what I'm missing :( I have two physical cpanel servers ns1.mydomain.com (xxx.xxx.xxx.100) ns2.mydomain.com (xxx.xxx.xxx.200) ns1 has DNS and hosts the websites. ns2 is cPanel DNS only. Also, I've configured clustering and DNS synchronization between the two servers successfully. My accounts however are still unable to resolve. When I test one of the domain accounts on intoDNS, I receive the following errors: 1) ns1.mydomain.com [xxx.xxx.xxx.100] (NO GLUE) ns2.mydomain.com [xxx.xxx.xxx.200] (NO GLUE) 2) Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records. 3) DNS servers responded ERROR: One or more of your nameservers did not respond: The ones that did not respond are: xxx.xxx.xxx.100 xxx.xxx.xxx.200 4) Missing nameservers reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again: ns1.mydomain.com ns2.mydomain.com 5) SOA record No valid SOA record came back! That's it. As far as I could tell, I've done everything right. Could this be a problem at the registrar for mydomain.com? Because when I asked them to register my 2 nameservers, it seems like they did not know what I meant and only created A records for ns1 and ns2, but I could be wrong. ANY help would be highly appreciated. Thanks in advance :)
    0
  • syslint
    Hi, Please do the following , 1) Go to InterNIC | Whois , check if your NS were registered properly and pointing to your DNS cluster 2) Check BIND is running and you can connect to port 53 from outside to your server 3) You may login to your domain registrar control panel and update all of your domains with the new NS . Let me know how it is going on.
    0
  • Hays Sleiman
    Hello, It's now working! Thanks to syslint! Not one of the articles mentioned opening port 53! I even went over them again to check I didn't miss anything. As soon as I opened the port, everything started working as intended and intoDNS has no more errors. Thanks again guys!
    0
  • cPanelMichael
    I am happy to see the issue is now resolved. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.