On 15 August 2014 12:05, Chuck Campbell <campbell@xxxxxxxxxxxx> wrote:
> I must have something mis-configured in my bond setup. Things are working,
> but
> I'm getting TONS of this sort of stuff in my log:
>
> +2001:502:ad09::4#53: 1 Time(s)
> network unreachable resolving 'kns1.kuwaitnet.net/A/IN':
> +2001:503:231d::2:30#53: 1 Time(s)
> network unreachable resolving 'kns1.kuwaitnet.net/A/IN':
> +2001:503:a83e::2:30#53: 1 Time(s)
> network unreachable resolving 'kns1.kuwaitnet.net/AAAA/IN':
> +2001:503:231d::2:30#53: 1 Time(s)
> network unreachable resolving 'kns1.kuwaitnet.net/AAAA/IN':
> +2001:503:a83e::2:30#53: 1 Time(s)
> network unreachable resolving 'kns2.kuwaitnet.net/A/IN':
> +2001:503:231d::2:30#53: 1 Time(s)
> network unreachable resolving 'kns2.kuwaitnet.net/A/IN':
> +2001:503:a83e::2:30#53: 1 Time(s)
> network unreachable resolving 'kns2.kuwaitnet.net/AAAA/IN':
> +2001:503:231d::2:30#53: 1 Time(s)
> network unreachable resolving 'kns2.kuwaitnet.net/AAAA/IN':
> +2001:503:a83e::2:30#53: 1 Time(s)
> network unreachable resolving 'kns3.kuwaitnet.net/A/IN':
> +2001:503:231d::2:30#53: 1 Time(s)
> network unreachable resolving 'kns3.kuwaitnet.net/A/IN':
> +2001:503:a83e::2:30#53: 1 Time(s)
> network unreachable resolving 'kns3.kuwaitnet.net/AAAA/IN':
> +2001:503:231d::2:30#53: 1 Time(s)
>
> I'm not sure where to look. it may be the "any" in the named.conf lines
> below,
> but I'm not sure.
> My named.conf looks like this:
> options {
> listen-on port 53 { 127.0.0.1; any; };
> # listen-on-v6 port 53 { ::1; };
> directory "/var/named";
> dump-file "/var/named/data/cache_dump.db";
> statistics-file "/var/named/data/named_stats.txt";
> memstatistics-file "/var/named/data/named_mem_stats.txt";
>
> // Those options should be used carefully because they disable port
> // randomization
> // query-source port 53;
> // query-source-v6 port 53;
>
> allow-query { localhost; any; };
> allow-query-cache { localhost; any; };
> # allow-query { localhost; };
> # allow-query-cache { localhost; };
> };
> logging {
> channel default_debug {
> file "data/named.run";
> severity dynamic;
> };
> };
> view localhost_resolver {
> match-clients { localhost; any; };
> match-destinations { localhost; any; };
> # match-clients { localhost; };
> # match-destinations { localhost; };
> recursion yes;
> include "/etc/named.rfc1912.zones";
> };
>
> --
> ACCEL Services, Inc.| Specialists in Gravity, Magnetics | (713)993-0671
> ph.
> | and Integrated Interpretation | (713)993-0608
> fax
> 448 W. 19th St. #325| Since 1992 | (713)306-5794
> cell
> Houston, TX, 77008 | Chuck Campbell |
> campbell@xxxxxxxxxxxx
> | President & Senior Geoscientist |
>
> "Integration means more than having all the maps at the same scale!"
>
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
> Have you tried starting the bind daemon with -4, or IPv4 only?
--
Gardner Bell
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
