Fwd: Different answer when querying @server from different clients

2015-03-06 Thread Jeff Sadowski
P.S. I think that is an outdated method. It should break DNSSEC. Views from bind would probably be a better way. On Fri, Mar 6, 2015 at 3:52 PM, Arthur Ramsey wrote: > I had to disable DNS ALG on Juniper SRX series firewall. > > Thanks for the help, > Arthur > > > On 03/06/2015 04:51 PM, Jeff Sad

Re: Different answer when querying @server from different clients

2015-03-06 Thread Arthur Ramsey
I had to disable DNS ALG on Juniper SRX series firewall. Thanks for the help, Arthur On 03/06/2015 04:51 PM, Jeff Sadowski wrote: I remember a network engineer that rewrote some DNS entries with a cisco router replacing w.x.y.z with a.b.c.d On Fri, Mar 6, 2015 at 3:46 PM, Arthur Ramsey wrote:

Re: Different answer when querying @server from different clients

2015-03-06 Thread Arthur Ramsey
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.135 [root@dc01 ~]# dig +short ns2.mediture.com 107.23.33.118

Re: Different answer when querying @server from different clients

2015-03-06 Thread Steven Carr
On 6 March 2015 at 21:43, Arthur Ramsey wrote: > I can't figure out why these two hosts resolve great.truchart.com > differently when querying the authoritative server. DNS views have been implmented on your DNS server. > [root@dc01 ~]# dig +trace great.truchart.com @74.113.249.135 > great.truc

Different answer when querying @server from different clients

2015-03-06 Thread Arthur Ramsey
I can't figure out why these two hosts resolve great.truchart.com differently when querying the authoritative server. [root@dc01 ~]# dig +trace great.truchart.com @74.113.249.135 ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.1 <<>> +trace great.truchart.com @74.113.249.135 ;; global options:

Re: Too many connections on the same IP

2015-03-06 Thread John Wobus
Re firewalls: I've been forced to adjust firewall rules to be stateless to get busy DNS servers to work. If the state table is filling, that's easy to check. Stateless rules have traps for the unwary so assure yourself that you understand all the issues. Specifically, make sure return traffic isn'

Use the $client$ token in findzone query - Bind-DLZ

2015-03-06 Thread Job
Hello, regarding this post of some years ago: http://bind9-users.isc.narkive.com/aduGYTeB/dlz-client-parameter-segfault i would like is there is some hacks/workaround in order to use $client$ variable in other query, as example in the "findzone" query? Actually the source client token is availa