jellyfin/jellyfin.org
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.org.git synced 2026-09-03 04:10:04 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1868 from BotBlake/IPv6-DNS-notes

Browse Source 
rephrase IPv6 local DNS note
This commit is contained in:
BotBlake
2026-06-02 09:01:18 +02:00
committed by GitHub
parent 943d13b0aa 7a1a3b04d2
commit 2d1f4e44a8
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/general/post-install/networking/index.md
+5 -5
View File
@@ -48,12 +48,12 @@ However its also possible to create a local DNS entry that will point to your Je
<details>
<summary>Learn more about limitations with local DNS</summary>
Devices like Google Chromecast or Google Streamer use hardcoded DNS Servers - therefore they will not make use of your local DNS entries.
There are multiple workarounds for this issue.
Devices like Google Chromecast or Google TV Streamer may ignore the DNS server provided by your local network.
As a result, they may not resolve custom local DNS entries correctly.
The easiest involves the usage of IPv6 Entries in the public DNS.
Since IPv6 addresses do not differentiate between local and public, the address will be able to be resolved locally.
This, however, requires the use of a public DNS server - The Jellyfin Server does not have to be accessible from the outside though!
One option to work around this is to publish an IPv6 DNS record through a public DNS provider.
If your Jellyfin server has a globally routable IPv6 address, devices can resolve it without relying on your local DNS server.
The server itself does not need to be publicly accessible. Inbound access can still be restricted through your firewall.
</details>