![]() |
I moved, having DNS issues - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access) +---- Thread: I moved, having DNS issues (/t-i-moved-having-dns-issues) |
I moved, having DNS issues - fizzik - 2024-04-13 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: ![]() RE: I moved, having DNS issues - TheDreadPirate - 2024-04-13 What does Dashboard > Networking look like in Jellyfin? RE: I moved, having DNS issues - fizzik - 2024-04-13 This is resolved, sorry. I removed the port forward for 80 and 443 and re-added it, then nginx started working properly. |