And the best possible outcome is they contact you and buy it for some much larger amount than you paid for it.
I wouldn’t touch this with a 10 foot pole. Squatting on domains that contain a trademark with the purpose of forcing a company to pay you out for it is illegal. There would need to be intent, but just going to court over something like that would NOT be worth it.
I had a similar thing happen where my last name was also part of a trademark for a huge institution. As soon as I registered a domain with the name in it, I got an email from their legal department demanding I forfeit the domain to them or they would take legal action.
I replied that the domain was my surname, and that it wasn’t being used commercially at all, much less in the industry they’re in, and I actually got an email back saying they’d back off as long as I didn’t try to pull any funny business.
Or not have the website listen on port 80, or redirect connections from http to https on connect. Lots of very simple ways to correct this problem.
That’s what it’s called. Linode is gone my friend. It’s time to say goodbye.
Your browser is redirecting, the site is not.
It’s because you linked to the site using http://. This is something the site should account for, but doesn’t.
The site is encrypted but you can also access the site over http. The author hasn’t configured any kind of HTTPS upgrade. This is an easily correctable oversight that a self proclaimed “self hosting expert” should have accounted for.
You mean Akamai Connected Cloud, formerly Linode.
Before anyone gets excited, 49 out of 50 states are at-will. So the purpose of this post isn’t about being mistaken about their ability to be shitcanned, only that they’re mistaken about the type of law that allows it.
My favorite part about that nonsense is that until 1954-55 God didn’t appear either in the pledge of allegiance or on our money. You can bet your bottom dollar if you took that line out of the pledge though conservatives would have a fit over “Woke revisionism” even though it itself is a revision.
Akamai Connected Cloud. Removing old branding is a chore and you keep some of the old URLs for awhile to not immediately break things, but they have officially changed the name. Linode is no more unfortunately.
Linode? You mean Akamai Connected Cloud?
because they aren’t MAKING Microsoft sysadmins anymore.
I mean as opposed to what? Windows admins probably still make up the lions share of Sysadmins and I don’t really see how that would stop now.
https://www.usememos.com/ Would be great for this.
You clearly don’t understand a single thing about how the internet works and are very confused. Let me help you out.
how you self host a CDN hosted by fastly???
You don’t? The website is what would be self hosted. Not Fastly.
When did I resolve the Hostname to a DNS record? … I resolved it’s domain to an IPv4 address which points entirely to a fastly server
Right there. You resolved the host record, probably an A record or ANAME for the website (dev.to) into an IPv4 address, using DNS.
It’s not a resource that get’s delivered by CDN, it’s the whole fucking website they are serving, which is a service they sell and that’s not self hosting.
Here’s what you’re critically misunderstanding about this. Just because you resolve the record for a website and the IP that’s returned belongs to fastly does not mean fastly is hosting the content. You literally haven’t done anything to prove that the website isn’t self-hosted on a computer in some guys garage. You’re making assumptions based on ignorance and using those assumptions to gatekeep self hosting because you don’t even know what you don’t know. It’s very possible that site isn’t self hosted, but so far you haven’t actually found any proof of that like you think you have.
If you think a domain is a hostname and an IPv4 address is a DNS record
A domain can have several host records of different types including one at the root of the domain. What you’re resolving isn’t “a domain” it’s a single record for that domain, and its associated IP address is contained in the DNS record. If you’d like to familiarize yourself with this system, try this: https://www.dummies.com/book/technology/information-technology/networking/general-networking/dns-for-dummies-292922/
It’s clear that you’re a hobbyist with very little understanding of how the internet and self hosting works on a fundamental level and that’s ok. But I recommend instead of wasting your energy being confidently wrong very publicly for the purpose of gatekeeping, you use that energy to learn how these things actually work instead.
Of course it would be self hosting. If the website isn’t hosted on fastly, and is hosted by an individual, that would be the definition of self hosting. You’re also assuming that Fastly is caching responses, do you know that for certain?
Literally all you’ve done so far is resolve the host name to a DNS record. You think you’ve done something, but you haven’t.
Oh yeah like that’s part of it. If this article is supposed to be a call to action, somebody who starts looking into “homelabs” is going to get confused, they’ll get some sticker shock, and they won’t understand how they apply to what’s said in the article. They’ll see a mix of information from small home servers to hyperconverged infrastructure, banks of Cisco routers and switches, etc. my first home lab was a stack of old Cisco gear I used to study for my network engineering degree. If you stumbled upon an old post of mine talking about my setup and all you’re looking for is a Plex box you’ll be like “What the fuck is all this shit, I’m not trying to deal with all that”
“Self hosting”, and “home server” are just more accurate keywords to look into and actually see things more closely related to what you want.
Fastly is also a CDN. The fact that a website is behind Fastly doesn’t imply that it isn’t selfhosted at all.
Only if nothing on it is permanent. You can have a home lab where the things you’re testing are self hosted apps. But if the server in question is meant to be permanent, like if you’re backing up the data on it, or you’ve got it on a UPS you make sure it stays available, or you would be upset if somebody came by and accidentally unplugged it during the day, it’s not a home lab.
A home lab is an unimportant, transient environment meant for tinkering, prototyping, and breaking.
A box that’s a solution to something, that’s hosting anything you can’t get rid of at a moments notice, is just a home server.
I have a similar setup and I just have the reverse proxy on the VPS. It then proxies back to the home server on whatever port the service is on. And yes you can forward the original client IP if you wish.