Status
People
(Reporter: bear, Assigned: arr)
Tracking
Details
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
(Assignee) | ||
Comment 1•6 years ago
|
||
That's correct, the w64 boxes are not in the same subdomain. winbuild vs build.
Assignee: server-ops-releng → arich
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
(Reporter) | ||
Comment 2•6 years ago
|
||
(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?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 3•6 years ago
|
||
What's the first search domain for you at home ? Gonna guess it's build.mozilla.org
Comment 4•6 years ago
|
||
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.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago → 6 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
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.
Description
•