[Jenkins-infra] ns2.jenkins-ci.org problem

Olblak me at olblak.com
Fri May 11 13:41:45 UTC 2018


Hey,
Thanks for reporting, indeed there is already a ticket for it INFRA-1463 (https://issues.jenkins-ci.org/browse/INFRA-1463).
To make it short, the server that was running ns2 doesn't exist anymore.
At the moment, it's mainly a "work" bandwith issue, the dns needs to be moved to azure and a design need to be done.

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---

On Tue, May 8, 2018, at 10:25 AM, Jun Kuriyama wrote:
> 
> I'm not sure there is a ticket already or not...
> 
> (1) ns2.jenkins-ci.org (162.209.124.149) does not respond to usual UDP query
> 
> From pingdom history, problem exists at least from 2018-02-23.
> 
> http://dnscheck.pingdom.com/troubleshooting.php?domain=jenkins-ci.org
> 
> 
> (2) It has delegation issue
> 
> As I query to a0.org.afilias-nst.info (one of .org NS servers), it
> returns ns2.jenkins-ci.org A record as 173.203.60.151.  But I query to
> ns1.jenkins-ci.org, it returns as 162.209.124.149.  This is not
> consistent state.
> 
> 
> -- 
> Jun Kuriyama <kuriyama at s2factory.co.jp> // S2 Factory, Inc.
>              <kuriyama at imgsrc.co.jp>   // IMG SRC, Inc.
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra


More information about the Jenkins-infra mailing list