• 0 Posts
  • 31 Comments
Joined 1 year ago
cake
Cake day: July 11th, 2023

help-circle
  • Then Paradox was developing it. They own the studio. Who else is going to build the game? An executive?

    I am sure that everyone would agree that Paradox owns/developed/published Europa Universalis 4… But that was made by “Paradox Tinto” or Stellaris was “Paradox Development Studio”… The publishing wing of Paradox doesn’t develop games. Obviously. But I don’t understand why thats in any way relevant to the discussion. Paradox (the company, not specifically the publishing wing) was 100% responsible for the development, the testing, and the publishing of Life by You. They built it, they took it down.








  • DNS engineer here, got two corrections to make if you care:

    the owner of Twitter.com couldn’t really do shit about you owning it.

    That’s not entirely true. .sucks is walking an extremely fine line and if they ever grow big enough and piss off enough companies, they will be shut down. Larry Strickling, head of the National Telecommunications and Information Administration has spoken on multiple occasions about his concerns about gTLD (what people are calling “novelty” TLD’s) abuse to redirect users incorrectly (either for parody or for malicious purpose) Source. ICANN absolutely will crack down if they think a gTLD is acting rogue as they would be afraid of the NTIA cracking down on them. Passing the gTLD rules was already very contentious for many reasons. Defensive domain list expansion being one of the biggest.

    There’s the other obvious issue that if you’re making a site like “twitter.sucks” you will have to be very careful not to infringe on their copy rights for things like their logo, etc. Especially if the basis of the site is to mock the .com version of the same.

    Surprisingly, no. Copyright infringement doesn’t apply to parody. Unless twitter.sucks is a fully functional site that draws in revenue (and not just from the humor, but from actually having a directly competing product), then it’s mostly safe from a copyright claim.







  • Well, it’s not just a money issue. There’s also the “are you knowledgeable, responsible, and have DNS engineers on staff” problem. If you own your own TLD, it means you can talk directly to the root zone. You could theoretically DDOS the root zone servers and cause them to crash. They would, of course, just revoke your TLD permanently & it wouldn’t really cause any noticeable disruption to the rest of the internet. You could also allow attack domains or shady websites. Maybe it could be used to pretend to be another site. Imagine owning “.conn” that would be a premium attack site TLD because it looks like “com”. There’s lots of other issues too.


  • If you initiate a zone transfer, you can now claim to be authoritative for a zone. That means you can be a ‘bad actor’ DNS server that serves fake records. In practice, this means that you can redirect people to an attack site.

    Let’s say you’re Joe the Random Internet User and you want to go to lemmy.world This is what happens in a non-attack (we’re skipping caching & non-authoritative answers for brevity):

    1. You type “lemmy.world” into your browser
    2. Your computer initiates a stub resolution for lemmy.world. (the trailing dot here isn’t a period. It’s the “true” FQDN)
    3. Computer looks at hosts file and doesn’t see anything
    4. DNS packets are sent to your configured DNS server. If you don’t have one configured, DHCP already configured it for you
    5. Your DNS server performs a recursive search for world by asking the root zone where the “world” Name Serer is
    6. root zone resolves world as:

    world. 3600 IN NS v0n0.nic.world.

    world. 3600 IN NS v0n1.nic.world.

    world. 3600 IN NS v0n2.nic.world.

    world. 3600 IN NS v0n3.nic.world.

    world. 3600 IN NS v2n0.nic.world.

    world. 3600 IN NS v2n1.nic.world.

    1. Your DNS server reaches out to one of those Name Server’s (That’s what the NS record is for) and asks it where “lemmy” is
    2. world Name Server responds with:

    lemmy.world. 300 IN A 172.67.218.212

    lemmy.world. 300 IN A 104.21.53.208

    1. Your DNS server contacts your computer and serves it those IP addresses. (A record’s are domain name to IP Address)

    Now lets say there’s a DNS spoof attack:

    1. Before the “world” server can get back to your DNS server, the hackers server interjects with it’s own authoritative claim that lemmy is here:

    lemmy.world. 300 IN A [attack site IP]

    1. Your DNS server contacts your computer and serves it that IP address. Your computer then contacts the attack site and you get a virus.

  • Companies don’t/can’t sell TLD’s. Only IANA can decide those. When the internet first started, .org, .net, .com etc. were handed out to non-profit organizations and the costs were purely to keep the servers running. Eventually though, when IANA decided to hand out country codes like .io (Indian Ocean), .cat (Catalonia) or .tv (Tuvalu), those countries rent their “desirable” names to private organizations that sell domain registrations for lots of money. In 2013, IANA decided to enact the gTLD auctions to help raise more money. Basically, if you wanted to (and had a lot of money & DNS engineers on staff), you could register any TLD you want provided you were willing to make a large donation to IANA. If someone else wanted it, they had to go into an action war over it. That’s how we ended up with things like .party or .sport or .world cough Now-a-days, if you want a TLD, you’d have to convince IANA to give you one… But good luck with that. They won’t give you one unless you’re some major corporation that can actually handle it. They also just don’t give them out. Usually it’s only when they really feel like more TLD’s are needed. It’s a very serious responsibility and mismanagement could accidentally DDOS a DNS root zone & impact the internet.


  • Friday I was doing a zone transfer! What are the odds?

    A zone transfer is like moving houses, except for an authoritative zone.

    In DNS, we have what’s called an authoritative zone. That means the device hosting the “resource records” (all the data that DNS passes around) is the “ultimate” answer. I.e, it’s not cached data. It’s not a hosts file. It’s not a recursive answer. It’s the real deal.

    When you want to move the authoritative zone to another server, you do a “zone transfer” that means the new server will copy all the resource records over TCP from current authoritative zone. The reason you may want to do this instead of manually hand-jamming it is that many large organizations have, sometimes, hundreds of resource records (last month I coordinated a zone transfer that was over 1000 records!).