You shouldn't have to keep opening the port assuming it is on the same system.

GameTracker won't be able to detect an IP change if it doesn't see the IP resolve to something different. DNS changes may take 24-48hrs to fully propagate the internet.

Typically you can connect to games by doing /connect IP:port, where IP can be replaced by a DNS since a DNS is just a "name" for an IP address. You'll probably have to research the command though.

burn wrote:
You shouldn't have to keep opening the port assuming it is on the same system.

GameTracker won't be able to detect an IP change if it doesn't see the IP resolve to something different. DNS changes may take 24-48hrs to fully propagate the internet.

Typically you can connect to games by doing /connect IP:port, where IP can be replaced by a DNS since a DNS is just a "name" for an IP address. You'll probably have to research the command though.
Thanks for your help. The command is connect. But when I connect it keeps trying establishing connection to the server.

You or whoever is running into issues would probably try pinging it to determine if it is being resolved to the correct IP. If it is not the current server's IP, they may just need to wait longer for the DNS change to propagate.

Since it is a non-default port, you'll need to specific it in the connect string as well.