> for policies purpuose, we need to know which remote site is resolving a Bind
> 9.x public DNS Server.
> The problem occurs when some carriers "share" the same IP address between
> more customers and they surf behind a shared NAT.
>
> Is there a way?
You could use DNS Cookies (https://tools.ie
On 28.02.17 14:35, Job wrote:
for policies purpuose, we need to know which remote site is resolving a Bind
9.x public DNS Server.
The problem occurs when some carriers "share" the same IP address between more
customers and they surf behind a shared NAT.
Is there a way? Perhaps with DNS crypt o
Hi there,
On Tue, 28 Feb 2017, Job wrote:
for policies purpuose, we need to know which remote site is resolving a Bind
9.x public DNS Server.
The problem occurs when some carriers "share" the same IP address between more
customers and they surf behind a shared NAT.
Sounds like a trial.
Is
esday, February 28, 2017 2:35 PM
To: bind-users@lists.isc.org
Subject: Recognizing remote IP in shared connections
Hi,
for policies purpuose, we need to know which remote site is resolving a Bind
9.x public DNS Server.
The problem occurs when some carriers "share" the same IP address between
ut is so a large log file (as network accounting,
can't be live for "too much".
Alberto Colosi
IT NetWork & Security Architect Engineer
From: bind-users on behalf of Job
Sent: Tuesday, February 28, 2017 2:35 PM
To: bind-users@lists.isc.org
S
Hi,
for policies purpuose, we need to know which remote site is resolving a Bind
9.x public DNS Server.
The problem occurs when some carriers "share" the same IP address between more
customers and they surf behind a shared NAT.
Is there a way? Perhaps with DNS crypt o dnssec?
Thank you!
/F
___
6 matches
Mail list logo
