742106 - dns lookup failing for w64-ix-slave### CNAME lookups on cruncher

Status: RESOLVED WORKSFORME

(Infrastructure & Operations :: RelOps: General, task)

Description

[Mike Taylor [:bear]]

on cruncher logged in as bear:

$ nslookup w64-ix-slave12.winbuild.scl1.mozilla.com
Server:         10.2.74.125
Address:        10.2.74.125#53

Non-authoritative answer:
Name:   w64-ix-slave12.winbuild.scl1.mozilla.com
Address: 10.12.40.32

$ nslookup w64-ix-slave12
Server:         10.2.74.125
Address:        10.2.74.125#53

** server can't find w64-ix-slave12: NXDOMAIN

$ ping w64-ix-slave12
ping: unknown host w64-ix-slave12

$ cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search build.sjc1.mozilla.com
nameserver 10.2.74.125
nameserver 10.2.74.127

Comment 1

[Amy Rich [:arr] [:arich]]

That's correct, the w64 boxes are not in the same subdomain.  winbuild vs build.

Comment 2

[Mike Taylor [:bear]]

(In reply to Amy Rich [:arich] [:arr] from comment #1)
> That's correct, the w64 boxes are not in the same subdomain.  winbuild vs
> build.

I'm trying to monitor them *from* cruncher.  If I do the same lookup from home I get dns resolution and I can ssh to them.

If I can't do this from cruncher then what host on the build network can I use to monitor across subdomains?

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

What's the first search domain for you at home ? Gonna guess it's build.mozilla.org

Comment 4

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

The tools should always be using full hostnames - not relying on the host's search domain.

My understanding was that the tool was going to use *.build.mozilla.org CNAMEs to determine the fqdns when necessary, and then generally use the fqdns.