Re: Different answer when querying @server from different clients

2015-03-08 Thread Barry S. Finkel
On 3/6/2015 4:52 PM, bind-users-requ...@lists.isc.org wrote: I don't think it is views. The same thing happens against Google's public DNS. The two hosts route to the Internet differently and that seems to at the root of the issue somehow. [root@dc01 ~]# dig +short ns1.mediture.com 74.113.249.

Re: Different answer when querying @server from different clients

2015-03-08 Thread Steven Carr
On 8 March 2015 at 13:50, Barry S. Finkel wrote: > Using "+trace" with "@8.8.8.8" ignores the "@8.8.8.8", as > that server is never queried when the query starts at the root > and moves down the DNS tree to authorized servers. Incorrect, specifying @8.8.8.8 means that dig +trace will use 8.8.8.8

BIND 9.10 IPv6 performance

2015-03-08 Thread Carsten Strotmann
Hi, I'm doing some performance tests on some modern Haswell CPU machines (20 cores) using Ubuntu Linux 14.04 (Kernel 3.13.0-46-generic) using BIND 9.10.1-P2 compiled with "--with-tuning=large". With using 8 worker threads I get near 400K QPS via IPv4 UDP (from a hot cache without resolving), whic

BIND9 statistics vs. BIND8 statistics

2015-03-08 Thread Dowon Kim
Hello, In BIND8, I can find statistics every hour in the log file (see here below) It was the default for BIND8 But in BIND9 I do not find same statistics in the log file. I know statistics-channels usage in named.conf or rndc stats with dump statistics file I define with statistics-file statement