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.

Named Erros in Logwatch

Discussion in 'General Discussion' started by tones_ie, Aug 21, 2013.

  1. tones_ie

    tones_ie Registered

    Joined:
    May 7, 2006
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Hi Guys,

    New WHM / Cpanel install on CENTOS 6.4 i686. I never saw any of these on my old server
    Logwatch reports hundreds of erros ....see below for sample....I have attached the full report too in case that was needed.....

    Can someone please explain what all these errors mean and what if anything i need to do to correct

    Code:
    error (FORMERR) resolving 'admin2.getthescoop.in/AAAA/IN': 184.172.63.127#53: 1 Time(s)
        error (FORMERR) resolving 'admin2.getthescoop.in/AAAA/IN': 208.43.116.42#53: 1 Time(s)
        error (FORMERR) resolving 'admin2.getthescoop.in/AAAA/IN': 23.23.82.169#53: 1 Time(s)
        error (FORMERR) resolving 'customer3.changeforlife.in/AAAA/IN': 184.172.63.127#53: 1 Time(s)
        error (FORMERR) resolving 'customer3.changeforlife.in/AAAA/IN': 208.43.116.42#53: 1 Time(s)
        error (FORMERR) resolving 'customer3.changeforlife.in/AAAA/IN': 23.23.82.169#53: 1 Time(s)
        error (FORMERR) resolving 'helper3.changeforlife.in/AAAA/IN': 184.172.63.127#53: 2 Time(s)
        error (FORMERR) resolving 'helper3.changeforlife.in/AAAA/IN': 208.43.116.42#53: 2 Time(s)
        error (FORMERR) resolving 'helper3.changeforlife.in/AAAA/IN': 23.23.82.169#53: 2 Time(s)
        error (FORMERR) resolving 'hotmai.com/AAAA/IN': 207.46.75.254#53: 16 Time(s)
        error (FORMERR) resolving 'hotmai.com/AAAA/IN': 213.199.180.53#53: 16 Time(s)
    error (network unreachable) resolving '10.186.208.192.in-addr.arpa/PTR/IN': 2607:ff50:0:19::2#53: 1 Time(s)
        error (network unreachable) resolving '10.6.184.2.in-addr.arpa/PTR/IN': 2001:660:3006:1::1:1#53: 1 Time(s)
        error (network unreachable) resolving '100.180.234.91.zen.spamhaus.org/TXT/IN': 2001:7b8:3:1f:0:2:53:2#53: 1 Time(s)
        error (network unreachable) resolving '100.81.222.67.zen.spamhaus.org/A/IN': 2001:7b8:3:1f:0:2:53:1#53: 1 Time(s)
        error (network unreachable) resolving '102.81.222.67.zen.spamhaus.org/A/IN': 2001:7b8:3:1f:0:2:53:1#53: 1 Time(s)
        error (network unreachable) resolving '103.103.188.199.zen.spamhaus.org/TXT/IN': 2001:7b8:3:1f:0:2:53:2#53: 1 Time(s)
        error (network unreachable) resolving '103.125.122.199.in-addr.arpa/PTR/IN': 2001:470:1a::2#53: 1 Time(s)
        error (network unreachable) resolving '103.125.122.199.in-addr.arpa/PTR/IN': 2001:500:13::63#53: 1 Time(s)
        error (network unreachable) resolving '103.125.122.199.in-addr.arpa/PTR/IN': 2001:500:31::63#53: 1 Time(s)
    error (unexpected RCODE REFUSED) resolving '15.0/26.192.255.213.in-addr.arpa/PTR/IN': 41.222.216.20#53: 4 Time(s)
        error (unexpected RCODE REFUSED) resolving '153.109.4.142.in-addr.arpa/PTR/IN': 199.180.100.29#53: 4 Time(s)
        error (unexpected RCODE REFUSED) resolving '153.109.4.142.in-addr.arpa/PTR/IN': 64.71.150.196#53: 4 Time(s)
        error (unexpected RCODE REFUSED) resolving '153.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53: 1 Time(s)
        error (unexpected RCODE REFUSED) resolving '153.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53: 1 Time(s)
        error (unexpected RCODE REFUSED) resolving '154.109.4.142.in-addr.arpa/PTR/IN': 199.180.100.29#53: 4 Time(s)
        error (unexpected RCODE REFUSED) resolving '154.109.4.142.in-addr.arpa/PTR/IN': 64.71.150.196#53: 4 Time(s)
        error (unexpected RCODE REFUSED) resolving '155.109.4.142.in-addr.arpa/PTR/IN': 199.180.100.29#53: 4 Time(s)
      error (unexpected RCODE SERVFAIL) resolving '129.120.163.79.in-addr.arpa/PTR/IN': 193.0.9.6#53: 1 Time(s)
        error (unexpected RCODE SERVFAIL) resolving '132.37.173.205.in-addr.arpa/PTR/IN': 205.173.38.253#53: 11 Time(s)
        error (unexpected RCODE SERVFAIL) resolving '132.37.173.205.in-addr.arpa/PTR/IN': 205.173.38.254#53: 11 Time(s)
        error (unexpected RCODE SERVFAIL) resolving '139.223.175.61.in-addr.arpa/PTR/IN': 202.96.103.36#53: 4 Time(s)
        error (unexpected RCODE SERVFAIL) resolving '139.223.175.61.in-addr.arpa/PTR/IN': 202.96.104.18#53: 4 Time(s)
        error (unexpected RCODE SERVFAIL) resolving '171.3.47.188.in-addr.arpa/PTR/IN': 193.0.9.6#53: 1 Time(s)
        error (unexpected RCODE SERVFAIL) resolving '183.201.129.192.in-addr.arpa/PTR/IN': 199.59.62.3#53: 1 Time(s)
        error (unexpected RCODE SERVFAIL) resolving '193.108.120.50.in-addr.arpa/PTR/IN': 199.224.64.201#53: 25 Time(s)
    
    Thanks in advance
     

    Attached Files:

  2. quietFinn

    quietFinn Well-Known Member

    Joined:
    Feb 4, 2006
    Messages:
    998
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    Finland
    cPanel Access Level:
    Root Administrator
    1st you should check the resolver:
    /etc/resolv.conf

    you can also check in command line, for ex:
     
  3. tones_ie

    tones_ie Registered

    Joined:
    May 7, 2006
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Hi quietFinn

    resolv.conf shows the following
    nameserver 127.0.0.1
    nameserver 8.8.8.8
    nameserver 8.8.4.4


    nslookup shows this
    root@host [~]# nslookup google.com
    Server: 127.0.0.1
    Address: 127.0.0.1#53

    Non-authoritative answer:
    Name: google.com
    Address: 74.125.225.230
    Name: google.com
    Address: 74.125.225.233
    Name: google.com
    Address: 74.125.225.227
    Name: google.com
    Address: 74.125.225.224
    Name: google.com
    Address: 74.125.225.228
    Name: google.com
    Address: 74.125.225.232
    Name: google.com
    Address: 74.125.225.226
    Name: google.com
    Address: 74.125.225.238
    Name: google.com
    Address: 74.125.225.229
    Name: google.com
    Address: 74.125.225.225
    Name: google.com
    Address: 74.125.225.231

    Appreciate the help...
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    The messages in your initial post can occur when the endpoint is unable to be sent the rcode (return code) with a specific zone. You could add the following entry to the logging section in /etc/named.conf to silence these messages:

    Code:
    category lame-servers { null; };
    Thank you.
     
  5. tones_ie

    tones_ie Registered

    Joined:
    May 7, 2006
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Hi cPanelMichael

    Thanks for the reply.....so to confirm, its not a misconfiguration of server / whm and i can safely add the code to ignore the logging ?
     
  6. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Assuming you have confirmed there are no problems with your DNS resolvers, then those warning messages should not pose an issue.

    Thank you.
     
  7. tones_ie

    tones_ie Registered

    Joined:
    May 7, 2006
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Thanks again guys :)
     
Loading...

Share This Page