Jim says that he is looking for a new host for the media server but the media server is working fine. It is the Vanwanet DNS which needs fixing. Run the command line below to see that the Vanwanet DNS is pointing to the IP address 195.2.76.245 which is currently unresponsive though it was working fine before.

nslookup -type=A media.8kun.top ns1.vanwanet.com

All Jim has to do is tell Vanwanet to change the DNS back to the way it was and all will be fine. What is this bullshit about finding a new host? Why was the DNS changed in the first place? These are the IP addresses for "8kun.top":

94.103.81.80

94.103.82.74

94.103.94.73

193.178.169.19

195.2.93.193

Just fix the Vanwanet DNS for "media.8kun.top" to be the same. Why the fuck not?

>>14474091

>Vanwanet doesnt control settings another does

ns1.vanwanet.com is clearly a domain owned by Vanwanet. Why do you think that they don't control it?

>>14474129

>Mass Crowd

Isn't that redundant?

>>14474245

If what you say is true then why not just turn off the media server instead of using this roundabout method? After all, we CAN access the server with a simple "hosts" file fix.