3 ms·
It’s always DNS
by nikanj 4y ago
It’s always DNS
- pletnes 4y agoExcept when it’s a compiler bug.
- papandada 4y agoFor a certain era for me, it was always "kerberos double hop"
- javajosh 4y agoNo sometimes its BGP, the stuff of nightmares.
- tomschlick 4y agoObligatory link to CloudFlare's IsBGPSafeYet? page: https://isbgpsafeyet.com/ https://isbgpsafeyet.com/
- nick__m 4y agoInternet-scale BGP is a nightmare, and it's a miracle that it works so well. But what makes BGP so nightmarish in a private enterprise network? As a software engineer who pivoted to infrastructure, I find that BGP is a lot better than the series of proprietary link-level SLAs that it replaced.
- zamadatix 4y agoI've always been partial to IS-IS for the IGP but I wouldn't say BGP is necessarily bad. Perhaps too many knobs and not exactly as speedy to react as you'd want for an IGP in all but basic topologies but both of those can be fixed by staying focused on tweaking a subset that makes sense. Also I think the whole iBGP vs eBGP thing drives people nuts.
- dnablob 4y agothis IGPs (IS-IS, OSPF, EIGRP) and BGP solve different problems and networks often need both. Some niche networks get away with using only BGP (massive datacenters), and some get away with using only an IGP (smaller networks), and some don't even need that (small networks).
- jimnotgym 4y agoI don't really do IT support any more, but when 'the internet was broken' at work last week my first reaction was to open cmd and nslookup a week known site! On corporate networks a missing dns server has been a major cause of issues.