3 ms·
Sorry, but this really comes off as victim blaming and "domain knowledge"-eliteness. Victim blaming because AT&T shouldn't be doing these things in the first p
by godelski 3y ago
Sorry, but this really comes off as victim blaming and "domain knowledge"-eliteness.
Victim blaming because AT&T shouldn't be doing these things in the first place. Yes, you're right, you should set things up in a better way to prevent this from happening, but you're excusing the bad behavior by placing the blame on the user.
The elitism comes from the fact that we live in a specialized world. Not everyone is an expert in everything. If you think you are, I'm here to tell you you're just lying to yourself and thus undermining yourself. There's even plenty of good programmers and people who work on other technical domains that don't have all the knowledge around DNS. This is true for any technology or any specific task. If you're an expert is any domain you're probably quite aware that getting things right ends up being very nuanced. So if you recognize that, then you should recognize that's true outside your main domain.
Now if your intention is to help people and educate them then may I offer another way to formulate the comment?
If your ISP is making changes that break resolution of your local LAN you can do some configurations to prevent this. You should probably do this anyways. OpenWRT will perform this for you out of the box, but if you can't or don't want to flash your router you can <insert explanation here> or I found this guide [<insert link number>]
[<insert link number>]
Even if you think people are dumb (__especially__ if you think people are dumb) this message will get more people to fix their problems. You may want to get in the habit of writing like this because we all know that there are things that other people do that affect us. Or chose to do/use things that move the markets and politics and whatever that we then become subjected to. Attacking or blaming them doesn't help us get what we want. Being nice does. At least being nice is the easier way (and you'll probably be less stressed too).
- wannacboatmovie 3y agoSpare me the kindness lecture. The entire rant, most of which is lacking in technical depth and understanding of name resolution despite the overconfidence, could be completely avoided with an entry in /etc/hosts (or its Windows equivalent). Which for a small home network and for someone who doesn't understand or want to fiddle with DNS - is perfectly adequate. I remember a story in HN folklore from someone who worked at a large enterprise many years ago that used an insane massive deployment of hosts files in lieu of DNS.
- godelski 3y agoGive me the lecture, what do I put in /etc/hosts? How does this prevent AT&T fucking with me? How do I make this work on all my machines to prevent this issue? Like my smart TV?
- wannacboatmovie 3y agoIPAddress <tab> HostName1 <space> HostName2 etc.... Just copy the same hosts file to all your hosts. Why does your smart TV need to talk to internal hosts? If so, is it terrible to just use the IP? Or use zeroconf/bonjour which was developed specifically so normies would not have to deal with internal DNS. Your ISP router may implement DNS proxy or more likely doesn't do any name resolution at all; or their embedded DHCP server just passes the ISP DNS IPs to the devices and the one you get is dependent on if you turned on their privacy thing. In which case you don't have internal DNS and the fact that it worked at some point in the past was coincidental and due to some fallback mechanism. The shitty-equipment issue is not unique to ATT. The best solution is to do what others suggest; place the ATT gateway in bridge mode and get your own router that runs OpenWRT; you can program your own local hostnames using the web GUI without touching the hosts file or knowing how DNS works, and everything should just work.
- godelski 3y agoTV should talk to internal hosts so it can play content that is hosted by internal hosts. Sure, shitty-equipment is prolific but how do we fix it and how do we pressure them to stop making shitty equipment. > The best solution is to do what others suggest; place the ATT gateway in bridge mode and get your own router that runs OpenWRT; How? Do I just link them with an ethernet cable?