Re: 9.3.3 - SPF record checks

In message <1369953470.1952.58.camel@jhorne.config>, John Horne writes: > On Fri, 2013-05-31 at 06:53 +1000, Mark Andrews wrote: > > In message <1369923655.1952.6.camel@jhorne.config>, John Horne writes: > > > Hello, > > > > > > I noticed in the 9.3.3 announcement the following new SPF check: > >

Re: 9.3.3 - SPF record checks

On Fri, 2013-05-31 at 06:53 +1000, Mark Andrews wrote: > In message <1369923655.1952.6.camel@jhorne.config>, John Horne writes: > > Hello, > > > > I noticed in the 9.3.3 announcement the following new SPF check: > > > >Adds a new configuration option, "check-spf"; valid values are > >"war

Re: 9.3.3 - SPF record checks

In message <1369923655.1952.6.camel@jhorne.config>, John Horne writes: > Hello, > > I noticed in the 9.3.3 announcement the following new SPF check: > >Adds a new configuration option, "check-spf"; valid values are >"warn" (default) and "ignore". When set to "warn", checks SPF >and

9.3.3 - SPF record checks

Hello, I noticed in the 9.3.3 announcement the following new SPF check: Adds a new configuration option, "check-spf"; valid values are "warn" (default) and "ignore". When set to "warn", checks SPF and TXT records in spf format, warning if either resource record type occurs without a

Re: Help on NXDOMAIN to try next forwarder in the list

In article , Ashok Agarwal wrote: > Sorry, its not */etc/hosts* file rather its */etc/resolv.conf*. > > > On Thu, May 30, 2013 at 1:25 PM, Ashok Agarwal > wrote: > > > One possible way can also be to set the number of nameservers to be looked > > upon in the /etc/hosts file. > > > > nameserve

Re: Help on NXDOMAIN to try next forwarder in the list

So your administrator is breaking DNS if all 3 servers have been added as NS records but the zone is not available on all 3 servers. Get him/her to fix your DNS hierarchy first then you wont need to check which server is hosting the subdomain. Steve On 30 May 2013 10:30, sumsum 2000 wrote: > Hi

Re: Help on NXDOMAIN to try next forwarder in the list

Hi, This is a non-standard behavior and I would like to have the following: In the case where I am working on, /etc/resolv.conf contains localhost 127.0.0.1 and BIND is listening on localhost port 53 as non-authoritative DNS So all the requests are sent through 127.0.0.1 and based on the domai

Re: Help on NXDOMAIN to try next forwarder in the list

Well you can do that. It does not change the fact that NXDOMAIN is a DEFINITIVE answer - it does not exist, there is no reason to look further. On 30/05/13 9:56, Ashok Agarwal wrote: > Sorry, its not */etc/hosts* file rather its */etc/resolv.conf*. > > > On Thu, May 30, 2013 at 1:25 PM, Ashok Ag

Re: Help on NXDOMAIN to try next forwarder in the list

Sorry, its not */etc/hosts* file rather its */etc/resolv.conf*. On Thu, May 30, 2013 at 1:25 PM, Ashok Agarwal wrote: > One possible way can also be to set the number of nameservers to be looked > upon in the /etc/hosts file. > > nameserver 8.8.8.8 > nameserver 4.4.2.2 > nameserver 4.1.2.2 > > R

Re: Help on NXDOMAIN to try next forwarder in the list

One possible way can also be to set the number of nameservers to be looked upon in the /etc/hosts file. nameserver 8.8.8.8 nameserver 4.4.2.2 nameserver 4.1.2.2 Regards, Ashok On Thu, May 30, 2013 at 1:05 PM, Steven Carr wrote: > It's not possible. NXDOMAIN is NXDOMAIN, it doesn't exist, it d

Re: Help on NXDOMAIN to try next forwarder in the list

It's not possible. NXDOMAIN is NXDOMAIN, it doesn't exist, it doesn't mean try another server to see if you get lucky next time. Steve On 30 May 2013 08:26, sumsum 2000 wrote: > Hi, > I have the following change to be available from BIND9. > > I have zone forwarders as follows with BIND9 setup

Help on NXDOMAIN to try next forwarder in the list

Hi, I have the following change to be available from BIND9. I have zone forwarders as follows with BIND9 setup with forward only option on a Non Authoritative DNS server zone "mytestdomain101.com" IN { type forward; forwarders {8.8.8.8;4.2.2.1;8.8.4.4}; forward only; };