It’s always DNS
For a certain era for me, it was always "kerberos double hop"
No DNS address record found for repo.maven.apache.org
11–20 of 20 posts
Re: No DNS address record found for repo.maven.apache.org
#12It’s always DNS
No sometimes its BGP, the stuff of nightmares.
Re: No DNS address record found for repo.maven.apache.org
#13It’s always DNS
I 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.
Re: No DNS address record found for repo.maven.apache.org
#14It’s always DNS
No sometimes its BGP, the stuff of nightmares.
Internet-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.
Re: No DNS address record found for repo.maven.apache.org
#15That's why you run your own repo as a proxy
Re: No DNS address record found for repo.maven.apache.org
#16Earlier quoted context omitted.
No sometimes its BGP, the stuff of nightmares.
Internet-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.
I'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.
Re: No DNS address record found for repo.maven.apache.org
#17In the short term, you could use https://repo1.maven.org/maven2 - but both the regular (repo, repo1).maven.apache.org and uk.maven.org aren't okay right now. :/
uk.maven.org went offline years ago, although it's still listed in the mirror metadata at https://repo.maven.apache.org/maven2/.meta/repository-metada...
If anyone who can fix that is reading, there's an issue here: https://issues.apache.org/jira/browse/MNGSITE-471
Re: No DNS address record found for repo.maven.apache.org
#18It’s always DNS
No sometimes its BGP, the stuff of nightmares.
Obligatory link to CloudFlare's IsBGPSafeYet? page: https://isbgpsafeyet.com/
Re: No DNS address record found for repo.maven.apache.org
#19Ah, that's why my builds were failing...
Mine, too. I had a sleepless night, so around 4:30 am CEST I started attacking a certain problem in an Android app. Wham!
Re: No DNS address record found for repo.maven.apache.org
#20Earlier quoted context omitted.
Internet-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.
I'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.
this
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).