dns issues with persona_deployer

[Ryan Kelly]

Hi All,


The persona_deployer seems to be stuck and I don't know enough about
our DNS setup to fix things.

Currently "login.dev.anosrep.org" resolves to "54.234.180.118" which
seems to be dead - possibly an old awsbox that has been torn down.

The deployer tries to talk to this box to check the
currently-deployed version, times out, and produces an error in IRC. So
we need to update the hostname to point at a live box.

The deployer seems to have logic to do this automatically, talking to
the zerigo API to point "login.dev.anosrep.org" towards the latest
deployment. It appears to have done this correctly. But zerigo is not
the authoritative nameserver for this domain, so the change doesn't take
effect?

Basically, I think this needs someone with more insight into the DNS
setup to intervene and set things straight.

Volunteers? :-)


Ryan

[John Morrison]

Actually, zerigo.net is authoritative for login.dev.anosrep.org.

But I was deploying an awsbox about 45 minutes ago, and despite it
telling me that it had configured the DNS name I had chosen, when I did
a `dig` of that name, it returned NXDOMAIN. I'm wondering if there's an
issue with zerigo or our account, and an error is being swallowed
somewhere.

John

> _______________________________________________
> dev-identity mailing list
> dev-id...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-identity

[Ryan Kelly]

On 15/05/2013 11:24 AM, John Morrison wrote:
> Actually, zerigo.net is authoritative for login.dev.anosrep.org.

Right, thanks; I kept digging and figured out how that fit together.

> But I was deploying an awsbox about 45 minutes ago, and despite it
> telling me that it had configured the DNS name I had chosen, when I did
> a `dig` of that name, it returned NXDOMAIN. I'm wondering if there's an
> issue with zerigo or our account, and an error is being swallowed
> somewhere.

I think you're on the money here. The zerigo management console shows
login.dev.anosrep.org pointing to a new, good IP address. But it's not
actually resolving as that address in the world.

So we may just have to wait for zerigo to right itself :-(

(And work on migrating this to Route53)


Ryan

[Lloyd Hilaiel]

On May 14, 2013, at 7:42 PM, Ryan Kelly <rfk...@mozilla.com> wrote:

> So we may just have to wait for zerigo to right itself :-(

Last time this happened I filed a complaint with zerigo, waited 4 hours, nothing. The tweeted at them and it was magically resolved within 10 minutes.

Route53!

lloyd

[John Morrison]

So, nominally, zerigo DNS seems to have sorted things out and
login.dev.anosrep.org is up.

John

On 5/14/13 6:42 PM, Ryan Kelly wrote:
> On 15/05/2013 11:24 AM, John Morrison wrote:
>> Actually, zerigo.net is authoritative for login.dev.anosrep.org.
>
> Right, thanks; I kept digging and figured out how that fit together.
>
>> But I was deploying an awsbox about 45 minutes ago, and despite it
>> telling me that it had configured the DNS name I had chosen, when I did
>> a `dig` of that name, it returned NXDOMAIN. I'm wondering if there's an
>> issue with zerigo or our account, and an error is being swallowed
>> somewhere.
>
> I think you're on the money here. The zerigo management console shows
> login.dev.anosrep.org pointing to a new, good IP address. But it's not
> actually resolving as that address in the world.
>

> So we may just have to wait for zerigo to right itself :-(
>