Re: What is wrong in the view matching below

On 5 Dec 2019, at 13:49, Harshith Mulky wrote: > view "external" { > >   match-clients { any; }; > >   recursion no; > > zone "nixcraft.com" IN { > >     type master; > >     file "internet.master.nixcraft.com"; > >   }; > > }; > > view "internal" { > > match-clients { internal; }; > > allow-recur

Re: What is wrong in the view matching below

On Thu, Dec 5, 2019 at 8:49 AM Harshith Mulky wrote: > Thank you. I corrected this > > acl internal { >10.54.8.0/24; >localhost; > }; > > view "external" { > match-clients { any; }; > recursion no; > zone "nixcraft.com" IN { > type master; > file "internet.master.nixcraft.com"

Re: What is wrong in the view matching below

Thank you. I corrected this acl internal { 10.54.8.0/24; localhost; }; view "external" { match-clients { any; }; recursion no; zone "nixcraft.com" IN { type master; file "internet.master.nixcraft.com"; }; }; view "internal" { match-clients { internal; }; allow-recursion { any;

Re: What is wrong in the view matching below

There’s a space after com O. -- Ondřej Surý ond...@isc.org > On 5 Dec 2019, at 13:29, Sten Carlsen wrote: > >> >> zone "internal.nixcraft.com " IN { >> type master; >> file "lan.master.nixcraft.com"; >> }; >> }; > > Looks like the file lan.master.nixcraft.com has no data. > >> >>

Re: What is wrong in the view matching below

> > zone "internal.nixcraft.com " IN { > type master; > file "lan.master.nixcraft.com "; > }; > }; Looks like the file lan.master.nixcraft.com has no data. > > Dec 05 17:51:54 sataradnsVM1 named[4038]: zone internal.nixc

What is wrong in the view matching below

I have setup view matching as below on my bind server running version "bind-9.9.5P1-2.2.2.x86_64" my /etc/named.conf is as below options { directory "/var/lib/named"; #dnssec-enable yes; managed-keys-directory "/var/lib/named/dyn/"; dump-file "/var/log/named_dump

Re: function in DNS to provide an answer depending on the source of query.

On Thu, Dec 05, 2019 at 07:57:24AM +, Harshith Mulky wrote: > Is there a possibility to achieve this from a DNS > > If Carrier A (source IP: A.A.A.A) sends NAPTR query X to DNS, then DNS > replies NAPTR response Y. > > If Carrier B (source IP: B.B.B.B) sends NAPTR query X to DNS, then DNS > r

Re: function in DNS to provide an answer depending on the source of query.

Views (with source views) can do this. Once had a config with five views - terrible idea. On 2019/12/05 09:57, Harshith Mulky wrote: Hello, Is there a possibility to achieve this from a DNS If Carrier A (source IP: A.A.A.A) sends NAPTR query X to DNS, then DNS replies NAPTR response Y.