Re: Recognizing remote IP in shared connections

2017-03-01 Thread Alex Dupuy via bind-users
> 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

Re: Recognizing remote IP in shared connections

2017-02-28 Thread Matus UHLAR - fantomas
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

Re: Recognizing remote IP in shared connections

2017-02-28 Thread G.W. Haywood
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

Re: Recognizing remote IP in shared connections

2017-02-28 Thread Alberto Colosi
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

Re: Recognizing remote IP in shared connections

2017-02-28 Thread Alberto Colosi
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