Replies: 1 comment 2 replies
-
You can try to bind another port for plain DNS instead 53 via AdGuardHome.yaml config file:
But you also need to change or add the port in client's settings🙂 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
Firstly, happy new year.
Secondly, a question about ports used by AdGuard and specifically port 53. I am currently running AdGuard Home from a Docker container on my Synology NAS. However, I recently wanted to install the DNS Server package on the NAS and it seems to crash and require a "repair" (which does not work) due to port 53 being occupied by AdGuard. I have contacted Synology Support who told me port 53 is absolutely necessary for DNS Server to run. Therefore, I'm now looking on the other side of the fence to check if AdGuard absolutely needs port 53 or if this can be modified in some way so that I can run both of them (AdGuard and DNS Server) simultaneously (or if I have make an "either / or" decision).
Sorry if this is an obvious (or blatantly stupid) question, I am kind of new to this and my research has been unfruitful so far.
Thank you.
MT
Beta Was this translation helpful? Give feedback.
All reactions