I hope this is the final update on the "Malware" story now.
You can't imagine how crazy things can be on the internet sometimes.
How things started:
Our SAS Gameserver is running on a dedicated server with a static IP address but currently with no DNS entry.
That's why I decided to register the subdomain "sas.fsim.us" on a free DynDNS hoster.
Everything was fine until some other user registered some other "*.fsim.us" subdomain, where apparently malware was spread.
As a result, Google decided to treat all "*.fsim.us" suspicious, which affected our "sas.fsim.us" subdomain as well, even though we've never been spreading any malware at all.
Therefor I decided to ask Google to rescan our subdomain and additionally I contacted the "fsim.us" owner to tell him that lately a user joined his (free) subdomain offer who apparently spreaded malware. Since there were only 20 hosts on that domain, I thought it would be easy for him to sort it out.
But...
How things proceeded:
The "fsim.us" owner kindly replied to my mail, thanked me for bringing this to his attention and said that he might have to clean all records to get rid of this, but I should wait for further information.
However in fact the "fsim.us" owner decided not only to kick out all subdomains and lock his free offer, no... he even tagged all accounts hosting "fsim.us" subdomains as "malware" to the DynDNS hoster.
As a result, all affected accounts got locked there without further notice. Great sh*t.
How we're operating now:
I decided to move away from that DynDNS hoster because I can't deal with services that lock you out for nothing with not prior notice just by a wrong tag from someone else.
We do have a new DynDNS hoster now and the SAS Gameserver from now on is reachable at
sas1946.rocks
So the DNS connection to our UP3 server now would be
sas1946.rocks:21010
And the stats page can be reached at
http://sas1946.rocks/up3test/I'm sorry for the inconvenience.
Best regards - Mike