Okay, I'm not exactly sure how to say this but when I update my game server domain IP address to my new game server IP address while my old game server is still running in the old IP address, GameTracker does not seem to update the IP addresses in it's database which causes the website to return the following error:

"The server you requested is not in the GameTracker database. We could not find the server you requested."

So basically it's like both new and old game servers are running at the same time, and the owner assigned a domain address to the server with the old IP when the server was originally added into the database, and it was running like that for a while, then the owner changed the domain's IP externally to a new IP while the old server is still running using the same old IP.

I have waited for more than 2 hours to see if there are any changes but the error stays the same. And, no. I haven't deleted my servers from GameTracker until now, I think the system gets confused which server IP to look up and returns the above error. And, yes. the domains were pinging to the new IP within first 5 minutes of change and the game client connects to the new server through the domain so I was sure this was not due to a delay in DNS changes.

Of course I can shut down the old game server or re-add the new server into GameTracker which will probably solve this but I thought if this is a bug that was hidden, it should be reported for a fix.

The domain name is checked for update automatically once every 24 hours, unless the server can not be contacted/scanned.
If the server can not be contacted/scanned, attempts to update the dns IP occur more frequently. How frequently has never been explicitly defined to my knowledge. I imagine it can be affected by server loads.

I am sure I am not telling you anything new when I say, the propagation of dns IP changes throughout the internet takes time in itself and may depend on the relative locations of the server / dns host name provider / Gametracker.
This can and does at times have an adverse effect on the length of time between a dns IP change, and the Gametracker scanners picking up on that change and making the adjustment.

The best solution is, ensure that your IP change has been effected locally (from a machine other than your server) and then to wait patiently.

Without explicit details such as server name, new/old IPs/domain name, I can provide no further insight. Even having those details, I may not be able to improve my response.

I guess I haven't managed to explain the original issue correctly, it might be causing some misunderstanding.

So as you said a domain will be checked once every 24 hours so this might not even be a bug because it has not been 24 hours since the new server got added so I don't really know. I'm going to re-add the server or shut down the old server so the database will hopefully get renewed. Still, if some developer can understand what I tried to say, go ahead and re-create this issue as above so you will know for sure what's going on.

If there is a server continuing to respond on the old IP address, then there will be no attempt to update the dns IP on Gametracker, except on the usual 24 hour schedule.

chimaera500 wrote:
If there is a server continuing to respond on the old IP address, then there will be no attempt to update the dns IP on Gametracker, except on the usual 24 hour schedule.

Exactly, thank you!