Account Creation Status: failed
Account Creation Status: failed
Cpanel::Exception/(XID tnjxrd) The system failed to find IPv4 addresses for "a.gtld-servers.net", "b.gtld-servers.net", "c.gtld-servers.net", "d.gtld-servers.net", "e.gtld-servers.net", "f.gtld-servers.net", "g.gtld-servers.net", "h.gtld-servers.net", "i.gtld-servers.net", "j.gtld-servers.net", "k.gtld-servers.net", "l.gtld-servers.net", and "m.gtld-servers.net". Because of this, the system cannot find "domain.com""s authoritative nameservers. See the cPanel & WHM error log for more details. at /usr/local/cpanel/Cpanel/DNS/GetNameservers.pm line 141. Cpanel::DNS::GetNameservers::get_nameservers(Cpanel::DNS::Unbound=HASH(0x2fdcc80), "domain.com", undef, 1) called at /usr/local/cpanel/Cpanel/DnsRoots.pm line 27 Cpanel::DnsRoots::fetchnameservers("domain.com") called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 729 Whostmgr::Accounts::Create::_create_nameserver_entries(HASH(0x2f82370), HASH(0x2fb2da8)) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 774 Whostmgr::Accounts::Create::_validate_nameservers(HASH(0x2f82370)) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 1099 Whostmgr::Accounts::Create::_validate_args(HASH(0x2f82370), HASH(0x1b50c68)) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 342 eval {...} called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 342 Whostmgr::Accounts::Create::_wwwacct("bwlimit", 20000, "user", "$USER", "is_restore", 0, "featurelist", "default", ...) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 2971 Whostmgr::Accounts::Create::__createaccount("maxpark", 5, "username", "$USER", "customip", "", "maxaddon", 2, ...) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 3025 Whostmgr::Accounts::Create::_createaccount("maxpark", 5, "username", "$USER", "customip", "", "maxaddon", 2, ...) called at whostmgr/bin/whostmgr5.pl line 781 main::wwwacct("wwwacct") called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 259 Whostmgr::Dispatch::_do_call("wwwacct", HASH(0x2b18d00), HASH(0x2b1bd10)) called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 157 Whostmgr::Dispatch::dispatch("wwwacct", 1, ARRAY(0x2b18af0), HASH(0x2b1bd10)) called at whostmgr/bin/whostmgr5.pl line 257-
The system can not find your domain's authoritative nameservers because DNS resolution is not working properly. You might try to update the nameservers added in /etc/resolv.conf or WHM>>Networking Setup>>Resolver Configuration then try adding the account again. 0 -
i don't know if this issue was resolved because I'm having exact same problem here. The suggestion concerning the DNS doesn't solve the problem. Error message below: Account Creation Status: failed Cpanel::Exception/(XID maucyq) The system failed to find IPv4 addresses for "ns1.nic.net.ng", "ns2.nic.net.ng", "ns5.nic.net.ng", and "nsa.nic.net.ng". Because of this, the system cannot find "domain.com.ng""s authoritative nameservers. See the cPanel & WHM error log for more details. at /usr/local/cpanel/Cpanel/DNS/GetNameservers.pm line 141. Cpanel::DNS::GetNameservers::get_nameservers(Cpanel::DNS::Unbound=HASH(0x3df7a98), "domain.com.ng", undef, 1) called at /usr/local/cpanel/Cpanel/DnsRoots.pm line 27 Cpanel::DnsRoots::fetchnameservers("domain.com.ng") called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 729 Whostmgr::Accounts::Create::_create_nameserver_entries(HASH(0x3d15a18), HASH(0x3df72d0)) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 774 Whostmgr::Accounts::Create::_validate_nameservers(HASH(0x3d15a18)) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 1099 Whostmgr::Accounts::Create::_validate_args(HASH(0x3d15a18), HASH(0x1b51ca0)) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 342 eval {...} called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 342 Whostmgr::Accounts::Create::_wwwacct("useip", "n", "bwlimit", 30000, "spf", 1, "locale", "en", ...) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 2971 Whostmgr::Accounts::Create::__createaccount("max_emailacct_quota", "unlimited", "maxsub", "unlimited", "dbuser", "dannydig", "mxcheck", "local", ...) called at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 3025 Whostmgr::Accounts::Create::_createaccount("max_emailacct_quota", "unlimited", "maxsub", "unlimited", "dbuser", "dannydig", "mxcheck", "local", ...) called at whostmgr/bin/whostmgr5.pl line 781 main::wwwacct("wwwacct") called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 259 Whostmgr::Dispatch::_do_call("wwwacct", HASH(0x38b27b8), HASH(0x38b55f8)) called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 157 Whostmgr::Dispatch::dispatch("wwwacct", 1, ARRAY(0x38b5550), HASH(0x38b55f8)) called at whostmgr/bin/whostmgr5.pl line 2570 -
The suggestion concerning the DNS doesn't solve the problem.
What did you update them from and to?0 -
What did you update them from and to?
Primary Resolver: 100.100.100.16 Secondary Resolver: 100.100.100.17 Both have been confirmed to be valid and working by my server provider0 -
is there any solution? it's clear this is a cpanel bug 0 -
While these DNS resolvers may function some items it seems they aren't able to query root nameservers and that would deem this a configuration issue, not a bug. If you use public DNS resolvers such as CloudFlare's or Google's does the issue persist? 0 -
8.8.8.8 8.8.4.4
I used the above Google public DNS resolvers but the problem persists0 -
Ok, are you by chance using a NAT configuration? 0 -
No, I am not using NAT configuration. Also I seem to be seeing the attached error message in my WHMCS: 0 -
I assume based on the error it's related to the same issue you're facing with being unable to query the root nameservers. Do you have ports 53 and 953 open on the server? You can check this by running the following from a CLI outside/unrelated to your server: sudo nmap -sU -sT -p 53,953
Can you also please attach screenshots/images directly to the thread rather than link to a third party?0 -
The ports are opened as shown in the screenshot attached. 0 -
Great, so as long as dnsroots can query outbound, which it appears that it can. Essentially any time DNS resolution cannot be completed it will result in this or a similar error, the cause of that can be a lot of different things. In this thread we've gone over the most common and fixable issues. In most cases I can't do much as far as lookups go because I don't typically have the IP or domain name. In this instance since it was included in the original message and because it's in the screenshot you provided I checked a few things. - A trace gives a bad referral error (dig +trace domain.com.ng) - but this is most likely a result of the domain not being able to be added to the server
- specific to your server, I am wondering what querying for the root NS specifically results in. On my server that can reach Root NS I get the following when running this query for them:
for i in {a..m}; do echo -n "$i.root-servers.net: "; dig -4 "$i".root-servers.net @"$i".root-servers.net +short;donea.root-servers.net: 198.41.0.4 b.root-servers.net: 199.9.14.201 c.root-servers.net: 192.33.4.12 d.root-servers.net: 199.7.91.13 e.root-servers.net: 192.203.230.10 f.root-servers.net: 192.5.5.241 g.root-servers.net: 192.112.36.4 h.root-servers.net: 198.97.190.53 i.root-servers.net: 192.36.148.17 j.root-servers.net: 192.58.128.30 k.root-servers.net: 193.0.14.129 l.root-servers.net: 199.7.83.42 m.root-servers.net: 202.12.27.33
What do you get on your server? - We know inbound requests over TCP and UDP port 53 are successful, what about queries made outbound on those ports? For instance, if you run something like
traceroute -p 53 -U anydomain.com
ortraceroute -p 53 anydomain/IP
from the server - Ultimately I do believe that this would be best investigated over the ticket system, especially if the items I'm requesting come back without any anomalies.
0
Please sign in to leave a comment.
Comments
12 comments