Finally got it fixed.
Did this, isolated the backend, made a pcap of the production site of the
traffic flowing from pdns -> backend and filtered that to get the json’s and
use those as input/real queries was ~350 queries.
A new python script, simple one with requests module using those jsons
Yes, I’m on it right now.
Changes are very often, mongo is in ssd and I’m querying by the _id that is
indexed, plus I’m using a mongo replica (it’s supposed to be a benefit for
reading)
But yes, I’m right now doing exactly what you told, writing an http test unit
in golang to heavily charge
On 29/11/2023 14:04, Alexis Fidalgo wrote:
So, by now, i dont know what is making for a query to be answered and
another not (timeout) and in a retry is answered ok. (this is why i
thought on speed and considered the unix socket but now i know it’s
not that)
Put logging in your remote
On 29/11/2023 10:19, Alexis Fidalgo wrote:
by the responder, what im not understanding is, why in 2 different languages
(golang and python) i get the same behavior.
Well, you haven't shown the code from either.
It would be extremely inefficient for PowerDNS to open a new connection for
> On 29 Nov 2023, at 05:00, Brian Candler wrote:
>
> On 29/11/2023 00:07, Alexis Fidalgo via Pdns-users wrote:
>> I think i found why this is not working, as you can see below, socket is
>> connected and first message is sent (the initialize message), which is
>> answered and the response is
On 29/11/2023 00:07, Alexis Fidalgo via Pdns-users wrote:
I think i found why this is not working, as you can see below, socket
is connected and first message is sent (the initialize message), which
is answered and the response is read ({“result”: true}).
Problem is (and i’ve testing with
I think i found why this is not working, as you can see below, socket is
connected and first message is sent (the initialize message), which is answered
and the response is read ({“result”: true}).
Problem is (and i’ve testing with golang and python) after the answer the
“initialize” message,
has to be on my side. i made a change in the way i read/write to the socket and
now i get
socket(AF_UNIX, SOCK_STREAM, 0) = 12
connect(12, {sa_family=AF_UNIX, sun_path="/tmp/pra.sock"}, 110) = 0
write(12, "{\"method\": \"initialize\", \"parame"..., 66) = 66
poll([{fd=12,
the mail with the whole strace is kept because of the attach but i can see this
sendto(3, "<30>Nov 28 16:17:46 pdns[167106]"..., 57, MSG_NOSIGNAL, NULL, 0) = 57
socket(AF_UNIX, SOCK_STREAM, 0) = 12
connect(12, {sa_family=AF_UNIX, sun_path="/tmp/pra.sock"}, 110) = 0
write(12,
Hi!
On 28/11/2023 19:59, Alexis Fidalgo via Pdns-users wrote:
Sorry about that, yes, this will work locally, meaning the remote
responder (my script) will run on the same VM than pdns-auth, so
pdns-auth will connect using a unix socket with the responder using
remote backend.
That actually
Sorry about that, yes, this will work locally, meaning the remote responder (my
script) will run on the same VM than pdns-auth, so pdns-auth will connect using
a unix socket with the responder using remote backend.
That actually occurs, this is what is shown from the pdns
---
alz@nuc
In that case, one of the common problems found when switching to Unix
sockets is that the reading process needs to have Read access to the Unix
socket (this also means that process must be able to traverse to the
directory containing the Unix socket).
Please check your file system permissions.
On 28/11/2023 18:10, Walter Parker via Pdns-users wrote:
Unclear as to what you mean by “remote backend connected using Unix
sockets”
See: https://doc.powerdns.com/authoritative/backends/remote.html
"Remote backend" in this case means "out-of-process", not necessarily on
a different server.
Unclear as to what you mean by “remote backend connected using Unix sockets”
If you mean that you wish to have a process on another system connect using
Unix sockets, that will not work. Unix sockets only work locally. TCP
sockets (which is what HTTP uses) are what is required for connections
Hello all, i have a running remote backend using http with no problems at all,
everything runs smoothly.
Now i need to enable unix sockets, so the remote backend is not connected
anymore using http but unix socket.
Nothing has changed beside to listen in the unix socket, meaning im returning
Hi there,
Reading the documentation on Dynamic DNS, I am not clear on if the remote
backend is supported if I want to use Dynamic DNS.
https://doc.powerdns.com/authoritative/dnsupdate.html
The documentation lists the backends, but simply says that those backends
have been modified to support
Hi Chris,
Adding my 2cts:
On Sat, 23 Feb 2019, bert hubert wrote:
On Sat, Feb 23, 2019 at 08:12:40PM +1100, Chris Jones wrote:
Thanks Bert, but I don’t understand how my backend is doing too much work?
How does PowerDNS know what the zone is if my backend doesn’t figure it out?
Chris,
On Sat, Feb 23, 2019 at 08:12:40PM +1100, Chris Jones wrote:
> Thanks Bert, but I don’t understand how my backend is doing too much work?
> How does PowerDNS know what the zone is if my backend doesn’t figure it out?
Chris, please carefully read the blog post. It is in there.
"The PacketHandler
Thanks Bert, but I don’t understand how my backend is doing too much work?
How does PowerDNS know what the zone is if my backend doesn’t figure it out?
Regards,
Chris.
On Sat, 23 Feb 2019 at 7:23 pm, bert hubert
wrote:
> On Sat, Feb 23, 2019 at 03:49:28PM +1100, Chris Jones wrote:
> > Hi
On Sat, Feb 23, 2019 at 03:49:28PM +1100, Chris Jones wrote:
> Hi there,
>
> I am in the process of writing a custom backend with PowerDNS 4.1.5 and I
> have a question on the expected response for SOA records.
Hi Chris Jones 44,
It looks like your backend is doing too much work. In
Hi there,
I am in the process of writing a custom backend with PowerDNS 4.1.5 and I
have a question on the expected response for SOA records.
As an example, when I dig a random subdomain at google.com I get the
following result:
root@linux:~$ dig SOA asd.dsa.www.www.google.com @ns1.google.com
On Fri, Feb 10, 2017 at 06:07:38PM -0500, Jeff Weber wrote:
> I've been working on implementing a remote backend and I've got a few
> questions now that I've gotten far enough along that queries are
> answered with my initial attempts.
>
> I'm using the http connector and I've noticed that the
I've been working on implementing a remote backend and I've got a few
questions now that I've gotten far enough along that queries are
answered with my initial attempts.
I'm using the http connector and I've noticed that the documentation
in a few places talks about a domain-id being passed. For
* on the Mon, Dec 05, 2016 at 02:25:08PM +0200, Aki Tuomi wrote:
>>> scopeMask = how many bits of requestor IP was used to produce this
>>> result. this should 0 unless you are using the client's (real) IP
>>> somehow to come up with the answer, and if you do, how many bits of the
>>> value was
On 05.12.2016 13:56, Mike Cardwell wrote:
> * on the Mon, Dec 05, 2016 at 01:34:07PM +0200, Aki Tuomi wrote:
>
>>> Just got started with PowerDNS. Developing an application using the
>>> Remote backend, but the docs at
>>> https://doc.powerdns.com/md/authoritative/backend-remote/ seem a
>>>
* on the Mon, Dec 05, 2016 at 01:34:07PM +0200, Aki Tuomi wrote:
>> Just got started with PowerDNS. Developing an application using the
>> Remote backend, but the docs at
>> https://doc.powerdns.com/md/authoritative/backend-remote/ seem a
>> little sparse. What do the following parameters contain
Hi,
Just got started with PowerDNS. Developing an application using the
Remote backend, but the docs at
https://doc.powerdns.com/md/authoritative/backend-remote/ seem a
little sparse. What do the following parameters contain and when
should they be used?
zone_id
domain_id
auth
scopeMask
I'm
Ah perfect, there goes my Sunday :)
Thank You Aki
AJ
On 1 February 2015 at 08:14, Aki Tuomi cmo...@youzen.ext.b2.fi wrote:
On Sun, Feb 01, 2015 at 02:41:07AM +, AJ McKee wrote:
Being the weekend, I decided to write a HTTP backend for pdns as a fun
thing to do.
One thing springs to
Being the weekend, I decided to write a HTTP backend for pdns as a fun
thing to do.
One thing springs to mind however are the packet and query cache. In
particular, how they cache.
Do they use the remote clients ip as part of the caching key, thus only
serving from the cache if the client is
29 matches
Mail list logo
