You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I had reasons recently to run zoneserver-over-ipv6 recently, which if one has tried, you will realize maradns does not really ship support for. Thankfully, if you are running zoneserver on an ipv4 interface, this can be accommodated via systemd's socket-proxy service.
An example to configure such follows:
mararc:
# mararc content
tcp_convert_acl = "0.0.0.0/0"
tcp_convert_server = "IP-OF-UDP-MARADNSSERVER"
ipv4_bind_addresses = "IPV4-ADDRESS-OF-MARASERVER" # pure-ipv6 is much more painful, having an ipv4 range mara can sit on for this even if that v4 range is RFC1918 is easier to provision
/etc/systemd/system/zoneserver-6to4.socket
# this provides for a listening socket for systemd to forward to a socket-notification-listening service
# zoneserver 6to4.socket
[Unit]
Description=Zoneserver-6to4 socket
[Socket]
ListenStream=[IPV6::ZONE::SERVER::IP::HERE]:53
Accept=no
[Install]
WantedBy=sockets.target
After setting these up, and enabling&starting the zoneserver-6to4.socket, you should be able to dig NAME @IPV6::ZONE::SERVER::IP::HERE +tcp and expect valid results!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So, I had reasons recently to run zoneserver-over-ipv6 recently, which if one has tried, you will realize maradns does not really ship support for. Thankfully, if you are running zoneserver on an ipv4 interface, this can be accommodated via systemd's socket-proxy service.
An example to configure such follows:
mararc:
/etc/systemd/system/zoneserver-6to4.socket
/etc/systemd/zoneserver-6to4.service:
After setting these up, and enabling&starting the zoneserver-6to4.socket, you should be able to
dig NAME @IPV6::ZONE::SERVER::IP::HERE +tcp
and expect valid results!Beta Was this translation helpful? Give feedback.
All reactions