🏳️⚧️
Nope, just substituted out my domain for the post.
Ran dig +trace and my domain and it returned a 100.x.x.x#53 public domain address.
I too am going from Apple Music to self-hosted.
Personally I run Navidrome on my server. It has a web player for computers and play:Sub has been my mobile player of choice. Also supports offline downloading to your device. Super lightweight as well.
If the tags for the music files are incorrect, I use Kid3 to correct them.
If you keep using your Apple TV and switch to Jellyfin as a backend, the Infuse application has been amazing. It’s free with a premium version (that does offer a lifetime license).
Guess what? An ATV natively supports keyboards and game controllers over Bluetooth. So for someone who doesn’t have an iPhone (the remote app is baked into iOS unfortunately) and reeeeeally hates tv remote typing and voice inputs, a mini keyboard is a viable option.
You really didn’t do any research before making so many hot takes.
So following dig ns domain in terminal vs web app on my phone (shared by another commenter and I had checked lemmy on mobile): my computer was resolving with a couple of different odd results including my public ipv6 address. On mobile it resolved properly.
Checked my DNS and my computer’s dns had my public ip in the listing. So now after removing that, the domain resolves to the wildcard (which dumps at my opnsense router and throws the dns rebind error). So I’m assuming that should be it?
Now I should only have to resolve configuring nginx properly.
Thank you for suggesting the dig command!