https://www.gametracker.com/server_info/dc.ea117.com:14567/

We setup a new server at a new address, and began forwarding all game and query traffic still directed at the old address to the new address. i.e. Old server IP still responds to queries and players.

DNS dc.ea117.com record was updated with new IP address and has propagated, and only had 30 minute TTL. I expect GameTracker _has_ resolved this DNS name, else GameTracker wouldn't have thought anything was wrong at all. i.e. Queries to the old address, if GameTracker hadn't re-resolved the DNS, would have continued being answered successfully.

So it's like GameTracker did re-resolve DNS, learned the new IP address, but says "there is no server in our database with this new IP address." Well, that's correct.... and is what using a DNS name in GameTrackers for our server was supposed to automatically resolve?

FAQ says "wait", so I am also waiting to see if it resolves itself. But the fact that it seems like GameTracker _did_ already resolve the new IP address, but now "fails" rather than having updated our GameTracker info to have this new IP address, has me concerned I'm waiting on something which is actually a bug and isn't going to change.

Thanks.

Resolved. "Whether the old server still responds" was listed as a factor in the steps for using DNS to migrate stats to a new server, so I shut down our forwarding from the old server IP address temporarily. In order to perhaps give GameTracker "more of a failure case" to react to.

Whether that helped or not, or whether it was just the passage of time, the GameTracker record for https://www.gametracker.com/server_info/dc.ea117.com:14567/ now resolves successfully again, and is pointing to the new IP address too.

Moved: Not a Gametracker bug.