Jump to content
Sign in to follow this  
cris

AdGuard Home

Recommended Posts


A new version is now available on the repository
Version: 0.98.0

Share this post


Link to post
Share on other sites

A new version is now available on the repository
Version: 0.98.1

Share this post


Link to post
Share on other sites

A new version is now available on the repository
Version: 0.98.1

Share this post


Link to post
Share on other sites

A new version is now available on the repository
Version: 0.98.1

Share this post


Link to post
Share on other sites

A new version is now available on the repository
Version: 0.98.1

Share this post


Link to post
Share on other sites

Hi,

I have a router that can't use other than port 53 for DNS server. However QNAP NAS is using already port 53. I resolved the problem by adding following lines to /etc/init.d/AdGuard.sh:

in start)

sed -i 's/53$/533/g' /etc/dnsmasq.conf
sed -i 's/127\.0\.1\.1$/127\.0\.0\.1/g' /etc/dnsmasq.conf
sed -i 's/127\.0\.1\.1$/127\.0\.0\.1/g' /etc/resolv.conf
killall -9 dnsmasq
/etc/init.d/network.sh restart

./AdGuardHome &

in stop)

killall -9 AdGuardHome
sed -i 's/533$/53/g' /etc/dnsmasq.conf
sed -i 's/127\.0\.0\.1$/127\.0\.1\.1/g' /etc/dnsmasq.conf
sed -i 's/127\.0\.0\.1$/127\.0\.1\.1/g' /etc/resolv.conf
killall -9 dnsmasq

/etc/init.d/network.sh restart

I am not sure if this is any good solution to the problem but I have not noticed any problems from it. Maybe the idea could be added to the init script in the future releases?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×