Looks like hug of death. Nice when it was going.
Restarted the server and it should be back up for now :). Here's the culprit:
> 2021/12/15 18:39:10 http: Accept error: accept tcp [::]:8080: accept4: too many open files; retrying in 1s
Mess with DNS
21–30 of 94 posts
Re: Mess with DNS
#22Very cool project!
It's interesting to see how different DNS providers cap the maximum TTL.
Google uses 21600s
Quad9 uses 43200s
Cloudflare does not cap at all!
And my personal unbound uses 86400s (which is the default)
Re: Mess with DNS
#23Very cool.
dig 'a test.hazel10.messwithdns.com' txt +short
"test"
Re: Mess with DNS
#24What’s happening…when I set a long/short TTL? Real answer: many ISP’s DNS servers are set to ignore whatever you set and use a value they feel works best for themselves.
Re: Mess with DNS
#25Earlier quoted context omitted.
Humans individually are pretty useless. Abandon a random human in a jungle and they will likely perish soon no matter how smart and well educated they are. The strength of humanity is teamwork, working together to build things other groups can build things upon. Abandon 100 random humans in the same jungle and they will build a town.
>Abandon 100 random humans in the same jungle and they will build a town. https://en.wikipedia.org/wiki/Lord_of_the_Flies I'm not sure -- but I do think it would be interesting how that would turn out. Australia would founded in this sort of fashion. I think there's a bit more nuance though.
except that's fiction, and this is non-fiction: https://en.wikipedia.org/wiki/Tongan_castaways
Re: Mess with DNS
#26On the security aspect, I wonder how is this site affected services that do domain ownership verification [1] where they assume that only a person who owns the domain can edit dns records. I think letsencrpt ACME protocol [2] does it for SSL certs too. This site does create a subdomain for every user, so may be these issues don't apply. [1] https://support.google.com/a/answer/183895?hl=en [2] https://letsencrypt.org/…
At least for certificate issuance they can turn it off via a CAA record:
https://en.wikipedia.org/wiki/DNS_Certification_Authority_Au...
Re: Mess with DNS
#27The tech is fantastic, and your writing skills also stood out to me. This is excellent work all around.
Re: Mess with DNS
#28This is a neat tool! FYI, make sure the domain is registered with Safe Browsing in advance. If one subdomain is cataloged as malicious by google the entire domain can be flagged. It can be a pain to deal with.
hypothetically, what happens if a domain is catalogued by malicious? Also who catalogues it? If you haven't bought the domain from Google, the only thing that Google can do is not show the domain on google search results. Did I miss anything?
Re: Mess with DNS
#29This is a neat tool! FYI, make sure the domain is registered with Safe Browsing in advance. If one subdomain is cataloged as malicious by google the entire domain can be flagged. It can be a pain to deal with.
hypothetically, what happens if a domain is catalogued by malicious? Also who catalogues it? If you haven't bought the domain from Google, the only thing that Google can do is not show the domain on google search results. Did I miss anything?
> If you haven't bought the domain from Google, the only thing that Google can do is not show the domain on google search results. Did I miss anything?
I would imagine they might also show warnings in Chrome.
Re: Mess with DNS
#30Earlier quoted context omitted.
Julia Evans's cool stuff aside (and it is _very cool_, we need all the high quality didactic material we can get!), all this info _is_ on the net. I'm always surprised when I see engineers (like in that linked post) who don't understand how to do things like regional failovers, DNS load balancing, load balancing strategies, load shedding, circuit breaking, AZ balancing/failover, etc. These are pretty standard concept…
I've never seen anything at all as interactive & playful as this. Nothing that comes close. All in one, designed to create the experience of DNS. It's in the name: Mess with DNS. That makes it far far far & away different And I think that makes all the difference. I tend to believe very strongly in hands on experience, think that seeing things happen yourself & getting to play is by far the best way to learn, just in…
> I've never seen anything at all as interactive & playful as this. Nothing that comes close. All in one, designed to create the experience of DNS. It's in the name: Mess with DNS. That makes it far far far & away different
Oh absolutely! I don't mean to diminish this. The ability to interact and play also works very well for my own learning.
> There's a theory of education called Constructivism[1] that is broadly similar. Adherents include folks like Seymore Papert[2], creator of Logo, employee at One Laptop Per Child (which I think is the most interesting & innovative software environment we've ever created, vastly under-appreciated). Projects like Logo are supposed to create that hands on feedback, to make programming not just writing scripts & having programs run, but ways to see the code really execute, to create more interactive modes.
+100
> With software eating the world, it is so so so important to me not just to create knowledge, to tell tales of what software is, but to let people have the experience themselves. To create playgrounds to meddle, to mess around. I wish so much that applications could actually show & explain what they are doing, what's inside of them, could reveal their workings, but we're so far away from that Enlightened world, we've fallen into such deep shadows imo.
You bring up a good point overall about the lack of interactive materials for engineers/students/interested folks. I also suggest opening up any cloud provider (cheap for playing around is probably better!) and trying these things with services like Traefik (which are easy to configure/play with). Try to do some multi-region failover stuff, observe what happens with different load balancing strategies, that sort of thing. It reminds me a lot of watching videos about setting up IP networks, stuff like Cisco certification material.
You've given me some food for thought on educational materials for sure.
> As for the lack of knowledge/experience, I'd say that most engineers don't have familiarity because there's not a lot of opportunities to set up & learn systems work; most coders spend their time coding, not setting up bits of infrastructure to run code on. You yourself also say "writing the code is the easiest part", which underscores just how complex/inter-related/particular all the systems/infrastructure stuff is, how probable it is engineers might not feel fully competent or brave enough to engage.
Yeah this stuff isn't easy and operational work is often a different skillset than writing code.