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 related Email

Discussion in 'Bind / DNS / Nameserver Issues' started by Stuff4me2win, Aug 25, 2012.

  1. Stuff4me2win

    Stuff4me2win Member

    Joined:
    Jul 25, 2012
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    I get the following email, and I don't know what to do to fix the issue described within. I believe the DNS is set up, the hosts file has an entry for webserver.centbomber.de, as I can ping the name from the server and get a returned IP address.

    I can't however, do a nslookup on webserver.centbomber.de.

    EMAIL:
    Code:
    -------
    Your hostname (webserver.centbomber.de) could not be resolved to an
    IP address. This means that /etc/hosts is not set up correctly,
    and/or there is no dns entry for webserver.centbomber.de. Please be
    sure that the contents of /etc/hosts are configured correctly, and
    also that there is a correct 'A' entry for the domain in the zone
    file.
    
    Some or all of these problems can be caused by /etc/resolv.conf
    being setup incorrectly. Please check that file if you believe
    everything else is correct.
    
    You may be able to automatically correct this problem by using the
    'Add an A entry for your hostname' option under 'Dns Functions' in
    your Web Host Manager.
    --------

    When I ping/nslookup/tracert webserver.centbomer.de from a remote PC, I get the following:


    Code:
    C:\Documents and Settings\an040ro>[B]ping webserver.centbomber.de[/B]
    
    Pinging webserver.centbomber.de [66.152.109.110] with 32 bytes of data:
    
    Request timed out.
    Request timed out.
    
    Ping statistics for 66.152.109.110:
        Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
    Control-C
    ^C
    C:\Documents and Settings\an040ro>[B]nslookup webserver.centbomber.de[/B]
    Server:  dns-cac-lb-01.rr.com
    Address:  209.18.47.61
    
    Non-authoritative answer:
    Name:    webserver.centbomber.de
    Addresses:  66.152.109.110, 69.16.143.110
    
    
    C:\Documents and Settings\an040ro>traceroute webserver.centbomber.de
    'traceroute' is not recognized as an internal or external command,
    operable program or batch file.
    
    C:\Documents and Settings\an040ro>[B]tracert webserver.centbomber.de[/B]
    
    Tracing route to webserver.centbomber.de [66.152.109.110]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.0.1
      2     *        *        *     Request timed out.
      3     8 ms     7 ms     7 ms  ten1-0-1.indp05-ser1.bhn.net [72.31.202.135]
      4    12 ms     9 ms    12 ms  ten0-0-0-3.indp10-car1.bhn.net [72.31.115.2]
      5    12 ms    12 ms    12 ms  ten1-0-0.indp10-cbr1.bhn.net [72.31.202.174]
      6    23 ms    24 ms    24 ms  ae4-10.ar01.clevohek.mwrtn.rr.com [65.189.143.26
    ]
      7    25 ms    23 ms    25 ms  ae1.tr00.clevohek.mwrtn.rr.com [65.189.140.130]
    
      8    33 ms    39 ms    39 ms  ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
      9    32 ms    33 ms    33 ms  107.14.19.135
     10    33 ms    34 ms    33 ms  te0-7-0-7.mpd22.iad02.atlas.cogentco.com [154.54
    .10.209]
     11    34 ms    33 ms    34 ms  te0-3-0-5.mpd22.dca01.atlas.cogentco.com [154.54
    .5.61]
     12    40 ms    45 ms    38 ms  te0-6-0-5.mpd22.jfk02.atlas.cogentco.com [154.54
    .42.38]
     13    51 ms    39 ms    40 ms  te9-8.mpd01.jfk01.atlas.cogentco.com [154.54.40.
    29]
     14    42 ms    44 ms    43 ms  te7-2.ccr01.alb02.atlas.cogentco.com [154.54.42.
    141]
     15    42 ms    55 ms    43 ms  38.104.52.10
     16    44 ms    45 ms    45 ms  ge-1-9.cr2.alb1.tvc-ip.com [66.109.38.161]
     17    46 ms    46 ms    44 ms  ge-2-2.es2.alb9.tvc-ip.com [66.109.38.194]
    
    
    
    When I do those same commands from the server I get these results:


    Code:
    root@webserver [/etc]# [B]ping webserver.centbomber.de[/B]
    PING webserver.centbomber.de (5.9.56.142) 56(84) bytes of data.
    64 bytes from webserver.centbomber.de (5.9.56.142): icmp_seq=1 ttl=64 time=0.021 ms
    64 bytes from webserver.centbomber.de (5.9.56.142): icmp_seq=2 ttl=64 time=0.016 ms
    64 bytes from webserver.centbomber.de (5.9.56.142): icmp_seq=3 ttl=64 time=0.019 ms
    ^C
    --- webserver.centbomber.de ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2122ms
    rtt min/avg/max/mdev = 0.016/0.018/0.021/0.005 ms
    root@webserver [/etc]# [B]nslookup webserver.centbomber.de[/B]
    Server:         8.8.8.8
    Address:        8.8.8.8#53
    
    ** server can't find webserver.centbomber.de: NXDOMAIN
    
    root@webserver [/etc]# [B]traceroute webserver.centbomber.de[/B]
    traceroute to webserver.centbomber.de (5.9.56.142), 30 hops max, 60 byte packets
     1  webserver.centbomber.de (5.9.56.142)  0.023 ms  0.009 ms  0.006 ms
    root@webserver [/etc]#
    I'm totally at a loss on this. Please help.
     
  2. cPanelJared

    cPanelJared Technical Analyst
    Staff Member

    Joined:
    Feb 25, 2010
    Messages:
    1,842
    Likes Received:
    18
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    ping is really not the most straightforward way to see what IP address a hostname resolves to. Instead, use host instead of ping or nslookup:

    Code:
    $ host webserver.centbomber.de
    Host webserver.centbomber.de not found: 3(NXDOMAIN)
    host just gives you the answer to "What IP address does this resolve to?" without sending out ping packets.

    I did a whois lookup and found that the following nameservers are listed as authoritative for the centbomber.de domain:

    Code:
    Nserver: ns1.first-ns.de
    Nserver: robotns2.second-ns.de
    Nserver: robotns3.second-ns.com
    I then used the dig command to query these nameservers directly, and found that they do not return A records for webserver.centbomber.de:

    Code:
    $ dig @ns1.first-ns.de a webserver.centbomber.de
    
    ; <<>> DiG 9.6-ESV-R4-P3 <<>> @ns1.first-ns.de a webserver.centbomber.de
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46916
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
    ;; WARNING: recursion requested but not available
    
    ;; QUESTION SECTION:
    ;webserver.centbomber.de.	IN	A
    
    ;; AUTHORITY SECTION:
    centbomber.de.		86400	IN	SOA	ns1.first-ns.de. postmaster.robot.first-ns.de. 2012082501 14400 1800 604800 86400
    
    ;; Query time: 133 msec
    ;; SERVER: 213.239.242.238#53(213.239.242.238)
    ;; WHEN: Mon Aug 27 08:41:56 2012
    ;; MSG SIZE  rcvd: 107
    
    $ dig @robotns2.second-ns.de a webserver.centbomber.de
    
    ; <<>> DiG 9.6-ESV-R4-P3 <<>> @robotns2.second-ns.de a webserver.centbomber.de
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26170
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
    ;; WARNING: recursion requested but not available
    
    ;; QUESTION SECTION:
    ;webserver.centbomber.de.	IN	A
    
    ;; AUTHORITY SECTION:
    centbomber.de.		86400	IN	SOA	ns1.first-ns.de. postmaster.robot.first-ns.de. 2012082501 14400 1800 604800 86400
    
    ;; Query time: 131 msec
    ;; SERVER: 213.133.105.6#53(213.133.105.6)
    ;; WHEN: Mon Aug 27 08:42:51 2012
    ;; MSG SIZE  rcvd: 107
    
    $ 
    $ dig @robotns3.second-ns.de a webserver.centbomber.de
    dig: couldn't get address for 'robotns3.second-ns.de': not found
    $ 
    
    As you can see, one of the nameservers, robotns3.second-ns.de, does not even resolve to an IP address.

    The three nameservers I just listed are the nameservers listed as authoritative in the whois output for centbomber.de, and they need to contain A records for webservers.centbomber.de in the DNS zone file for centbomber.de. Right now, they do not. Are these nameservers actually hosted on your server, or are they hosted externally? If they are hosted externally, then adding an A record on the server itself will have no effect.

    Since you are able to resolve the hostname to an IP address from inside the server, there may be a problem with BIND views. If the nameservers are hosted on your server, you can try this:

    Code:
    # /scripts/rebuilddnsconfig
    Then, restart the DNS service (either BIND/named, nsd, or MyDNS).

    If this does not help, please submit a ticket so that we can log into your server and look at your exact configuration.
     
Loading...

Share This Page