Closed tykling closed 8 months ago
That's a weird one! Nothing in the logs of the server (it would probably have to be in verbose mode to log anything interesting)?
Note to self: the getrandom
call means that dnsdist has been built without libsodium, which might be a clue.
The servers are busy so I had to block clients in the firewall to see what is going on but there was indeed an interesting clue in the logs, when it fails dnsdist -v
logs:
Control connection from [::1000:0:0:0]:43311 dropped because of ACL
Following runs work well and log a more expected message:
Got control connection from [::1]:64450
But how ::1
becomes ::1000:0:0:0
I have no idea...
oh, I might have an idea!
Short description
After restarting dnsdist the first time I run
dnsdist -c
it fails with an error instead of entering the dnsdist console.Environment
These are the default options for the port https://www.freshports.org/dns/dnsdist and my buildlogs can be seen here https://poudriere.tyknet.dk/data/latest-per-pkg/dnsdist/
Steps to reproduce
The config doesn't appear to matter much but here is my
dnsdist.conf
:The issue looks like this:
Expected behaviour
To enter the dnsdist console every time
Actual behaviour
Fatal error: EOF while reading message
Other information
This is truss(1) output from a failing case:
Looks like it fails writing right after getrandom(). dnsdist is serving requests just fine during this by the way.
This is a truss(1) of a working case: