This is a small addition to the previous guide I had created earlier.

The previous guide showed how you can add a iptables firewall that will work with your docker containers, while it may not seem complicated, and really it isn’t, it does take a little bit of reading and understanding for it to “click”, at least it did for me.

What this modification will do is modify your iptables rules to allow a dynamic IP to only be allowed access to your secure services. This may not be ideal for everyone, but for me it works great, since I can set it to my home IP address. This means I can only connect via SSH and the docker service via Portainer.

You may say, how do you connect if you are not at home? Well I just VPN to my home connection and then connect to my secure services.

Also if your looking for a way to securely connect to your docker service remotely, check out this awesome guide.

Step 1: Only a Minor Modification Needed

So there only needs to be a minor modification needed to start off.

For simplicity sake, I am going to assume you already have dynamic IP setup for your home, or where ever it is you want to setup access.

The script that we will use to detect our dynamic IP will use the host command. If you are using Debian, which is my flavour of server, you may need to install dnsutils. It can be installed with apt install dnsutils.

Find out what your current IP is as you will need it to modify the iptables config file /etc/iptables.conf that was created in the prior guide.

:FILTERS - [0:0]
:DOCKER-USER - [0:0]


-A INPUT -i lo -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT


-A FILTERS -m conntrack --ctstate NEW -p tcp -m multiport --dports 80 -j ACCEPT
-A FILTERS -m conntrack --ctstate NEW -p tcp -m multiport --dports 443 -j ACCEPT
-A FILTERS -m conntrack --ctstate NEW -p tcp -m multiport --src <YOUR.DYNAMIC.I.P> --dports 22 -m comment --comment "secure ssh" -j ACCEPT
-A FILTERS -j REJECT --reject-with icmp-port-unreachable


You will notice that the ssh iptables line has been modified.

Now before you restart the iptables service, make sure you have a way to connect to your server in case something goes wrong. Once you have a way to reconnect, go ahead and restart the service. If all goes well, nothing will happen.

Step 2: Grab your Dynamic IP and Update iptables

Create a new folder and executable file to store your new script:

root@server:[~]> mkdir /etc/dyndns
root@server:[~]> touch /etc/dyndns/
root@server:[~]> chmod +x /etc/dyndns/

Edit the new file /etc/dyndns/ with your favourite editor and paste/modify the following script. Be sure to change the HOSTNAME to your actual dynamic domain. Also if you have additional ports you want to secure, be sure to add additional lines, modifying them to your needs. The principle behind what we are doing is replacing the line located in our /etc/iptables.conf file based on the comment we have for the iptables rule anytime the dynamic IP does is not found in the iptables.

DYNIP=$(host $HOSTNAME | grep -iE "[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+" | cut -f4 -d' ' | head -n 1)

# Exit if invalid IP address is returned
case $DYNIP in )
        echo "invalid IP";
        exit 1 ;; )
        echo "invalid IP";
        exit 1 ;;

# Exit if IP address not in proper format
if ! [[ $DYNIP =~ (([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5]) ]]; then
    echo "invalid IP";
    exit 1

if ! iptables-nft -n -L FILTERS | grep -iE "$DYNIP" >/dev/null 2>&1 ; then
    sed -i "/secure ssh/c\-A FILTERS -m conntrack --ctstate NEW -p tcp -m multiport --src $DYNIP --dports 22 -m comment --comment \"secure ssh\" -j ACCEPT" $IPTABLESCONF
    systemctl restart iptables

I didn’t come up with the above script, I found it thanks to this nice little stackexchange.

UFW: Allow traffic only from a domain with dynamic IP address
I run a VPS which I would like to secure using UFW, allowing connections only to port 80.\nHowever, in order to be able to administer it remotely, I need to keep port 22 open and make it reachable f...

Once you have it configured, just add a new cron rule to run the script every 5 minutes, or however long you want the check to occur.