Hosting Custom Nameservers on Dedicated Server's WHM
Hello,
I'm trying to setup on own custom nameservers on my dedicated WHM server.
1) My domain is registered with namecheap. I've set up custom nameservers there
ns1.mydomain.com 54.xx.yy.16
ns2.mydomain.com 54.xx.yy.16
2) On WHM Home / Server Configuration / Basic WebHost Manager" Setup
I've configured address records
ns1.mydomain.com 54.xx.yy.16
ns2.mydomain.com 54.xx.yy.16
3) On WHM I've added A records and other records for mydomain.com on Home / DNS Functions / DNS Zone Manager
Please see the attached screenshots for all of the above.
4) All these have been set up more than 72 hours ago so propagation shouldn't be an issue by now
5) I've a concern that the IP address 54.xx.yy.16 which I've used for both nameservers is the same.
This IP address is also my dedicated server's IP address.
I'm not sure if I should have used my main server's IP address for nameservers? Please advise.
At the end of all these settings
ping ns1.mydomain.com
ping ns2.mydomain.com
are not working
So nameservers are not resolving to my host. How do I fix it?
-
$ dig ns1.mydomain.com @54.xx.yy.16 ; <<>> DiG 9.10.6 <<>> ns1.mydomain.com @54.xx.yy.16 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11758 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;ns1.mydomain.com. IN A ;; ANSWER SECTION: ns1.mydomain.com. 14400 IN A 54.xx.yy.16 ;; AUTHORITY SECTION: mydomain.com. 86400 IN NS ns1.mydomain.com. mydomain.com. 86400 IN NS ns2.mydomain.com. ;; ADDITIONAL SECTION: ns2.mydomain.com. 14400 IN A 54.xx.yy.16 ;; Query time: 75 msec ;; SERVER: 54.xx.yy.16#53(54.xx.yy.16) ;; WHEN: Tue Apr 04 20:53:27 BST 2023 ;; MSG SIZE rcvd: 110 0 -
Hey there! It doesn't matter that the IP address is or is not the main shared IP, or if it is being shared with other accounts - the DNS system will still work. What happens when you check one of the domains using those nameservers with a tool like intodns.com? Or, what happens if you just ping the nameserver from your local workstation? You've said you configured the Basic WebHost Manager setup page, but do the nameservers themselves have A records configured so they respond in DNS? 0 -
1) Ping to nameservers from my local machine ping: cannot resolve ns1.mydomain.com: Unknown host 2) do the nameservers themselves have A records configured so they respond in DNS? I've these A records on my host, are these the ones you are talking about?
3) IntoDNS gives bunch of errors:ns1.mydomain.com. 14400 A 54.xx.yy.16 ns2.mydomain.com. 14400 A 54.xx.yy.16 NS alt="Info">https://intodns.com/static/images/info.gif
NS records from your nameservers NS records got from your nameservers listed at the parent NS are: Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly. alt="Error">https://intodns.com/static/images/error.gif
Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records. alt="Error">https://intodns.com/static/images/error.gif
DNS servers responded ERROR: One or more of your nameservers did not respond: The ones that did not respond are: 54.xx.yy.16 alt="Error">https://intodns.com/static/images/error.gif
Multiple Nameservers ERROR: Looks like you have less than 2 nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me. alt="Error">https://intodns.com/static/images/error.gif
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. SOA alt="Error">https://intodns.com/static/images/error.gif
SOA record No valid SOA record came back! MX alt="Error">https://intodns.com/static/images/error.gif
MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers! WWW alt="Error">https://intodns.com/static/images/error.gif
WWW A Record ERROR: I could not get any A records for 0 -
The first thing I would confirm is that port 53 is open for inbound connections to your machine. The easiest way to test that would be with a simple telnet test to your server, from an external system: telnet x.x.x.x 53
where "x.x.x.x" is your server's IP address. If that isn't open, no nameserver functions will work properly. Let's confirm that is open and not filtered and then we can go from there.0 -
Yes it is open telnet 54.xx.yy.16 53 Trying 54.36.127.16... Connected to ns39xxx.ip-54-xx-1yz.eu. Escape character is '^]'. 0 -
Alright, so that's good. The next thing is to find out why the nameservers don't respond to ping. This part seems more odd since your "dig @" test seemed to work well, but a general ping did not. Are the A records part of individual ns.domain.com zone files? If so, you will likely see improvement by placing those A records in the main domain.com zone instead of relying on the separate ns.domain.com zone files. 0 -
No, I don't have individual zone records for ns1 and ns2. These records are inside mydomain.com. I'm attaching the DNS zone screenshot again, have a look at this 0 -
That all looks fine to me. At this point it would be best to create a ticket so we could examine the machine directly. 0 -
That all looks fine to me. At this point it would be best to create a ticket so we could examine the machine directly.
I've created ticket 950392270 -
Thanks for that - I'm following along with that ticket on my end now. 0
Please sign in to leave a comment.
Comments
10 comments