Re: How to I prevent sending additional data to everybody?

2019-03-05 Thread Grant Taylor via bind-users
On 03/05/2019 12:07 PM, Tony Finch wrote: It's not clear to me where the zone cuts are, but I guess what you are seeing is a referral when outside the allow-recursion ACL, so the server thinks glue is required; and no additional data inside the allow-recursion ACL because there's no referral when

Re: How to I prevent sending additional data to everybody?

2019-03-05 Thread Tony Finch
Grant Taylor via bind-users wrote: > > My test query is returning the A record for an NS that is out of zone but in a > different zone on the same server. > > something.aaa.example.net.NS ns1.bbb.example.net. > > dig is still showing ns1.bbb.example.net's A record in additional data when

Re: How to I prevent sending additional data to everybody?

2019-03-05 Thread Grant Taylor via bind-users
On 03/05/2019 10:51 AM, Tony Finch wrote: There's an old entry in the CHANGES file: 912. [bug] Attempts to set the 'additional-from-cache' or 'additional-from-auth' option to 'no' in a server with recursion enabled will now

Re: How to I prevent sending additional data to everybody?

2019-03-05 Thread Tony Finch
Grant Taylor via bind-users wrote: > > options { > … > additional-from-auth no; > additional-from-cache no; > allow-recursion { myACL; }; > // recursion no; > … > }; There's an old entry in the CHANGES file: 912. [bug] Attempts to set the 'additio

How to I prevent sending additional data to everybody?

2019-03-05 Thread Grant Taylor via bind-users
Hi, I need some help understanding why the following doesn't work as desired. I want to 1) allow recursion from subnets defined in myACL, 2) block recursion from the rest of the world, and 3) not return any additional data to anybody. options { … additional-from-auth no;

Re: Problems removing a domain

2019-03-05 Thread Matus UHLAR - fantomas
On 05.03.19 14:41, Paul van der Vlis wrote: This was a long time ago. In the meantime I have rebooted the server. What I see, is that the resolving does not work from other locations. Only when I use my own nameserver the domain is resolved, and it gives an "Non-authoritative answer". both ki

Re: Problems removing a domain

2019-03-05 Thread Paul van der Vlis
Op 05-03-19 om 15:21 schreef Matus UHLAR - fantomas: >>> On 05/03/2019 01:01, Paul van der Vlis wrote: Not sure. It was a domain used for testing purposes. Before it was in /etc/bind/named.conf.local, but I removed it from there. > >> Op 05-03-19 om 11:51 schreef Anand Buddhdev

Re: Problems removing a domain

2019-03-05 Thread Matus UHLAR - fantomas
On 05/03/2019 01:01, Paul van der Vlis wrote: Not sure. It was a domain used for testing purposes. Before it was in /etc/bind/named.conf.local, but I removed it from there. Op 05-03-19 om 11:51 schreef Anand Buddhdev: Did you run "rndc reconfig" after removing it from the named.conf.local fi

Re: Problems removing a domain

2019-03-05 Thread Paul van der Vlis
Op 05-03-19 om 11:51 schreef Anand Buddhdev: > On 05/03/2019 01:01, Paul van der Vlis wrote: > >> Not sure. It was a domain used for testing purposes. >> >> Before it was in /etc/bind/named.conf.local, but I removed it from there. > > Did you run "rndc reconfig" after removing it from the named.c

Re: Problems removing a domain

2019-03-05 Thread Anand Buddhdev
On 05/03/2019 01:01, Paul van der Vlis wrote: > Not sure. It was a domain used for testing purposes. > > Before it was in /etc/bind/named.conf.local, but I removed it from there. Did you run "rndc reconfig" after removing it from the named.conf.local file? Anand