iew:
https://blog.apnic.net/2018/11/14/geoip-in-knot-dns-2-7/
Thanks
Angus
From: bind-users on behalf of Nick Tait via
bind-users
Sent: 16 May 2022 13:55
To: BIND Users Mailing List
Subject: Re: per record responses based on originating IP
On 16/05/22 20:05, Angus Cl
On 16/05/22 20:05, Angus Clarke wrote:
As mentioned in a separate reply to Grant, the goal is to have
(amongst other things) local recursors "find" the locally deployed
authoritative servers through NS records. What hasn't been mentioned
is that I am also looking to simplify configuration
alf of Nick Tait via
bind-users
Sent: 14 May 2022 02:34
To: bind-users@lists.isc.org
Subject: Re: per record responses based on originating IP
On 13/05/22 09:02, Grant Taylor via bind-users wrote:
On 5/12/22 2:41 PM, Nick Tait via bind-users wrote:
This sounds like exactly the sort of use case
On 5/15/22 7:28 AM, Angus Clarke wrote:
Hi Grant
Hi Angus,
maybe, I'm reading up ...
poking around the manual, are you alluding to the "sortlist" directive?
Yes, that's what I was referring to.
So the concern with returning an ordered RRset is that the set could be
large:
Okay.
I
RRset. Maybe I can limit a RRset response to the first X number of
entries?
Thanks
Angus
From: bind-users on behalf of Grant Taylor
via bind-users
Sent: 12 May 2022 18:11
To: bind-users@lists.isc.org
Subject: Re: per record responses based on originating IP
On 13/05/22 09:02, Grant Taylor via bind-users wrote:
On 5/12/22 2:41 PM, Nick Tait via bind-users wrote:
This sounds like exactly the sort of use case for Response Policy Zones:
How are you going to have RPZ return different addresses for different
clients? Are you suggesting use different
On 5/12/22 2:41 PM, Nick Tait via bind-users wrote:
This sounds like exactly the sort of use case for Response Policy Zones:
How are you going to have RPZ return different addresses for different
clients? Are you suggesting use different RPZs with different contents
for different clients?
On 13/05/2022 12:30 am, Angus Clarke wrote:
Does bind have some simple way to respond differently based on source
address but on a per record basis? Or perhaps include a baseline zone
in a view and separately include differences for that view - something
like this perhaps?
Hi Angus.
This
On 5/12/22 6:30 AM, Angus Clarke wrote:
Hello
Hi,
With bind (and others) it seems that DNS views are the way to go,
Before stepping up to views I'd stop to ask the question, would
returning multiple IPs in a preferred sort order suffice?
BIND has the ability to sort RRs differently
Hello
I'm familiar with Dan Bernstein's aging DNS software. With it I can add
location based responses to individual records, so that the DNS can respond
differently to a name lookup according to the source network/IP on a per-record
basis.
With bind (and others) it seems that DNS views are
10 matches
Mail list logo
