zero-pad win32-slaveNN's hostnames in the build.sjc1.mozilla.com zone

RESOLVED FIXED

Status

P5
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: dustin, Assigned: arich)

Tracking

Details

This is not causing problems, but is unattractive and may trip up automated scripts at some point:

dustin@lorentz ~ $ host win32-slave5
Host win32-slave5 not found: 3(NXDOMAIN)
dustin@lorentz ~ $ host win32-slave05
win32-slave05.build.mozilla.org is an alias for win32-slave5.build.sjc1.mozilla.com.
win32-slave5.build.sjc1.mozilla.com has address 10.2.71.174
Probably also true in scl1.

Note to Amy: Mozilla does not zero-pad hostnames in the new naming scheme. Build is the exception, as they wanted to keep zero-padding. As such, there are some cases where things were set up in early days of the new scheme that aren't zero-padded.
This is P5 - don't rush it.  We should probably figure out if keeping the two-level DNS resolution is worthwhile first.
(Assignee)

Updated

8 years ago
Assignee: server-ops-releng → arich
(Assignee)

Comment 3

8 years ago
Looking at this more closely, what we have is chained CNAMEs in here as well:

win32-slave01	        IN  CNAME   win32-slave01.build.sjc1.mozilla.com.
moz2-win32-slave01      IN  CNAME   win32-slave01

We have CNAMEs pointing to CNAMEs, which is ugly at best, and later version of ISC's bind make you turn on this functionality since it's widely discouraged.  Is there a reason we have two sets of CNAMEs in addition to the A record?

If possible, I'd like to remove one or the other and go with one set of CNAMEs.
Status: NEW → ASSIGNED
(Assignee)

Comment 4

8 years ago
Okay, based on the conversation between Dustin and myself, the following has been done:

remove the moz2-win32-slaveNN CNAMEs
change A, PTR, to be win32-slaveNN.build.sjc1.mozilla.com. (with zero padding)
change win32-slave.build CNAME to point to A

dnsconfig/zones/mozilla.com/sjc1/build:
win32-slave01     IN  A	    10.2.71.210

dnsconfig/zones/mozilla.org/build/private:
win32-slave01	 IN  CNAME  win32-slave01.build.sjc1.mozilla.com.

dnsconfig/mpt-dmz/71.2.10.in-addr.arpa:
210               IN  PTR    win32-slave01.build.sjc1.mozilla.org.

dhcpconfig/mpt/vlan71.conf: 
host win32-slave01 { hardware ethernet 00:50:56:97:01:49; fixed-address 10.2.71.210; }

At the same time, I also cleaned up the other chained CNAMEs in 
dnsconfig/zones/mozilla.org/build/private.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Assignee)

Comment 5

8 years ago
This also required changes on the nagios end:

hosts.h:lazy_host:
win32-slave01.build.sjc1:bm-admin01:build

services.h:
$win32-slaves = win32-slave01.build.sjc1,...

hostgroups.cfg:
define hostgroup {        hostgroup_name  releng-win32-build        alias           RelEng Windows 32 Build Boxes
        members         win32-slave01.build.sjc1,...
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.