IPv6 DNS set to client rather than dnsmasq

IPv6 DNS set to client rather than dnsmasq

IPv6 DNS set to client rather than dnsmasq
IPv6 DNS set to client rather than dnsmasq
2024-09-04 20:06:07
Model: Archer BE800  
Hardware Version: V1
Firmware Version: 1.1.6

Hi I'm facing an issue with how BE800 is managing DNS on the lan for ipv6.

For ipv4 you get either your ISP DNS or manually entered ones and then they are added to the dnsmaq configuration and the router ip is send via DHCP to ipv4 clients. dnsmasq serve as DNS cache for the lan but also resolves local machine IP (including tplinkwifi.net by the way)

For ipv6 if you choose SLAAC/statless DHCP for the lan the ISP DNS or manually entered are sent to the clients, by-passing the cache and the local network resolution ...

 

The stateless DHCP should sent the router local ipv6 address instead, and ipv6 DNS should be added as remote DNS to dnsmasq configuration (since dnsmasq is already listening to ipv6 anyway).

 

Benoit

  0      
  0      
#1
Options
1 Reply
Re:IPv6 DNS set to client rather than dnsmasq
2024-09-05 07:22:47

  @benoitm974 

Hi,

Thanks for your feedback.

 

I have recorded your suggestions and will forward to development team for evaluation.

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer BE550 New Software Enhances System Stability and Optimizes MLO Network Stability. TL-WA3001 Supports EasyMesh, Speed Limit, Guest Network in AP Mode and/or Multi-SSID Mode. If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
  0  
  0  
#2
Options