Skip to main content

Hosting Custom Nameservers on Dedicated Server's WHM

CharlesGLondon
Hello, 1) My nameserver's domain is registered on GoDaddy. Let's say mydomain.com 2) On GoDaddy I've created ns1 and ns2 and pointed to IP addresses on my dedicated server ns1.mydomain.com -> 123.456.789.111 ns2.mydomain.com -> 123.456.789.112 123.456.789.111 & 123.456.789.111 ar dedicated IPs on my dedicated server. 3) On my dedicated server's WHM I've added A records for these domains Home / Server Configuration / Basic WebHost Manager" Setup I can see A record for ns1.mydomain.com & ns2.mydomain.com in DNS edit as well. ping ns1.mydomain.com doesn't return anything so it doesn't seem to work. Let me know what did I miss?

Comments

20 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! There's three options that could be happening here. Option 1 - the "add A records for your nameservers" tool created separate DNS zones for the nameservers, causing confusion. You'll want to check the DNS zones on the system, and if that did happen, remove the extra zones and add the A records to the main mydomain.com zone file. Option 2 - Just because the nameservers point here, doesn't mean the DNS for mydomain.com does. You'll need to create the A records wherever the DNS for mydomain.com is handled. Option 3 - Everything is working fine, and you just need to give the DNS changes some time to propagate. You could confirm the DNS is working on your machine with the following command: dig ns1.mydomain.com @x.x.x.x
    It's important to note that the test for Option 3 would not override the situation presented in Option 1. Let me know if that helps as one of those will help to get things working.
    0
  • CharlesGLondon
    Hey there! There's three options that could be happening here. Option 1 - the "add A records for your nameservers" tool created separate DNS zones for the nameservers, causing confusion. You'll want to check the DNS zones on the system, and if that did happen, remove the extra zones and add the A records to the main mydomain.com zone file.

    Yes that may be the case. I see SOA, NS, MX, CNAME and other A rercords such as cpanel.ns1.mydomain.com, whm., webmail. etc. Do I need to remove all other records and just keep one A record for ns1.mydomain.com?
    0
  • CharlesGLondon
    Hey there! There's three options that could be happening here. Option 2 - Just because the nameservers point here, doesn't mean the DNS for mydomain.com does. You'll need to create the A records wherever the DNS for mydomain.com is handled.

    I'm not sure if I need to create A records for mydomain.com. I've another nameservers setup where there is no A record for myotherdomain.com and yet is working. Host names ns1.mydomain.com and ns2.mydomains.com are already setup so I guess this is what we need to setup properly to get it all working?
    0
  • cPRex Jurassic Moderator
    You wouldn't need to remove the other records. Having a unique DNS zone is fine, but not if there is already a separate zone for just mydomain.com, as that can lead to confusion.
    0
  • CharlesGLondon
    You wouldn't need to remove the other records. Having a unique DNS zone is fine, but not if there is already a separate zone for just mydomain.com, as that can lead to confusion.

    Ok so I found that there was DNS entry for mydomain.com which I just deleted. Following is dig's output $ dig ns1.mydomain.com @123.456.789.111 ; <<>> DiG 9.10.6 <<>> ns1.mydomain.com @123.456.789.111 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39381 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1 ;; 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 123.456.789.111 ;; AUTHORITY SECTION: ns1.mydomain.com. 86400 IN NS ns2.ip-14-16-121.eu. ns1.mydomain.com. 86400 IN NS ns1.ip-14-16-121.eu. ;; Query time: 37 msec ;; SERVER: 123.456.789.111#53(123.456.789.111) ;; WHEN: Thu Sep 08 15:35:09 BST 2022 ;; MSG SIZE rcvd: 113
    0
  • cPRex Jurassic Moderator
    If that's the right IP, it looks like you're all set!
    0
  • CharlesGLondon
    If that's the right IP, it looks like you're all set!

    IP is correct $ ping ns1.mydomain.com ping: cannot resolve ns1. mydomain.com: Unknown host $ ping 123.456.789.111 PING 123.456.789.111 (123.456.789.111): 56 data bytes 64 bytes from 123.456.789.111: icmp_seq=0 ttl=51 time=23.767 ms 64 bytes from 123.456.789.111: icmp_seq=1 ttl=51 time=19.356 ms 64 bytes from 123.456.789.111: icmp_seq=2 ttl=51 time=17.416 ms 64 bytes from 123.456.789.111: icmp_seq=3 ttl=51 time=19.477 ms
    0
  • cPRex Jurassic Moderator
    That could just be propagation. With all the recent changes it's hard to tell for sure. Do you have any domains pointed to those nameservers yet? If so, you could use a tool like intodns.com to do a more thorough scan.
    0
  • CharlesGLondon
    I think I may have found the issue. On GoDaddy nameservers for mydomain.com was set to ns1.mydomain.com & ns2.mydomain.com. I've set it to be GoDaddy's default nameserver now. I hope this change will work now? I've to wait for propagation so can't tell right now if it works.
    0
  • CharlesGLondon
    I think I may have found the issue. On GoDaddy nameservers for mydomain.com was set to ns1.mydomain.com & ns2.mydomain.com. I've set it to be GoDaddy's default nameserver now. I hope this change will work now? I've to wait for propagation so can't tell right now if it works.

    It didn't work after setting mydomain.com nameserver to be GoDaddy's default nameservers. ping ns1.mydomain.com returns: ping: cannot resolve ns1.mydomain.com: Unknown host
    0
  • cPRex Jurassic Moderator
    Can you try working through the guide here?
    0
  • CharlesGLondon
    Can you try working through the guide here?
    0
  • cPRex Jurassic Moderator
    Yes, A records have to exist and be working for the nameservers to properly respond. If that doesn't get things working how you expect, please submit a ticket to our team so we can check this out.
    0
  • CharlesGLondon
    Yes, A records have to exist and be working for the nameservers to properly respond.

    I've already created ticket, I was asked to contact GoDaddy. I'm attaching screenshots from GoDaddy, let me know if it is all setup correctly on GoDaddy?
    0
  • cPRex Jurassic Moderator
    At this point dealing in hypotheticals isn't going to work (meaning, not being able to see the domain and full configuration and server access). If you put in a ticket, and we said you need to poke GoDaddy about the issue, that's going to be the best plan.
    0
  • CharlesGLondon
    At this point dealing in hypotheticals isn't going to work (meaning, not being able to see the domain and full configuration and server access). If you put in a ticket, and we said you need to poke GoDaddy about the issue, that's going to be the best plan.

    Already wasted 3 days with your support and GoDaddy. No one knows what is wrong or how to fix.
    0
  • cPRex Jurassic Moderator
    Send me a private message with the actual domain name, and the nameservers you're trying to use.
    0
  • CharlesGLondon
    After adding A record it does ping so let me test it with a domain using this nameserver to find out if it is all working or not. If not I'll DM you.
    0
  • CharlesGLondon
    Hello, It still doesn't seem to work. I've added A records on GoDaddy for my custom nameservers. I can now ping to these nameservers. I've used these nameservers for a domain. I can't ping this domain. I've sent you private message.
    0
  • cPRex Jurassic Moderator
    Thanks - I just replied to that now.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post