S5E3 "The Great Recession"

you are viewing a single comment's thread
view the rest of the comments
[–] 22 points 1 year ago (10 children)

Since casting JF to a Chromecast requires that it be resolvable by Google's DNS (or at least, it used to be that way I think), here's a fun trick to get it working: point your public DNS record to your private IP. It's apparently not always supported by your DNS provider, but it works great for me (namecheap).

No need to expose your JF instance over the Internet this way, and no need for complicated DNS interception stuff with your router.

You may need to have SSL certs for casting, not sure.

  • source
  • hideshow 10 child comments
  • [–] 4 points 1 year ago (3 children)

    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.)

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 1 year ago* (last edited 1 year ago) (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (2 children)

    I redirect all DNS to my router. Its how my ad block works. No matter what you try all DNS leads to the router.

  • source
  • parent
  • hideshow 2 child comments