Ruben, thank you very much! This is what I need.
21.03.2012, в 2:06, Ruben d'Arco написал(а):
> Hi,
>
> I think these links might be useful for you:
> http://tools.ietf.org/html/draft-vandergaast-edns-client-subnet-00
> http://wilmer.gaa.st/edns-client-subnet/
>
> I'm not sure, but i believe th
Hi,
I think these links might be useful for you:
http://tools.ietf.org/html/draft-vandergaast-edns-client-subnet-00
http://wilmer.gaa.st/edns-client-subnet/
I'm not sure, but i believe the pipebackend uses the ip address from the
edns-client-subnet and if that does not exist, falls back to the s
On Wed, Mar 21, 2012 at 01:55:06AM +0400, Mikhail Nasonov wrote:
> Hello!
>
> Please tell, is it possible to determine the IP address source from which
> request was initialized? PipeBackend have the option "remote-ip-address", but
> it shows the IP address of the final request (usually this is
Hello!
Please tell, is it possible to determine the IP address source from which
request was initialized? PipeBackend have the option "remote-ip-address", but
it shows the IP address of the final request (usually this is the DNS server of
the user, not his personal address).
Thank you in advan
Hi,
On my debian stable (recursor 3.2) i have the same result.
On the current SVN, this work as you expect it.
I suggest you try a newer version of the recursor.
Regards,
Ruben
On Tue, Mar 20, 2012 at 01:10:25PM -0500, k...@rice.edu wrote:
> Hi PDNS community,
>
> I am investigating a
Hi PDNS community,
I am investigating a CNAME resolution problem using
PDNS Recursor 3.3.1. Here is the lookup that fails:
> nslookup blog.mythandsymbol.com
Server: 127.0.0.1
Address:127.0.0.1#53
** server can't find blog.mythandsymbol.com: NXDOMAIN
Is is actually a CNAME:
> ns
