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
sorry, let me only to add a comment to previous mail
if who make the query use a DNS Forwarding System (like use ISP DNS as
forwarders or direct resolver) you'll only have ISP DNS on last forward action
From: bind-users on behalf of Job
Sent: Tuesday, Febru
Hi, let me to say that is a bit strange what you say. If you mean a NAT many to
1 can't be reached in reverse way but "many" can only exit and receive reply
packets for esthabilished session or udp related packet
if you mean for example an application server that give as output different web
c
Hi,
thank you all for the replies. "Don't do it" was also my first thought.
Andrea
Il 24/02/2017 21:19, /dev/rob0 ha scritto:
> On Fri, Feb 24, 2017 at 02:05:54PM -0500, Warren Kumari wrote:
>> --
>> I don't think the execution is relevant when it was obviously
>> a bad idea in the first place.
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
