3 ms·

Spare me the kindness lecture. The entire rant, most of which is lacking in technical depth and understanding of name resolution despite the overconfidence, co

Spare 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 ago
Give 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 ago
  IPAddress <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 ago
    TV 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?

godelski 3y ago

Give 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 ago
IPAddress <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 ago
  TV 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?