That is what I figured. Thanks, Sam.
On 5/5/2016 6:30 AM, Sam Clippinger via spamdyke-users wrote:
Right now, spamdyke has no support for IPv6 at all, so it can't
understand that nameserver line. However, the only consequence
should be that error message -- it shouldn't have any trouble
Right now, spamdyke has no support for IPv6 at all, so it can't understand that
nameserver line. However, the only consequence should be that error message --
it shouldn't have any trouble skipping that line and using the IPv4 nameserver.
-- Sam Clippinger
On May 4, 2016, at 2:54 PM, BC
Using FreeBSD here.
In addition to my normal IPv4 connection, I have an IPv6 tunnel set up
via Hurricane Electric. Also use unbound as my local DNS cache
resolver for resolving both IPv4 & IPv6 addresses and it has been
doing both for over a year now.
spamdyke doesn't seem to like the
