1318375 - No DNS entry for elasticsearch-private.bugs.scl3.mozilla.com ?

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Infrastructure, defect)

Description

[Kyle Lahnakoski [:ekyle]]

It appears elasticsearch-private.bugs.scl3.mozilla.com  is no longer resolving for me

> C:\Users\kyle>curl elasticsearch-private.bugs.scl3.mozilla.com
> curl: (6) Could not resolve host: elasticsearch-private.bugs.scl3.mozilla.com

I am on the MozillaVPN.

Comment 1

[Kyle Lahnakoski [:ekyle]]

I am guessing it started happening around Thu, 10 Nov 2016 09:36:15 -0800 (PST)

Comment 2

[Kendall Libby [:fubar] (he/him)]

Nuts, I didn't think anything was actually using that address, from looking at things. I changed them to prevent confusion with the new ES cluster for BMO.

esfrontline-private-vip.bugs.scl3.mozilla.com 
esfrontline-public-vip.bugs.scl3.mozilla.com 

Sorry about that. :-(

Comment 3

[Kyle Lahnakoski [:ekyle]]

may we reinstate the address until January? I will review my code and dashboards to find all instances if this address, and work on deploying fixes.

Comment 4

[Kendall Libby [:fubar] (he/him)]

I've added a CNAME that should be visible in ~15min or so. Do we need to do the same for the public one?

Comment 5

[Kyle Lahnakoski [:ekyle]]

The public one is probably only used by me, and not needed.  Dashboards all use https://esfrontline.bugzilla.mozilla.org:443 for the public data.

Comment 6

[:dhouse]

:ekyle is this fixed and working now?

I see this in inventory:
FQDN 		 		 		Target 	
elasticsearch-private.bugs.scl3.mozilla.com 	esfrontline-private-vip.bugs.scl3.mozilla.com

And it resolves for me:
$ host elasticsearch-private.bugs.scl3.mozilla.com
elasticsearch-private.bugs.scl3.mozilla.com is an alias for esfrontline-private-vip.bugs.scl3.mozilla.com.
esfrontline-private-vip.bugs.scl3.mozilla.com has address 10.22.82.50

Comment 7

[Kyle Lahnakoski [:ekyle]]

Yes, it is working now.  Thank you!