Unbound - Authoritative Recursive Caching DNS Server

[Delusion]

After removing this script (uninstalling) I have no access to internet without defining specific DNS servers. Can't use my ISP DNS servers and must turn on DNS Filtering to route all devices via DNS servers I specified! What happened?

 

[dave14305]

After removing this script (uninstalling) I have no access to internet without defining specific DNS servers. Can't use my ISP DNS servers and must turn on DNS Filtering to route all devices via DNS servers I specified! What happened?

Clean out /jffs/scripts/dnsmasq.postconf and/or /jffs/configs/dnsmasq.conf.add

 

[rgnldo]

only reboot

 

[Delusion]

Clean out /jffs/scripts/dnsmasq.postconf and/or /jffs/configs/dnsmasq.conf.add

They are clean . :\ very strange... I did reboot after uninstall and it didn't work

 

[rgnldo]

They are clean . :\ very strange

IMPORTANT: It is recommended to REBOOT in order to complete the removal of unbound
             You will be asked to confirm BEFORE proceeding with the REBOOT

             rs = Restart (or Start) unbound                                         s  = Display unbound statistics (s=Summary Totals; sa=All)

             e  = Exit Script

             Option ==> 2

             IMPORTANT: It is recommended to REBOOT in order to complete the removal of unbound
                          You will be asked to confirm BEFORE proceeding with the REBOOT

             y = Are you sure you want to uninstall unbound?
             n = Cancel
             e = Exit Script

             Option ==> y

             Uninstalling unbound
             Removing firewall rules
             KILLing unbound PID=1965
             Removing Ad and Tracker Update cron job
             Existing unbound package found. Removing unbound
             Removing package unbound-control-setup from root...
             Removing package unbound-control from root...
             Removing package unbound-anchor from root...
             Removing package unbound-daemon from root...
             unbound Entware packages 'unbound-control-setup unbound-control unbound-anchor unbound-daemon' successfully installed
             /opt/var/lib/unbound/adblock folder and all files removed
             /opt/var/lib/unbound folder and all files removed
             No files found to remove in /opt/etc/unbound
             /opt/etc/unbound folder and all files removed
             Removing unbound installer directives from 'dnsmasq.postconf'

                     Uninstall of unbound completed.

             The router will now REBOOT to finalize the removal of unbound
             After the REBOOT, review the DNS settings on the WAN GUI and adjust if necessary

             Press Y to REBOOT  or press ENTER to ABORT

 

[Delusion]

here is the output of "cat /etc/dnsmasq.conf

https://pastebin.com/raw/KaUhe6UH

 

[rgnldo]

Clean out /jffs/scripts/dnsmasq.postconf and/or /jffs/configs/dnsmasq.conf.add

If you do not choose to reboot, launch

service restart_dnsmasq

ls /jffs/configs/
.

cat /jffs/scripts/dnsmasq.postconf
#!/bin/sh

 

[rgnldo]

They are clean . :\ very strange... I did reboot after uninstall and it didn't work

Script is working correctly. Rebooting is preferable if you have opted for more features.

 

[dave14305]

here is the output of "cat /etc/dnsmasq.conf

https://pastebin.com/raw/KaUhe6UH

cat /tmp/resolv.dnsmasq

 

[dave14305]

here is the output of "cat /etc/dnsmasq.conf

https://pastebin.com/raw/KaUhe6UH

Also check /jffs/scripts/firewall-start for the dns redirection.

 

[Martineau]

Script is working correctly. Rebooting is preferable if you have opted for more features.

Erm...

….actually, just in case the user does not reboot immediately after uninstalling unbound, the script does (silently) restart dnsmasq, however, it performs it after removing any unbound entries from 'dnsmasq.conf.add' but before removing the unbound entries from 'dnsmasq.postconf'

However, as you state, a REBOOT would fully honour the dnsmasq re-configuration.

Pushed v1.14 to correct this, and verbosely indicate that dnsmasq has been restarted.

Option ==> 2

IMPORTANT: It is recommended to REBOOT in order to complete the removal of unbound
             You will be asked to confirm BEFORE proceeding with the REBOOT
y = Are you sure you want to uninstall unbound?
n = Cancel
e = Exit Script

Option ==> y

Uninstalling unbound
Removing firewall rules
KILLing unbound PID=5735
Removing Ad and Tracker Update cron job
Existing unbound package found. Removing unbound
Removing package unbound-control-setup from root...
Removing package unbound-control from root...
Removing package unbound-anchor from root...
Removing package unbound-daemon from root...
unbound Entware packages 'unbound-control-setup unbound-control unbound-anchor unbound-daemon' successfully installed
/opt/var/lib/unbound/adblock folder and all files removed
/opt/var/lib/unbound folder and all files removed
No files found to remove in /opt/etc/unbound
/opt/etc/unbound folder and all files removed
Removing unbound installer directives from 'dnsmasq.postconf'
Restarting dnsmasq.....

    Uninstall of unbound completed.

The router will now REBOOT to finalize the removal of unbound
After the REBOOT, review the DNS settings on the WAN GUI and adjust if necessary

Press Y to REBOOT  or press ENTER to ABORT

 

[Martineau]

Also check /jffs/scripts/firewall-start for the dns redirection.

Didn't think the unbound installer script still modified 'firewall-start'

 

[dave14305]

Erm...

….actually, just in case the user does not reboot immediately after uninstalling unbound, the script does (silently) restart dnsmasq, however, it performs it after removing any unbound entries from 'dnsmasq.conf.add' but before removing the unbound entries from 'dnsmasq.postconf'

However, as you state, a REBOOT would fully honour the dnsmasq re-configuration.

Pushed v1.14 to correct this, and verbosely indicate that dnsmasq has been restarted.

Option ==> 2

IMPORTANT: It is recommended to REBOOT in order to complete the removal of unbound
             You will be asked to confirm BEFORE proceeding with the REBOOT
y = Are you sure you want to uninstall unbound?
n = Cancel
e = Exit Script

Option ==> y

Uninstalling unbound
Removing firewall rules
KILLing unbound PID=5735
Removing Ad and Tracker Update cron job
Existing unbound package found. Removing unbound
Removing package unbound-control-setup from root...
Removing package unbound-control from root...
Removing package unbound-anchor from root...
Removing package unbound-daemon from root...
unbound Entware packages 'unbound-control-setup unbound-control unbound-anchor unbound-daemon' successfully installed
/opt/var/lib/unbound/adblock folder and all files removed
/opt/var/lib/unbound folder and all files removed
No files found to remove in /opt/etc/unbound
/opt/etc/unbound folder and all files removed
Removing unbound installer directives from 'dnsmasq.postconf'
Restarting dnsmasq.....

    Uninstall of unbound completed.

The router will now REBOOT to finalize the removal of unbound
After the REBOOT, review the DNS settings on the WAN GUI and adjust if necessary

Press Y to REBOOT  or press ENTER to ABORT

A firewall restart would be necessary if ever enabling the redirect.

 

[dave14305]

Didn't think the unbound installer script still modified 'firewall-start'

Beware of early adopters.

 

[rgnldo]

A firewall restart would be necessary if ever enabling the redirect.

If you check, there are no changes to the firewall.

 

[rgnldo]

Pushed v1.14 to correct this, and verbosely indicate that dnsmasq has been restarted.

I had understood the script. Thank you for this collaboration.

 

[Martineau]

A firewall restart would be necessary if ever enabling the redirect.

Well the script still contains the (unused) 'Redirect_outbound_DNS_requests()' function which only deletes the two redirect rules it implemented, so whilst it may be prudent, but simply deleting the redirect rules seemed to suffice without a disruptive firewall restart?

 

[Stevens243]

I have a quick question that has been talked about but that I don't see a specific answer to: If I do not have stubby installed (as a script) but am using DoT in Merlin, should I integrate stubby in the setup? Also, while I'm asking, since I'm using diversion, should I use/install ad/tracker blocking or leave that to diversion?

Thanks.

 

[dave14305]

If you check, there are no changes to the firewall.

Older versions (Dec 20) automatically applied the changes without the complete unbound_installer comment. So the current script would not remove those lines.

 

[rgnldo]

Well the script still contains the (unused) 'Redirect_outbound_DNS_requests()' function which only deletes the two redirect rules it implemented, so whilst it may be prudent, but simply deleting the redirect rules seemed to suffice without a disruptive firewall restart?

Right. It turns out that applying IPTABLES rules runs the risk of compatibility with future releases of FW Merlin. Prudently, DNSFILTER is sufficient.