# \[BUG\] Encrypted DNS (DoH) not working on MT6000 Flint 2 - Firmware 4.8.4 **URL:** \ **Category:** VPN, DNS, Leaks\ **Created:** [March 27, 2026, 11:30am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827 "2026-03-27T11:30:13Z")\ **Posts on this page:** 10\ **Page:** 2
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [March 30, 2026, 3:44am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/21 "2026-03-30T03:44:12Z")
Hi Thank you for the report. We’ve reproduced the issue and identified the root cause, and will have the R&D team work on a fix. For now, please [SSH into the router](https://docs.gl-inet.com/router/en/4/tutorials/ssh_log_in_to_the_router/) and run the following commands as a temporary workaround: ```auto cat << 'EOF' > /etc/init.d/dnscrypt-proxy #!/bin/sh /etc/rc.common USE_PROCD=1 # starts before dnsmasq starts START=18 # stops before networking stops STOP=89 PROG=/usr/sbin/dnscrypt-proxy CONFIGFILE=/etc/dnscrypt-proxy2/dnscrypt-proxy.toml start_service() { local mode=$(uci -q get gl-dns.@dns[0].mode) local proto=$(uci -q get gl-dns.@dns[0].proto) ["$mode" = "secure"] || exit 0 ["$proto" = "DoT"] && exit 0 /etc/init.d/dnscrypt-proxy-vpn start procd_open_instance procd_set_param group nonevpn procd_set_param command "$PROG" -config "$CONFIGFILE" procd_set_param file "$CONFIGFILE" procd_set_param stdout 1 procd_set_param stderr 1 procd_set_param respawn ${respawn_threshold:-3600} ${respawn_timeout:-5} ${respawn_retry:-5} procd_close_instance } stop_service() { /etc/init.d/dnscrypt-proxy-vpn stop } EOF /etc/init.d/dnscrypt-proxy start ``` ---
**Author:** ![MsX](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/m/4af34b/32.png) [@MsX](https://forum.gl-inet.com/u/MsX)\ **Post date:** [March 30, 2026, 8:48am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/23 "2026-03-30T08:48:03Z")
Thanks, it worked fine. What is the timeline for the bugfix release? Thanks it worked correctly, what is the timeframe for the bugfix release? Obviously this script no longer works once the router is restarted, you have to repeat it. ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [March 30, 2026, 10:14am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/24 "2026-03-30T10:14:25Z")
We’ve asked the R&D team to prioritize this issue. Since it isn’t particularly complex, a fix should be released soon—likely within a few days. We’ve tested the workaround locally, and it remains effective after a reboot without needing to run the commands again, unless the device is reset or the firmware is upgraded/downgraded. After applying the configuration, do you encounter any issues after rebooting the router? If so, please run the following commands and share the results so we can investigate further: ```auto cat /etc/init.d/dnscrypt-proxy ps | grep dnscrypt netstat -tlnup | grep 5453 logread | grep dnscrypt ``` ---
**Author:** ![MsX](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/m/4af34b/32.png) [@MsX](https://forum.gl-inet.com/u/MsX)\ **Post date:** [March 30, 2026, 11:50am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/25 "2026-03-30T11:50:25Z")
I confirm that it works after rebooting without having to repeat the first script reported I confirm that it works after a reboot without the need to repeat the first script reported, thanks and good work, we are waiting for a fix for the WiFi too ---
**Author:** ![Beppe01](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/59ef9b/32.png) [@Beppe01](https://forum.gl-inet.com/u/Beppe01)\ **Post date:** [March 31, 2026, 5:54pm UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/26 "2026-03-31T17:54:01Z")
Good morning everyone, Unfortunately, I also need to express my disappointment. It is unacceptable that, starting from version 4.3 onward, all the updates have presented issues. We have great confidence in your products, and I kindly ask you to put more effort into the development process. Thank you. ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [April 1, 2026, 8:13am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/27 "2026-04-01T08:13:28Z")
The adjustment in Wi-Fi power is a regulatory compliance requirement. Please refer to our statement below: > [@Flint 2: worse Wi-Fi coverage on 4.8.4 compared to 4.8.3](https://forum.gl-inet.com/t/flint-2-worse-wi-fi-coverage-on-4-8-4-compared-to-4-8-3/67859/7): > > Hi To ensure regulatory compliance, we have adjusted the Wi-Fi transmit power parameters for the Flint 2 (GL-MT6000) in firmware version 4.8.4. Some users may notice changes in signal coverage following this update, and we sincerely apologize for any inconvenience this may cause. To optimize your wireless experience, we recommend manually setting your 5 GHz channel to Band 3 / UNII-2C (CH100 - CH144). Under current regulatory frameworks, these specific channels are permitted to operate at a hi… ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [April 1, 2026, 8:15am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/28 "2026-04-01T08:15:11Z")
We sincerely apologize again for the inconvenience caused. We have asked the relevant team to conduct an internal review of this incident and improve the processes to prevent similar issues from occurring in the future. ---
**Author:** ![PoweredByVeg](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/poweredbyveg/32/25044_2.png) [@PoweredByVeg](https://forum.gl-inet.com/u/PoweredByVeg)\ **Post date:** [April 1, 2026, 8:42am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/29 "2026-04-01T08:42:10Z")
Why did you not put this on the release notes? You just stated it was bug fixes as far as I can remember. Doesn’t sit right with me that you kept it quiet until someone highlighted the reduced WiFi power. ---
**Author:** ![Aashish.007](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/ea5d25/32.png) [@Aashish.007](https://forum.gl-inet.com/u/Aashish.007)\ **Post date:** [April 1, 2026, 10:24am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/30 "2026-04-01T10:24:45Z")
Yes, each release should have detailed release notes. We together could report this and find the error, otherwise some errors may go unnoticed between versions. ---
**Author:** ![system](https://forum-static.gl-inet.com/original/3X/7/7/77e28f6cb342ac4bd641bd9a6254595d61b2812a.png) [@system](https://forum.gl-inet.com/u/system)\ **Post date:** [July 22, 2026, 10:31am UTC](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827/32 "2026-07-22T10:31:54Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed. [Previous page](https://forum.gl-inet.com/t/bug-encrypted-dns-doh-not-working-on-mt6000-flint-2-firmware-4-8-4/67827.md?page=1)