Why dnsmasq don't reply to local 'lan' request ?
Hi running BE800 on my lan i don't get local name resolution for other machine connected via DHCP. If a machine request an IP to BE800 with a hostname 'machineA' then DNS should reply with locaip of the machine when request 'machiineA' or 'machineA.lan (suspect default domain of the router is .lan ?)
I'm testing requesting the router 192.168.1.1 UDP 53 vis command 'dig @192.168.1.1 machineA' and don't get any answer very strange...
I find the DNS setup of the BE800 very strange specialy between ipv4 and ipv6 ... Is there a plan to consolidate this ?
Benoit
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, I noticed that the senior engineering team has followed up your case via email already. Although different questions, it is the same router, right?
I strongly recommend that you discuss this with them directly, who are more professional and knowledgeable.
- Copy Link
- Report Inappropriate Content
@benoitm974 I think i found the answer in the beta firmware dnsproxy is wrtting a iptable rule to redirect every UDP and TCP traffic to port 53 of the tplinkwifi.net(192.168.x.x depending on which local lan we define in configuration) to the primary DNS of WAN4 !!!
I personnaly think this is seriously bad design and not very ransparent to final users :( Was this just to get the Tether app to work using tplinkwifi.net or the browser to redirect ? This seems really like a broken implementation...
And it does add latency to dns resolution on page which is un necessary...
- Copy Link
- Report Inappropriate Content
Hi, thanks for posting question here.
May I confirm whether it is the same situation if you installed the latest official firmware version instead of the Beta one?
Then we will feedback this to the engineering team for further research.
- Copy Link
- Report Inappropriate Content
yes it is the same on latest production veersion
- Copy Link
- Report Inappropriate Content
Hi, I noticed that the senior engineering team has followed up your case via email already. Although different questions, it is the same router, right?
I strongly recommend that you discuss this with them directly, who are more professional and knowledgeable.
- Copy Link
- Report Inappropriate Content
@Marvin_S Unfortunatelly I was told this was escalated but since no news ....
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 120
Replies: 5
Voters 0
No one has voted for it yet.