Re: [Pdns-users] [EXT] Re: remote backend

2023-11-30 Thread Alexis Fidalgo via Pdns-users
Yes, i wrote it fast in the playground as an example, didn't verified if it was completely ok (sorry about that), it was only to graph the idea. I’ll try what you suggested right now. Thanks! > On 30 Nov 2023, at 07:00, Brian Candler wrote: > > That code is incomplete and not runnable. What

Re: [Pdns-users] [EXT] Re: remote backend

2023-11-30 Thread Brian Candler via Pdns-users
That code is incomplete and not runnable. What is "[0:netip]" for example? More importantly, what is "c" when you do c.Write(data) ? However, there is also an unstated question here, which is "how are the requests and responses delimited when PowerDNS using the unixsock remote backend?"  You'r

Re: [Pdns-users] [EXT] Re: remote backend

2023-11-30 Thread Alexis Fidalgo via Pdns-users
Check this, i removed the code from my responder by now but it was something like this func main() { l, err := net.ListenUnix("unix", &UnixAddr{Name: "unix",Net :"/tmp/echo.sock",}) if err != nil { panic(err) } for { fd, err := l.Accept() if err != nil {

Re: [Pdns-users] [EXT] Re: remote backend

2023-11-30 Thread Remi Gacogne via Pdns-users
On 29/11/2023 01:07, Alexis Fidalgo wrote: Problem is (and i’ve testing with golang and python) after the answer the “initialize” message, the socket is closed, so, getAllDomains message is being sent using a closed socket and that’s why i don’t see it on the responder side and pdns does not re