How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?

How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?

How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?
How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?
17 hours ago - last edited 15 hours ago
Model: Archer MR600  
Hardware Version: V3
Firmware Version: 1.2.0 0.9.1 v0001.0 Build 240716 Rel.54691n

I want to see per-client DNS analytics (like hostnames and MAC addresses) from my TP-Link MR600 v3 in my Control D dashboard. I’ve read this usually requires running a DNS daemon (like ctrld) on the router via SSH, but I’m not sure if, or how, this can be done on the MR600 v3.

Is there a way to enable SSH or terminal access, or install a third-party DNS helper/daemon on this router? Are there any native options or firmware upgrades that would allow sending client-level DNS metadata to an external DNS service?

Any step-by-step guidance or clarification would be really appreciated!

  0      
  0      
#1
Options
4 Reply
Re:How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?
4 hours ago

  @Vintage-MR600 

Hi, thank you very much for the feedback.

I'm afraid Archer MR600 doesn't support SSH access or installing a third-party DNS helper/daemon.

You can try to set the Control D DNS as the local DHCP server here to see whether it helps:

Best regards.

 

  0  
  0  
#2
Options
Re:How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?
4 hours ago

  @David-TP Hey David, appreciate your response. I am already using Control D on my router my only concern is that I am able to see my modem clients by executing this to my router?:
 

(Invoke-WebRequest -Uri 'https//..api.controld...com/dl/ps1' -UseBasicParsing).Content | Set-Content "$env:TEMPctrld_install.ps1"; Invoke-Expression "& '$env:TEMPctrld_install.ps1' 'RESOLVER_ID_HERE' 'forced'"


but as you mention that MR600 doesn't support SSH access or installing a third-party DNS helper/daemon. meaning that there is no other workaround? 

  0  
  0  
#3
Options
Re:How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?
3 hours ago

  @Vintage-MR600 

Hi, thanks for the update.

Archer MR600 can't execute these "Invoke-WebRequest" scripts.

I have seen users run the ctrld daemon on a separate, always-on device (e.g., Raspberry Pi, home server, or old laptop) and point it as the local DNS server on the Archer 4G routers for per-client DNS analytics.

Best regards.

  0  
  0  
#4
Options
Re:How to Enable Per-Device DNS Client Metadata or Daemon Access on TP-Link MR600 v3 for Control D?
3 hours ago

  @David-TP I see, what router would you recommend for me to be able use this kind of features and have more control and have advance features and so on such as forcing to use IPv6 only (Starlink) without a problem connecting to IPv4, I saw someone doing this on a different brand of router but lack of support unlike TP-link laugh

(This is only use for home network)

  0  
  0  
#5
Options