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

是否可以对接已有的adguard? #16

Open
laurencedu opened this issue Jun 30, 2024 · 5 comments
Open

是否可以对接已有的adguard? #16

laurencedu opened this issue Jun 30, 2024 · 5 comments

Comments

@laurencedu
Copy link

我已经安装了docker版的adguardHome,因为已经配置了很多内容,不想更换。

@dnomd343
Copy link
Owner

dnomd343 commented Jul 2, 2024

可以的,需要你将原有的docker版AdguardHome配置目录,拷贝并替换到ClearDNS的容器目录下(按正常配置,运行后存在adguard目录),重启容器即可将原有配置更新进去。
由于开源许可证问题,AdguardHome在ClearDNS中以独立进程运行,因此配置文件和缓存与官方版并没有区别。不过需要注意,在ClearDNS中,它的登录密码会被接管,你需要在配置文件中指定AdguardHome的登录用户名和密码。

@liuhai0001
Copy link

ADG上游dns设定好后,重启会被恢复成默认的上游dns

@dnomd343
Copy link
Owner

dnomd343 commented Jul 3, 2024

ClearDNS的重点是分流呀,把国内外DNS请求分流到不同上游去,AdguardHome处于客户端和分流入口中间,更多的是用于广告拦截,它的上游就得是分流器入口(默认为127.0.0.1:5353)才对。如果AdguardHome的上游直接就是自定义DNS服务器,那就失去分流功能了呀。

@liuhai0001
Copy link

需要自定义部份网站到指定DNS解析,要在哪里修改,例如部份域名用公司DNS解析

@dnomd343
Copy link
Owner

dnomd343 commented Jul 4, 2024

这个在目前架构下没法直接做到(未实现规则分流)。不过你可以在domestic出口处再包一层,ClearDNS提供了自定义命令的能力,即你可以再拉起一个overture进程,把公司域名分流加进去,它在容器内部暴露一个接口作为domestic上游。

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

3 participants