Can I ask - why would anyone do this? Several URL shortening services of the past have shuttered and it has left the web littered with links to sites that can never be resolved (linkrot) - this to me just seems like a another surefire way to speedrun future deadlinks in forums etc. Why?
Edit - I have misunderstood the assignment.
This is targeted at self-hosted/personal-domain stuff only, not general internet site URL shortening/redirection.
It isn’t on the default port either, it’s on a random high number port which is why I thought it was extra odd they found it.
It isn’t on the default port either, it’s on a random high number port which is why I thought it was extra odd they found it.
Like the other commenter said, I dunno how the heck the griefers find the servers - but if it’s on the open Internet, they do.
I set up a server for me an a handful of mates - advertised the address nowhere. They told nobody. A month in a friend and I were playing as usual, and a player with a Russian username joined. I’m like “uh hi who are you?”. They stayed another minute or two while saying nothing, then left.
I think they left when they realized i had an anti-griefer permissions mod that protects the blocks in an area around the spawn point from being modified (its called ‘Flan’). So they joined, saw the server had some protections, and decided it wouldn’t be much fun for them.
Whitelist immediately enabled - no more random Russians.
In addition to other advice here just be aware that Minecraft servers are prime targets for griefing and abuse.
I recommend setting it to whitelist mode and then each kid your friend wants to join just has to send their username to him so you can add the username to the whitelist. Its an added overhead but it’s much less painful than reverting to a backup for a griefed server - and your kid won’t have to worry about other kids on-sharing the server address.
Simple question but can be a complex answer. Basically it depends where your phone gets DNS from: if it’s using the ISP DNS (or some other public DNS server) it will resolve the public internet IP of your server and the data will route out to the ISP WAN before being routed back in.
On the other hand you can configure a split DNS system, so say you are using your modem/gateway as your DNS server and it forwards DNS queries up to your ISP (or other) DNS server - a common setup, 1. you can add in a static host entry for your local server. Eg ‘yourservice.yourserverdomain.com = 192.168.1.20 (your server’s LAN IP)’
Now when your phone is on the WiFi and it looks up your server’s address it gets the local IP and routes locally, which will be faster.
If you need more info, search for terms like ‘reverse proxy split DNS best practice’.
Yeah I use Linux for my servers and my HTPC, but I never really hibernate or sleep those so I had no idea if it might occur there too. It’s great to hear this is not likely to be an issue - thanks
The problem I have with this I put the PC to sleep overnight every night - and like clockwork, Windows wakes it back up sometime overnight to do… Something.
I’ve been diagnosing the issue for years - checking wake timers, switching hardware devices permissions to wake the system off. I might fix it for a few months and then a new Windows update comes along and it’s back to its usual routine of waking itself.
Looking forward to seeing if it persists with Linux when I move at the end of support period for Win10 later this year.
Ah that is probably my bad then, I read it as being able to redirect arbitrary URLs, hence the need for geoblock and abuse protections - if it’s only your own self-hosted/personal domains then yeah that absolutely makes sense.