31–40 of 69 posts
So obvious in retrospect, and so little talked about. Could something be done with the DNS / IP protocols that would improve this?
Something digitalocean could do? Once an ip is assigned to another customer either: warn, warn/disable dns, change dns automatically
I once inherited an ip block the previous owner never pointed his SEO network domains away from. I setup a wildcard, captured all the traffic and made good coin for quite a while.
Earlier quoted context omitted.
that doesn't prevent the "a domain you own points at someone elses server and they can do unsavory things with it". (Especially bad if it's a subdomain, or a domain linked to one of your others.) it's not for OPs sake, but for the domain owners sake.
My domain name is under my control and therefore should not point to servers I do not trust. If one's domain name points to an untrusted server, a very fundamental mistake has been made and no amount of configuration can fix the issues associated with it. Webmasters we have two things in control: 1. Their domain name. It should point to trusted servers only. 2. Their web server. It should be configured to return succ…
Edit: only asking for cases where #1 does not apply - that is you don’t have domains or sub-domains pointing at rogue IPs
So obvious in retrospect, and so little talked about. Could something be done with the DNS / IP protocols that would improve this?
The protocols are working as intended.
Yep. A few years ago I had a server on DigitalOcean and stopped using it. I forgot to remove the A record for it on a sub-domain connected to my main site and suddenly a sub-domain on my main site was serving ~400,000 pirated PDFs because the old server's IP address was in control by someone else. I wrote about it here: https://nickjanetakis.com/blog/a-recycled-ip-address-caused-... And it was discussed on HN back th…
I mean hell, create a bunch of random bogus A records too just in case any of them wins the lottery ticket. A records are free, after all.
Earlier quoted context omitted.
My domain name is under my control and therefore should not point to servers I do not trust. If one's domain name points to an untrusted server, a very fundamental mistake has been made and no amount of configuration can fix the issues associated with it. Webmasters we have two things in control: 1. Their domain name. It should point to trusted servers only. 2. Their web server. It should be configured to return succ…
Just curious - can you explain #2 ? I get that someone can register some freebitcoin.xyz and point to your IP, but the content is still controlled by you, right? What is the security angle here if your host returned a static index.html to any host? Some CSRF? Edit: only asking for cases where #1 does not apply - that is you don’t have domains or sub-domains pointing at rogue IPs