Clarify public/private role for holmium (aka labs-ns2)
Closed, InvalidPublic
Actions

Assigned To

Authored By

	Andrew
	Mar 23 2015, 7:36 PM

Description

Holmium (the designate/pdns server) will be providing both internal and external dns service. It has a public IP and a public name (currently labs-ns2.wikimedia.org) which is good for the public part.

We're going to start with it serving internal IPs for internal labs instance names, e.g. util-abogott.testlabs.wikimedia.org. Instances could contact it via the public IP if necessary, but it would be nicer to do it via an internal IP so that we can tell the difference between queries.

...or... we just need two different dns servers entirely. I'm currently a bit confused.

Event Timeline

Andrew created this task.Mar 23 2015, 7:36 PM

Andrew assigned this task to mark.

Andrew raised the priority of this task from to High.

Andrew updated the task description. (Show Details)

Andrew added projects: Patch-For-Review, Cloud-Services.

Andrew added subscribers: gerritbot, Aklapper, Andrew.

OK, actually, this is mainly resolved by

https://gerrit.wikimedia.org/r/#/c/198820/

So, I'm not sure if this matters. It's weird to have a public dns server that serves up addresses for .eqiad.wmflabs addresses, but I'm not sure how we avoid that... it will depend on how this server interacts with the rest of our dns setup.

Andrew renamed this task from Provide internal IP access to holmium from labs instances to Clarify public/private role for holmium (aka labs-ns2).Mar 24 2015, 5:11 PM

Andrew set Security to None.

Andrew removed a parent task: T87280: Investigate replacing our custom DNS code with Designate.Jun 26 2015, 6:11 PM

I'm not sure what the purpose of this ticket is. Could you please clarify?

This was a note to self which is long since moot.

Clarify public/private role for holmium (aka labs-ns2)Closed, InvalidPublicActions

Description

Event Timeline

Clarify public/private role for holmium (aka labs-ns2)
Closed, InvalidPublic
Actions