3 ms·
The easy resolution here would be for microsoft to push an update that does the moral equivalent of adding hosts file lines 127.0.0.1 corp.com ::1 corp
by gpm 7y ago
The easy resolution here would be for microsoft to push an update that does the moral equivalent of adding hosts file lines
127.0.0.1 corp.com
::1 corp.com
- gfodor 7y agoThat's hardly a resolution, because it assumes such an update would actually be applied to all the machines in question.
- gpm 7y agoIf a machine is connected to the internet and not getting updates, it's fucked anyways.
- deleted 7y ago[deleted]
- swiley 7y ago1) windows has a hosts and resolve.conf file (don’t ask me where it is but I’ve seen it and it works) 2) what are likely the most risky applications tend to ignore the libc resolver and its configuration.
- joshuaissac 7y agoThe Windows hosts file is usually at C:\Windows\System32\drivers\etc\hosts. Winsock was modelled after BSD, hence the resemblance in the filename. /etc/resolv.conf is available from Bash when WSL is enabled. It reflects the settings from the registry by default, but can be made to be independent of them.
- Kaze404 7y agoI always wondered why it was in such an awkward location. It makes sense now.
- TimTheTinker 7y agoThat would break internal workflows for a lot of companies—they’re relying on “corp” as a bare TLD to resolve to an internal network endpoint. I bet many IT admins would find this “quick fix” that would “make it work again” by effectively removing that /etc/hosts entry. Perhaps a better patch would be to remove the [TLD] => [TLD].com DNS failover resolution feature.
- gpm 7y agoIf .corp is successfully resolving this change should have no impact, since the problem is only when .corp fails to resolve and the resolver falls back to .corp.com.
- TimTheTinker 7y agoSorry - you’re right. I misread. But I still think failing over from corp to corp.com is a bug, not a feature.
- gpm 7y ago> But I still think failing over from corp to corp.com is a bug, not a feature. I think it was a mistake, but you probably can't fix it now. Too many random pieces of code are going to be relying on it.
- pishpash 7y agoThat doesn't make sense. When .corp fails to resolve now, .corp.com is also a deadend because O'Connor turned the domain off, so nothing should happen to any software by not trying to access .corp.com. Surely a rule can be made in the resolver code that specifically in the case of .corp failing to resolve, short-circuit it there and do not failover to internet domains.
- gpm 7y agoRight, what you're suggesting is one implementation of what I meant by "the moral equivalent of adding these lines to /etc/hosts". I think TimTheTinker was suggesting the much more general fix of breaking the fallback for all domain names, not just .corp domain names.
- fanf2 7y agoWhat Microsoft should have done was read and implement https://tools.ietf.org/html/rfc1535 https://tools.ietf.org/html/rfc1535 and apply a bit more learning from others and a bit more foresight when they were setting up this disaster in the 1990s. I have a small bit of sympathy for them, because when Active Directory was first learning how to do domain names, they cost $100 per year and required a huge amount of bureaucratic nonsense. MS wanted to be able to sell their software to businesses that might never connect to the Internet. But they could have done a much better job.
- chx 7y agoAnd, of course, a great many internal computers will _never_ get an update from Microsoft. https://gs.statcounter.com/os-version-market-share/windows/desktop/worldwide https://gs.statcounter.com/os-version-market-share/windows/d... Windows 7 still has a quarter of the market...
- gpm 7y agoAs I said elsewhere, if it's not getting updates, it's fucked anyways. Support for Windows 7 can be purchased dates up to 2023... https://www.zdnet.com/article/microsoft-to-offer-paid-windows-7-extended-security-updates/ https://www.zdnet.com/article/microsoft-to-offer-paid-window...
- forty 7y agoYes, I'm not sure, why Microsoft doesn't do that by default from within Windows? (I mean that or any other way to hardcode whatever the domain is currently answering) Looks like it would fix most of the problem.