1452775 - Update ns record for taskcluster-worker.net

Status: RESOLVED FIXED

(Infrastructure & Operations :: DNS and Domain Registration, task)

Description

[Brian Stack [:bstack]]

Currently this is set to some docker cloud addresses. Please update this to be the following two servers:

ec2-34-250-14-47.eu-west-1.compute.amazonaws.com.
ec2-54-187-183-25.us-west-2.compute.amazonaws.com.

Thanks for any help! Let us know if we can do anything.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

(this is similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1274062)

Comment 2

[Brian Hourigan [:digi]]

I'm not getting a SOA response from ec2-34-250-14-47.eu-west-1.compute.amazonaws.com or ec2-54-187-183-25.us-west-2.compute.amazonaws.com for taskcluster-worker.net.

If I make the change queries for taskcluster-worker.net will not function

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

They've never served SOA's, and it has worked OK for years.  They don't serve NS records either.

I know, I know.. but let's make the change and see what happens.  The current situation is also non-functional, so it can't get worse.

Comment 4

[Brian Hourigan [:digi]]

(In reply to Dustin J. Mitchell [:dustin] pronoun: he from comment #3)
> They've never served SOA's, and it has worked OK for years.  They don't
> serve NS records either.
> 
> I know, I know.. but let's make the change and see what happens.  The
> current situation is also non-functional, so it can't get worse.

No problem - I was just being cautious. I submitted the change but it got kicked back:

Failed to change nameservers from: [stateless-dns-1.8ba909e3.cont.dockerapp.io, stateless-dns.d85ca0db.svc.dockerapp.io] to: [ec2-54-187-183-25.us-west-2.compute.amazonaws.com, ec2-34-250-14-47.eu-west-1.compute.amazonaws.com] because: There was an error creating host ec2-54-187-183-25.us-west-2.compute.amazonaws.com at the registry. Any actions depending upon the successful creation of this host have been aborted.

I'm reaching out to our registrar to find out what the issue is.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

Jonas, would it be terribly difficult to also serve an appropriate SOA from this application, if the lack of same turns out to cause issues?

Comment 6

[Jonas Finnemann Jensen (:jonasfj)]

@dustin, It probably wouldn't be so hard -- if I knew what it was.
I think at the time wikipedia could explain to me what the SOA record was good for, so I just ignored it :)

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

It looks like that's not necessary (we discussed in vidyo).

Comment 8

[Brian Hourigan [:digi]]

Glue records created and nameservers changed.

ns1.taskcluster-worker.net 52.49.228.53
ns2.taskcluster-worker.net 34.213.136.122