The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

DNS Issue (layer2.cpanel.net)

Discussion in 'Bind / DNS / Nameserver Issues' started by ChrisFirth, Nov 11, 2009.

  1. ChrisFirth

    ChrisFirth Active Member
    PartnerNOC

    Joined:
    Apr 10, 2008
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    cPanel Access Level:
    DataCenter Provider
    Hi all,

    We have a few cPanel servers that have been running without an issue for a while. I noticed today when I run /scripts/upcp we get the following message:

    Fetching Installer...layer2.cpanel.net could not be resolved to an ip adddress, please check your /etc/resolv.conf at /scripts/cPScript/HttpRequest.pm line 318.

    We have our own caching name servers (running djbdns dnscache), and every other name resolves fine.

    The issue seems to be a timeout happening somewhere as the name seems to resolve fine (I have been testing by using the systems getaddrinfo() and res_query() to make sure that the system resolver is working correctly). It does take a long period of time to resolve, but it does get there in the end.

    To see if the issue was with our DNS servers, I switched over to a large ISP's caching name servers (which are running Bind). The issue also seems to happen there, the name does resolve although it does take while to happen and the 'upcp' script seems to still fail.

    I have tested this on a few different cPanel servers (some running Fedora 7, others running CentOS 5.4) and the issue is present on both distributions.

    I have also seen this happen for new cPanel installs recently, I have had to edit the script that attempts to do a lookup and add an exit to the top so that it would actually let me install cPanel.

    Also, in some cases I have noticed when testing using 'host' I can see the following happen:
    Code:
    [root@cpanel12 ~]# host layer2.cpanel.net 203.0.178.191
    
    Using domain server:
    Name: 203.0.178.191
    Address: 203.0.178.191#53
    Aliases:
    
    layer2.cpanel.net is an alias for httpupdate.cpanel.net.
    httpupdate.cpanel.net has address 8.10.120.130
    httpupdate.cpanel.net has address 64.50.161.11
    httpupdate.cpanel.net has address 67.159.2.2
    httpupdate.cpanel.net has address 67.205.110.4
    httpupdate.cpanel.net has address 67.222.0.10
    httpupdate.cpanel.net has address 67.227.128.74
    httpupdate.cpanel.net has address 69.50.192.73
    httpupdate.cpanel.net has address 69.72.212.10
    httpupdate.cpanel.net has address 69.73.140.17
    httpupdate.cpanel.net has address 69.90.250.34
    httpupdate.cpanel.net has address 69.90.250.35
    httpupdate.cpanel.net has address 70.87.220.252
    httpupdate.cpanel.net has address 72.233.42.250
    httpupdate.cpanel.net has address 74.50.120.123
    httpupdate.cpanel.net has address 74.200.212.130
    httpupdate.cpanel.net has address 75.126.236.226
    httpupdate.cpanel.net has address 75.127.84.226
    httpupdate.cpanel.net has address 208.43.129.162
    httpupdate.cpanel.net has address 208.74.121.39
    httpupdate.cpanel.net has address 208.74.123.21
    httpupdate.cpanel.net has address 208.78.42.4
    httpupdate.cpanel.net has address 208.82.118.100
    httpupdate.cpanel.net has address 208.109.109.239
    httpupdate.cpanel.net has address 209.85.80.214
    httpupdate.cpanel.net has address 216.38.56.98
    httpupdate.cpanel.net has address 216.104.43.138
    
    ;; connection timed out; no servers could be reached
    
    Additionally, when using our own DNS servers, quite often we do not get ANY addresses returned, which appears to be caused by a lookup failing somewhere along the line.

    Has anyone come across the same issue before?

    Thanks
     
  2. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    DNS resolver Issues ( /etc/resolv.conf )

    I would try a set of known-working DNS resolvers, such as the following:
    Code:
    4.2.2.1
    4.2.2.2
    4.2.2.3
    As an alternative, if you don't mind registering your IP ranges to disable certain unnecessary features I personally would also consider using the free "Basic" service from OpenDNS; if using OpenDNS it is necessary to register a free account and setup your IP ranges to disable "typo correction" and the "OpenDNS proxy" to ensure the resolver functionality works correctly.
     
    #2 cPanelDon, Nov 12, 2009
    Last edited: Nov 12, 2009
Loading...

Share This Page