Domain-specific private reverse DNS upstream servers are now validated to allow only*.in-addr.arpaand*.ip6.arpadomains pointing to locally-served networks#3381.Note:If you already have invalid entries in your configuration, consider removing them manually, since they essentially had no effect. Res...
Private rDNS resolution (dns.use_private_ptr_resolvers in YAML configuration) now requires a valid "Private reverse DNS servers", when enabled (#6820). NOTE: Disabling private rDNS resolution behaves effectively the same as if no private reverse DNS servers provided by user and by the OS. Fix...
我們發佈此修復程式的原因是,上次 AdGuard Home 更新後,一些使用者無法啟動 AdGuard Home。AdGuard Home 0.107.49 更新日期:2024年5月21日 在這次修補程式中,我們修復了一些錯誤,讓 AdGuard Home 運行更流暢。AdGuard Home 0.107.48 更新日期:2024年4月5日 定執行 DNS 查詢。 這是一個錯誤,我們已修復了它。
Private rDNS resolution (dns.use_private_ptr_resolvers in YAML configuration) now requires a valid "Private reverse DNS servers", when enabled (#6820). NOTE: Disabling private rDNS resolution behaves effectively the same as if no private reverse DNS servers provided by user and by the OS. Fix...
If not, set use_private_ptr_resolvers to false. jerheij commented May 22, 2024 • edited More info: I have 3 docker instances running of which 2 failed like described. These two show, under the Private reverse DNS servers heading: AdGuard Home could not determine suitable private ...
Users should configure explicitly a private reverse DNS server. Disable the feature by default. Related Issues Potential better solution here would be to read DNS servers from Supervisor, and if it isthe Home Assistant host itself, enable the feature and set the local DNS server using...
The "Use private reverse DNS resolvers" toggle button always enabled even I unchecked that from adguard web interface. 开发人员回复, Hi, your second point was just fixed with a new preference setting in v1.16 and I’ll take a look at the bug & design suggestion! - Joost ...
To rollback this change, remove the new field upstream_mode, set back dns.all_servers and dns.fastest_addr properties in dns section, and change the schema_version back to 27. Fixed “Invalid AddrPort” in the Private reverse DNS servers section on the Settings → DNS settings page. Panic...
@<dns_server> +tcp What should be the result of this test? I just get a NXDOMAIN response when I do the test with the LAN IP address of my Asus router, within an acceptable time. Yet ADH blocks when I set this IP address as upstream DNS and with the private reverse DNS servers. ...
Private rDNS resolution (dns.use_private_ptr_resolvers in YAML configuration) now requires a valid "Private reverse DNS servers", when enabled (#6820). NOTE: Disabling private rDNS resolution behaves effectively the same as if no private reverse DNS servers provided by user and by the OS....