Dns & uribl

Discussion in 'Server Operation' started by DrJohn, Oct 13, 2011.

  1. DrJohn

    DrJohn Member

    This is Perfect Server Ubuntu 10.04. I recently changed DNS forwarders from my ISP-provided to a pair of the fastest (from here) public DNS sites: SpeakEasy and Google Public DNS. The ISP sites were about 5x slower and were returning advertising material for non-existent domains.

    In /etc/bind/named.conf.options:
    forwarders {
    		// Google Public DNS;
    I've always seen a number of DNS errors in the logs, like these from the ISP DNS servers:
    DNS format error from resolving dns1.name-services.com/AAAA: invalid response: 1 Time(s)
    error (FORMERR) resolving 'dns3.name-services.com/AAAA/IN': 17 Time(s)
    error (network unreachable) resolving '': 2001:7b8:3:1f:0:2:53:2#53: 1 Time(s)
    error (unexpected RCODE REFUSED) resolving '': 
    success resolving '' (in 'bb.barracudacentral.org'?) after disabling EDNS: 1 Time(s)
    but the number is small (< 50 per day) and there seems to be no impact.

    After changing the DNS servers, I see a couple of hundred errors related to URIBL DNS queries (out of a 10.04 VM running ISPConfig 2.2.40 / SA) like these (many different domains overall):
    error (unexpected RCODE REFUSED) resolving 'radisson.com.multi.uribl.com/A/IN': 1 Time(s)
    All of these were returned from the Google Public DNS server.
    In addition, I see about the same number of these and similar:
     error (network unreachable) resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53: 1 Time(s)
    error (network unreachable) resolving 'k.gtld-servers.net/AAAA/IN': 2001:7fd::1#53: 1 Time(s)
    error (network unreachable) resolving 'ns3.google.com/AAAA/IN': 2001:503:c27::2:30#53: 1 Time(s)
    I'd like to clear this up on the server. Is this a symptom of 1) a problem with the local Bind installation; 2) a problem with SA / URIBL; 3) a problem with the public DNS servers; 4) not a problem other than syslog inflation?

    Thanks !
  2. DrJohn

    DrJohn Member

    Apparently this is a problem with the Google Public DNS. I removed it from the list of forwarders and poof! no more such log entries.

    -- John

Share This Page