diff --git a/AdguardHome/README.md b/AdguardHome/README.md
index d13d1df..917955e 100644
--- a/AdguardHome/README.md
+++ b/AdguardHome/README.md
@@ -7,7 +7,6 @@
 ### Requirements
 1. You have setup the on boot script described [here](https://github.com/boostchicken/udm-utilities/tree/master/on-boot-script)
 2. AdguardHome persists through firmware updates as it will store the configuration in a folder (you need to create this). It needs 2 folders, a Work and Configuration folder. Please create the 2 folders in "/mnt/data/". In my example I created "AdguardHome-Confdir" and "AdguardHome-Workdir"
-3. The on-boot script needs to be setup after firmware update of UDM. When on-boot script is recreated, everything should work.
 
 ### Customization
 * Feel free to change [20-dns.conflist](../cni-plugins/20-dns.conflist) to change the IP address of the container.
diff --git a/dns-common/on_boot.d/10-dns.sh b/dns-common/on_boot.d/10-dns.sh
index 466e6f2..870f0a6 100644
--- a/dns-common/on_boot.d/10-dns.sh
+++ b/dns-common/on_boot.d/10-dns.sh
@@ -72,7 +72,7 @@ fi
 if podman container exists ${CONTAINER}; then
   podman start ${CONTAINER}
 else
-  logger Container $CONTAINER not found, make sure you set the proper name, if you have you can ignore this error
+  logger -s -t podman-dns -p ERROR Container $CONTAINER not found, make sure you set the proper name, if you have you can ignore this error
 fi
 
 # (optional) IPv4 force DNS (TCP/UDP 53) through DNS container
diff --git a/nextdns/README.md b/nextdns/README.md
index 4e13b4c..9b688d3 100644
--- a/nextdns/README.md
+++ b/nextdns/README.md
@@ -8,7 +8,6 @@
 
 ### Requirements
 1. You have already setup the on boot script described [here](https://github.com/boostchicken/udm-utilities/tree/master/on-boot-script)
-2. NextDNS persists through firmware updates. The on-boot script does not.  If you update your firmware, setup on-boot again and everything should work.
 
 ### Customization
 * Feel free to change [20-dns.conflist](../cni-plugins/20-dns.conflist) to change the IP address of the container. 
diff --git a/on-boot-script/packages/udm-boot_1.0.0-1_all.deb b/on-boot-script/packages/udm-boot_1.0.0-1_all.deb
index 7bcb9a3..3f4d942 100644
Binary files a/on-boot-script/packages/udm-boot_1.0.0-1_all.deb and b/on-boot-script/packages/udm-boot_1.0.0-1_all.deb differ
diff --git a/run-pihole/README.md b/run-pihole/README.md
index 1c47582..b5cf7f0 100644
--- a/run-pihole/README.md
+++ b/run-pihole/README.md
@@ -6,7 +6,6 @@
 
 ### Requirements
 1. You have successfully setup the on boot script described [here](https://github.com/boostchicken/udm-utilities/tree/master/on-boot-script)
-2. PiHole persists through firmware updates. The on-boot script does not.  If you update your firmware, setup on-boot again and everything should work.
 
 ### Customization
 * Feel free to change [20-dns.conflist](../cni-plugins/20-dns.conflist) to change the IP address of the container.