Skip to main content

Can't access WHM through hostname

QueasyTiger
Hiya. So, I can access my WHM when I use the ip, but not the hostname. I get the NXDOMAIN error in my browser, and it doesn't resolve to the IP. All of my A records are there, and my DNS resolver is 1.1.1.1, and 1.0.0.1. I can't access any of the cPanel sites via their domains either, and the nameservers are set to my own with the registrar. I have no clue what's going on! Just ask for more info, screenshots etc.

Comments

8 comments

Date Votes
  • cPanelLauren
    This sounds like a DNS issue, which nameserver are you using on the server and can you confirm the hostname has an A record in the root domain's DNS zone file?
    0
  • QueasyTiger
    This sounds like a DNS issue, which nameserver are you using on the server and can you confirm the hostname has an A record in the root domain's DNS zone file?

    Hi, sorry for the late reply. My nameservers are ns1.domain.tld and ns2.domain.tld. I'm using a free domain temporarily to test my ideas for my internet services business. Could that be the cause of my issues? My DNS Zones are attached. I can also confirm that all the appropriate ports have been forwarded. I'm kinda stumped. Thanks! [Moderator note: removed actual domain name from this post.]
    0
  • SamuelM
    Hello @QueasyTiger Thanks for providing the screenshot. I am redacting the screenshot so as not to expose your domain name. When performing a DNS query for your domain's A record with the dig utility and its trace option, I received the following result: $ dig domain.tld A +trace [..] domain.tld. 300 IN NS ns1.domain.tld. domain.tld. 300 IN NS ns2.domain.tld. couldn't get address for 'ns1.domain.tld': not found couldn't get address for 'ns2.domain.tld': not found dig: couldn't get address for 'ns1.domain.tld': no more
    This indicates that the name servers do not have IP addresses assigned to them at the registrar. I recommend you refer to the following page from our documentation with instructions for configuring custom name servers to work properly with cPanel:
    0
  • QueasyTiger
    Hello @QueasyTiger Thanks for providing the screenshot. I am redacting the screenshot so as not to expose your domain name. When performing a DNS query for your domain's A record with the dig utility and its trace option, I received the following result: $ dig domain.tld A +trace [..] domain.tld. 300 IN NS ns1.domain.tld. domain.tld. 300 IN NS ns2.domain.tld. couldn't get address for 'ns1.domain.tld': not found couldn't get address for 'ns2.domain.tld': not found dig: couldn't get address for 'ns1.domain.tld': no more
    This indicates that the name servers do not have IP addresses assigned to them at the registrar. I recommend you refer to the following page from our documentation with instructions for configuring custom name servers to work properly with cPanel:
    0
  • SamuelM
    Hello again @QueasyTiger There's nothing to apologize for. If you configure your domain to use custom name servers that resolve to your server, all DNS changes including adding an A record will be carried out within cPanel/WHM. If you use the name servers provided by Freenom and Godaddy, then all DNS management must be done at Freenom or Godaddy. You are free to use either option. Some users prefer to set up custom name servers that can be managed by cPanel/WHM so that the process of making DNS changes is easily accessible. Another thing to note is that if you add A records pointing to your cPanel server for ns1, ns2, and srv2 at the registrar, you will also need to make sure that those records have been created on the cPanel server itself. This can be done in WHM. Refer to the "Create A or AAAA entries for your nameservers" section in the
    0
  • QueasyTiger
    Hello again @QueasyTiger There's nothing to apologize for. If you configure your domain to use custom name servers that resolve to your server, all DNS changes including adding an A record will be carried out within cPanel/WHM. If you use the name servers provided by Freenom and Godaddy, then all DNS management must be done at Freenom or Godaddy. You are free to use either option. Some users prefer to set up custom name servers that can be managed by cPanel/WHM so that the process of making DNS changes is easily accessible. Another thing to note is that if you add A records pointing to your cPanel server for ns1, ns2, and srv2 at the registrar, you will also need to make sure that those records have been created on the cPanel server itself. This can be done in WHM. Refer to the "Create A or AAAA entries for your nameservers" section in the
    0
  • SamuelM
    Hello again @QueasyTiger The supported way to update the server's primary IP address is using the IP Migration Wizard in WHM: Please let us know if you have any questions.
    0
  • QueasyTiger
    Hello again @QueasyTiger The supported way to update the server's primary IP address is using the IP Migration Wizard in WHM: Please let us know if you have any questions.

    Okay, so accessing the server via the local IP gives me this result: Unfortunately, I can't go any further. As for changing the IP through the command line, everything seems to be in order. The only way I can think of accessing the server at this point is changing the public IP of the server to access WHM. Is this possible? Also thanks for being patient. I might cut my losses and start again since I have learned a lot so far, if you think that it might be easier than fixing my current configuration. Thanks again!
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post