Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom DNS Resolver #342

Closed
shaneoreilly opened this issue Oct 14, 2023 · 2 comments
Closed

Custom DNS Resolver #342

shaneoreilly opened this issue Oct 14, 2023 · 2 comments

Comments

@shaneoreilly
Copy link

image: firefox
host: docker (on Synology)

Hi there,

Everything on n.eko is working as expected, but I am hoping to override the DNS resolver server for n.eko only, and ignore what my network DNS lookup provider is.

Essentially I use pi.hole, and want to have n.eko act as a sort of Web Proxy running locally, that can bypass PiHole's DNS resolver sinkhole.

Most solutions mention modifying about:config, but that looks blocked with n.eko./

Does anyone have any guidance on how I would acheive this?

@m1k1o
Copy link
Owner

m1k1o commented Oct 14, 2023

Docker allows you to set custom DNS:

https://docs.docker.com/network/#dns-services

Or you can create own browser policies that have specified custom DNS and mount them to the container.

https://neko.m1k1o.net/#/getting-started/?id=want-to-customize-and-install-own-add-ons-set-custom-bookmarks

@shaneoreilly
Copy link
Author

Perfect thank you @m1k1o !

I added an ENV flag for 'dns' in the Synology DSM 'Container Manager' settings but it didn't take effect, so I used Portainer's GUI to handle it.

Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants