Flint 2 MT6000 | Tailscale Custom DNS + MagicDNS not working

[Sub01]

I've followed this guide here to get the DNS working on my MT6000 for client devices but to no avail:

Tailscale - Using AdGuard DNS is not working

Testing routers: MT6000 and MT3000, Firmware: v4.7.0 and v4.6.9 It seems it is available to fulfill your request. Long story short, you just need to add a port forwarding rule to redirect DNS queries arriving on the tailscale0 interface's port 53 to localhost's port 3053 where AdGuard Home is listening Here are the specific steps for reference: 1. Enable Tailscale in the GL interface, and ensure that the router is successfully bound to your Tailscale account. 2. Go to the Tailscale Admin Co…

Tailscale MagicDNS + a Pihole DNS instance accessed via Tailscale isn't working. However, when calling any site thats registered under Pihole DNS + MagicDNS from the Flint 2 via ssh, it works. Only client devices connected to the Flint 2 aren't working!

The Pihole DNS has already been added to the DNS Server list:

Logs:

Mon Feb 17 03:22:18 2025 kern.warn kernel: [ 2491.159991] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:18 2025 kern.warn kernel: [ 2491.556452] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:18 2025 kern.err kernel: [ 2491.565765] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:20 2025 kern.warn kernel: [ 2493.175962] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:20 2025 kern.warn kernel: [ 2493.652442] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:20 2025 kern.err kernel: [ 2493.661760] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:22 2025 kern.warn kernel: [ 2495.191956] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:22 2025 kern.warn kernel: [ 2495.748530] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:22 2025 kern.err kernel: [ 2495.757845] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:24 2025 kern.warn kernel: [ 2497.207960] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:25 2025 kern.warn kernel: [ 2497.844452] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:27 2025 kern.warn kernel: [ 2499.863945] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:27 2025 kern.warn kernel: [ 2499.936399] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:27 2025 kern.err kernel: [ 2499.945710] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:29 2025 kern.warn kernel: [ 2501.879939] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:29 2025 kern.warn kernel: [ 2502.032407] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:29 2025 kern.err kernel: [ 2502.041717] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:31 2025 kern.warn kernel: [ 2503.895933] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:31 2025 kern.warn kernel: [ 2504.128388] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:31 2025 kern.err kernel: [ 2504.137702] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:33 2025 kern.warn kernel: [ 2505.911931] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:33 2025 kern.warn kernel: [ 2506.224408] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:33 2025 kern.err kernel: [ 2506.233721] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:35 2025 kern.warn kernel: [ 2507.927953] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction
Mon Feb 17 03:22:35 2025 kern.warn kernel: [ 2508.320420] 7986@C09L2,cntl_connect_request() 395: type=2,len=0,caller:ApCliIfUp+0x1e0/0x3d0 [mt_wifi]
Mon Feb 17 03:22:35 2025 kern.err kernel: [ 2508.329731] 7986@C09L1,cntl_connect_request() 412: Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
Mon Feb 17 03:22:37 2025 kern.warn kernel: [ 2509.943946] 7986@C09L2,sync_fsm_join_timeout_action() 1091: ProbeTimeoutAtJoinAction

[bruce]

These logs are not related to DNS, but Wi-Fi drivers and can be ignored.

Does the DNS part of client network settings, manually set a custom DNS and it does not point to the router?