Posted: Sat Sep 12, 2020 1:42 Post subject: Slow DNS?
I have 2 devices on my network that are suddenly unhappy using my router (192.168.1.1) as a DNS. These devices are a Samsung Smart TV and an Apple TV. I found that if I override the DHCP provided DNS address (192.168.1.1) on these devices to use a public DNS server directly (like 184.108.40.206) they magically start working. The thing is my router is already pointing to these public DNS servers anyway and should just be forwarding on the DNS queries so I am not really sure why this would make a difference for these 2 devices. Most other devices on my network do not seem to have a problem using my router as a DNS.
The only thing I can think of is maybe the router DNS is introducing some latency that these 2 devices in particular are sensitive to? Doing an nslookup on my laptop, it does sometimes take a good 5 seconds to get a response. I guess I am not really sure where to start looking to figure out what is going on here...
the database isn't up to date and might behave like it was stated on the website :
This database may not have up-to-date information and may even recommend a build which might cause issues. As such, you should check the device specific forum (Broadcom, Atheros, MediaTek, etc.) first before flashing any build recommended in this database. There you will find build specific topics that discuss any issues with a particular build/release. For more up-to-date firmware files, please visit the firmware faq.
also add static IP to your SSNG TV and replace its ip in those lines...
you can use other DNS than GGL, but try with GGL if so...im using 220.127.116.11 with no problems as well i have "Forced DNS" turned on too... _________________ Atheros
TP-Link WR740Nv1 -----DD-WRT 44538 BS AP,NAT
TP-Link WR740Nv4 -----DD-WRT 44251 BS WAP/Switch
TP-Link WR1043NDv2 ---DD-WRT 45229 BS AP,NAT,AP Isolation,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---DD-WRT 45493 BS AP,NAT,AD Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---Gargoyle OS 1.12.0 AP,NAT,QoS,Quotas
Netgear R7800 -----DD-WRT 45493 BS AP,NAT,AD-Block,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT
Netgear R7000 -----DD-WRT 45493 BS AP,Wi-Fi OFF,NAT,AD-Block,Firewall,Local DNS,Forced DNS,DoT,VPN
Stubby for DNS over TLS I DNSCrypt v2 by mac913
But why is my Samsung TV special that I have to do firewall hacks to get it to work? What is the difference between the client sending DNS queries to 192.168.1.1 and the router forwarding on to 18.104.22.168 compared to the client sending the DNS queries directly to 22.214.171.124?
I also noticed last night that my Raspberry Pi has the same problem.
to answer your question, i shall ask... did you read the link i posted above....??
Sorry if I missed it, but what was I supposed to get from that link? I see that the issue and "fix" is similar to mine, but I don't see an explanation as to why this is a problem.
If you are implying that my Samsung TV is built on top of Android and so prefers using 126.96.36.199, I can actually use any other DNS (188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, etc...), the problem is only when using 192.168.1.1 as DNS. And obviously, my Apple TV is not built on top of Android to begin with.