jenkins-ci.org DNS issues
R. Tyler Croy
from GoDaddy, I missed a crucial step and made a mistake which has resulted in
the jenkins-ci.org domain name becoming unresolvable.
We were using GoDaddy's DNS service as well, and I mistakenly assumed that DNS
records would be valid until the completion of the transfer.
Turns out this was a *bad* assumption. GoDaddy apparently nullifies all DNS
records in its DNS service as soon as its end of the transfer transaction
occurs.
Due to the archaic nature of the DNS registrar system, I honestly have no
timeline other than "within 5 days" for the transfer to complete. Once it is at
our new registrar (Namecheap), their DNS service will automatically pick up the
zone file which I've configured.
In the meantime however, if you need to hit our services, you can add some
hosts manually to your host file from our zone file which I've uploaded here: <https://gist.github.com/1525472>
I apologize for the troubles, I knew we wouldn't get through this transfer
unscathed, I didn't anticipate a cockup of this size though (this is why I've
been putting off leaving GoDaddy for *months*).
Cheers
- R. Tyler Croy
--------------------------------------
Code: http://github.com/rtyler
Chatter: http://twitter.com/agentdero
rty...@jabber.org
R. Tyler Croy
On Tue, 27 Dec 2011, R. Tyler Croy wrote:
> In the process of transfering the jenkins-ci.org and jenkins-ci.com domains
> from GoDaddy, I missed a crucial step and made a mistake which has resulted in
> the jenkins-ci.org domain name becoming unresolvable.
I've gone ahead and brought up a temporary DNS server which will answer
requests for everything under jenkins-ci.org.
If you add "nameserver 140.211.15.121" to the top of your resolv.conf (the
server won't give results for anything that isn't jenkins-ci.org, promise!)
then you will be able to navigate some of the Jenkins ecosystem
Some things won't work, such as logging into the wiki/JIRA. I'm on the fence
whether I should fix this or not.
R. Tyler Croy
On Tue, 27 Dec 2011, R. Tyler Croy wrote:
>
> On Tue, 27 Dec 2011, R. Tyler Croy wrote:
>
> > In the process of transfering the jenkins-ci.org and jenkins-ci.com domains
> > from GoDaddy, I missed a crucial step and made a mistake which has resulted in
> > the jenkins-ci.org domain name becoming unresolvable.
The domain transfer is complete and I'm now waiting for our new primary and
secnodary DNS nameserver settings to propagate.
Depending on how rapidly your upstream DNS provider updates from the root
nameservers, you should see jenkins-ci.org coming back around anywhere from an
hour to 6 hours from now.
R. Tyler Croy
On Wed, 28 Dec 2011, R. Tyler Croy wrote:
>
> On Tue, 27 Dec 2011, R. Tyler Croy wrote:
>
> >
> > On Tue, 27 Dec 2011, R. Tyler Croy wrote:
> >
> > > In the process of transfering the jenkins-ci.org and jenkins-ci.com domains
> > > from GoDaddy, I missed a crucial step and made a mistake which has resulted in
> > > the jenkins-ci.org domain name becoming unresolvable.
>
>
> The domain transfer is complete and I'm now waiting for our new primary and
> secnodary DNS nameserver settings to propagate.
>
>
> Depending on how rapidly your upstream DNS provider updates from the root
> nameservers, you should see jenkins-ci.org coming back around anywhere from an
> hour to 6 hours from now.
Now that we're in the clear, I think this thread is officially over :)
I've posted a post-mortem of sorts on my blog here if you're interested:
<http://unethicalblogger.com/2011/12/29/regarding-jenkins-dns-issues.html>
Didier Durand
You're right: site is again accessible from my place (France)
regards
didier
> < 1KViewDownload