Skip to content

Conversation

@echo-devnull
Copy link

Also see: https://pracucci.com/kubernetes-dns-resolution-ndots-options-and-why-it-may-affect-application-performances.html

And: https://forums.plex.tv/t/claiming-a-plex-media-server-docker-kubernetes/914912/24

Simply put: Kubernetes is trying to internally resolve "plex.tv" because it thinks this is a internal service name (only 1 dot).

We can either make plex media server try and resolve the actual FQDN for plex.tv. (ending with a dot)

Or add this dnsconfig to the statefulset.

Also see: https://pracucci.com/kubernetes-dns-resolution-ndots-options-and-why-it-may-affect-application-performances.html

And: https://forums.plex.tv/t/claiming-a-plex-media-server-docker-kubernetes/914912/24

Simply put: Kubernetes is trying to internally resolve "plex.tv" because it thinks this is a internal service name (only 1 dot).

We can either make plex media server try and resolve the actual FQDN for `plex.tv.` (ending with a dot)

Or add this dnsconfig to the statefulset.
@echo-devnull echo-devnull requested a review from a team April 28, 2025 21:21
@cilindrox cilindrox self-assigned this May 2, 2025
@cilindrox
Copy link
Member

Thanks @echo-devnull - I've added a configurable dnsConfig stanza for v0.10 (#141)
Users should be able to configure ndots from there.

@cilindrox
Copy link
Member

v0.10.0 is out now with a configurable dnsConfig stanza. Thanks @echo-devnull

@cilindrox cilindrox closed this May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants