2024-04-13, 02:53 AM
Hey guys, just want to preface this by saying this is NOT a Jellyfin issue. Just hoping that there are some DNS aficionados among you who are willing to help me out.
I recently moved apartments and as a result got a new public IP. No problem, I changed my DNS settings so my .com domain would still work (was working fine before). Gave it a couple of days, it seems to still be unresolvable. Jellyfin is reachable by using the public IP plus port, so I know that forwarding is not a problem. Only reason I'd think it would be is I also got a new router.
I also run a Minecraft server with this domain, and that is working with zero issues. That is what's killing me/doesn't make any sense. If DNS wasn't working, you'd think nothing worked.
What are some things that I could check? This is what happens when trying to run a traceroute, none of these are my public IP:
![[Image: rc1bwer.png]](https://i.imgur.com/rc1bwer.png)
I recently moved apartments and as a result got a new public IP. No problem, I changed my DNS settings so my .com domain would still work (was working fine before). Gave it a couple of days, it seems to still be unresolvable. Jellyfin is reachable by using the public IP plus port, so I know that forwarding is not a problem. Only reason I'd think it would be is I also got a new router.
I also run a Minecraft server with this domain, and that is working with zero issues. That is what's killing me/doesn't make any sense. If DNS wasn't working, you'd think nothing worked.
What are some things that I could check? This is what happens when trying to run a traceroute, none of these are my public IP:
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github){kind=icon}