complicated DNS interception stuff with your router.
It’s often not that hard. Many routers have a setting for local dns records.
If you do make a public DNS record, I recommend not putting “plex” or “jellyfin” or “TV” in the domain or subdomain. Make it something more generic.
I recently got a domain from Namecheap, $100 for ten years. If you want something that changes every year, you can get some .xyz domain for like $2 for the first year (and then it’ll go up to more the next years.)
It’s often not that hard. Many routers have a setting for local dns records.
Right, that’s easy, but IIRC google devices hard code their DNS servers for casting, so you need to intercept traffic bound for 8.8.8.8.
These folks suggest that just blocking the DNS servers allows you to use your own fallback. Haven’t personally tried that, but perhaps more straightforward.
I’d intercept port 53 traffic for UDP and TCP, that way it doesn’t matter what the IP is. I don’t know about consumer stuff, but a dst nat rule should work.
It’s often not that hard. Many routers have a setting for local dns records.
If you do make a public DNS record, I recommend not putting “plex” or “jellyfin” or “TV” in the domain or subdomain. Make it something more generic.
I recently got a domain from Namecheap, $100 for ten years. If you want something that changes every year, you can get some .xyz domain for like $2 for the first year (and then it’ll go up to more the next years.)
Right, that’s easy, but IIRC google devices hard code their DNS servers for casting, so you need to intercept traffic bound for
8.8.8.8.These folks suggest that just blocking the DNS servers allows you to use your own fallback. Haven’t personally tried that, but perhaps more straightforward.
I’d intercept port 53 traffic for UDP and TCP, that way it doesn’t matter what the IP is. I don’t know about consumer stuff, but a dst nat rule should work.
Good to know. I don’t have a setup yet, but I might soon.