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, t
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, events=POLLIN}],
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, "{\"method\":
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 o
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 /opt/pdn
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.
W
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
betw
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
ex
