Closed
Bug 592745
Opened 14 years ago
Closed 14 years ago
change DNS servers for releng servers
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jabba, Assigned: jhford)
References
Details
Since moving to the new proxy server, which also serves as a DNS cache, there are still some servers using the old server. Please ensure that no servers are using 10.250.48.7 as their DNS server and change them all to use 10.250.48.16 instead. Some servers that are still using the old server: 10.250.48.136 10.250.48.137 10.250.48.138 10.250.48.139 10.250.48.236 10.250.48.240 10.250.48.241 10.250.48.246 10.250.48.247 10.250.51.72 10.250.48.186 10.250.51.157 10.250.49.80 10.250.50.174 There might be some others. I think most of these are masters and ref machines or other slaves that haven't rebooted in a long time. My goal is to shutdown this DNS server on Thursday, so all clients should be pointing to the new proxy for DNS. Theoretically, if any get missed, they'll just time out on their DNS lookups and use the other server in /etc/resolv.conf, but since these are masters, I think having you reconfigure them during the downtime is best.
Assignee | ||
Comment 1•14 years ago
|
||
A.k.a staging-mobile-master.build.mozilla.org geriatric-master.mv.mozilla.com talos-master02.build.mozilla.com talos-staging-master02.build.mozilla.org test-master02.build.mozilla.org talos-r3-fed-ref.build.mozilla.org talos-r3-fed-ref64.build.mozilla.org test-master01.build.mozilla.org mv-production-puppet.build.mozilla.org talos-r3-fed64-043.build.mozilla.org maemo-n810-71.mv.mozilla.com talos-r3-fed64-053.build.mozilla.org talos-r3-fed64-002.build.mozilla.org qm-laddon01.build.mozilla.org
Updated•14 years ago
|
Assignee: nobody → jhford
Assignee | ||
Updated•14 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > A.k.a > staging-mobile-master.build.mozilla.org > geriatric-master.mv.mozilla.com > talos-master02.build.mozilla.com > talos-staging-master02.build.mozilla.org > test-master02.build.mozilla.org > talos-r3-fed-ref.build.mozilla.org > talos-r3-fed-ref64.build.mozilla.org > test-master01.build.mozilla.org > mv-production-puppet.build.mozilla.org > talos-r3-fed64-043.build.mozilla.org > maemo-n810-71.mv.mozilla.com > talos-r3-fed64-053.build.mozilla.org > talos-r3-fed64-002.build.mozilla.org > qm-laddon01.build.mozilla.org were all set to use the new dns proxy except: talos-r3-fed-ref.build.mozilla.org talos-r3-fed-ref64.build.mozilla.org talos-r3-fed64-043.build.mozilla.org <-- this one still thinks its a ref image talos-r3-fed64-053.build.mozilla.org <-- looks like it needs a reboot and I couldn't log into: qm-laddon01.build.mozilla.org and it looks like the reverse dns is busted on: talos-master02.build.mozilla.com - needs s/.com/.org/
Assignee | ||
Comment 3•14 years ago
|
||
the two broken talos fed64 slaves will be fixed in bug 593033
Assignee | ||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•14 years ago
|
||
fixed talos-master02 reverse dns and shutdown bc-proxy01. Thanks.
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•