[HOWTO] DNS tunneling with iodined on TurrisOS HBK [5.2.3]

[AreYouLoco]

@vcunat

kresd doesn’t need to listen on WAN addresses. Your /etc/config/resolver probably retained lines like

        list interface '0.0.0.0'
        list interface '::0'

If you remove those, it will only listen on localhost and LAN. After that I don’t think there should be problem with iodined simply listening directly on port 53 of your WAN address(es).

I commented out the lines and did /etc/init.d/resolver restart now kresd listens only on localhost and my lan adresses. So I started iodined with:
root@router:~# LC_ALL=C iodined -f -DDDD -u nobody -d dns0 -m 1500 -l $MY_PUBLIC_ROUTER_IP -p 53 -P testpassword 10.222.111.254/28 t.mydomain.tld

And made sure it listens on public IP port 53
But the tool provided to check the server still complains. Also android iodine client cannot connect.

EDIT:

@vcunat

with iodined simply listening directly on port 53 of your WAN address(es).

From the firewall point of view it shouldn’t matter if a port is forwarded or accessed directly right?