Re: Option in named to turn off EDNS Globally

2016-08-05 Thread Mark Andrews
In message , Harshith Mulky writes: > > I have tried enabling with the significant bits > > server 0.0.0.0/0 { edns no; }; > server ::/0 { edns no; }; > > > But, I get the following Error > > Error in named configuration: > /etc/named.conf:120: '{' expected near '/' > > Error in /var/log/m

Re: Option in named to turn off EDNS Globally

2016-08-05 Thread Nico CARTRON
Hi Harshith, > On 05 Aug 2016, at 08:47, Harshith Mulky wrote: > > I have tried enabling with the significant bits > > server 0.0.0.0/0 { edns no; }; > server ::/0 { edns no; }; > > But, I get the following Error > Error in named configuration: > /etc/named.conf:120: '{' expected near '/' > >

Re: Option in named to turn off EDNS Globally

2016-08-05 Thread Nico CARTRON
On 5 August 2016 at 09:15:29, Harshith Mulky (harshith.mu...@outlook.com) wrote: Hello Nico, This was only for Testing between 2 devices, 1 supporting edns and the other not supporting edns and checking how the Application behaves(lwresd and named) OK. Better also answering on the mailing lis

help

2016-08-05 Thread RAM MOHAN, Hari Ganesh
Hi There, We have two DNS views (HDQ and softlayer), Softlayer DNS view is configured with forwarder as loopback. This is working for all zones except few zones (Ex. Mi-testq03.pt) named.conf file, view "softlayer" { match-clients { "softlayer"; "softlayer-slaves"; "lnxd0006" }; forward only

Re: help

2016-08-05 Thread S Carr
On 5 August 2016 at 17:21, RAM MOHAN, Hari Ganesh wrote: > We are not able to understand that why we are not able to resolve > mi-testq03.pt whereas mi-testq03.fr is just working fine. There is an A record at the apex of the mi-testq03.pt zone, right? What do you get if you try to dig for the SOA

resigning of zones

2016-08-05 Thread Andreas Meyer
Hello! After what amount of time a zone is resigned by named when it was edited? Regards Andreas ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https

RE: help

2016-08-05 Thread RAM MOHAN, Hari Ganesh
Yes. You are right there is A record at the apex. Dig SOA gives two different results, It tells SERVFAIL and then NXDOMAIN [dns@lnxd0006 ~]$ dig mi-testq03.pt SOA ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.8 <<>> mi-testq03.pt SOA ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- op

Re: help

2016-08-05 Thread S Carr
On 5 August 2016 at 19:26, RAM MOHAN, Hari Ganesh wrote: > > Dig SOA gives two different results, It tells SERVFAIL and then NXDOMAIN > Check your BIND logs to make sure the zone has been successfully transferred from the master. ___ Please visit https:

RE: help

2016-08-05 Thread RAM MOHAN, Hari Ganesh
Yes, zone has transferred successfully. Aug 5 18:44:16 ncldl38037 named[8532]: client 162.130.128.167#33747 (mi-testq03.pt): view hdq: transfer of 'mi-testq03.pt/IN': AXFR-style IXFR started Aug 5 18:44:16 ncldl38037 named[8532]: client 162.130.128.167#33747 (mi-testq03.pt): view hdq: transfe