1
Virtual private networks / Re: Some clarification on DNS via VPN
« on: May 11, 2024, 11:56:32 am »Sounds like maybe your smart TV is somehow programmed to use a hardcoded DNS, and if that isn't reachable it just defaults to a network error? I don't know the first thing about smart TVs cause I never own(ed) one, but hardcoded DNS seems to be a common thing among IoT. You could try setting an override in your local DNS for whichever IP the TV wants to connect to for DNS. Say it's looking to connect to 1.1.1.1, so you set an override for 1.1.1.1 to go to e.g. 9.9.9.9. I'm not sure this would work, but might be worth a shot.And how do I set that override?
This is to be expected, I believe, since in standard networks, the gateway often acts as a DNS server, too. Can other hosts in the 192.168.10.0/24 net resolve DNS queries (or rather, have them resolved by the DNS)? If not, then your DNS is likely the culprit.Actually the smart TV is the only device attached to that port.
It's a shame if there is no way to make the smart TV properly working through a VPN...
Could you confirm the port forward is correct (see attachments in my previous post) ?