Closed
Bug 1179592
Opened 10 years ago
Closed 8 years ago
Need DNS changes for tableau[2-3].metrics.scl3.mozilla.com
Categories
(Infrastructure & Operations Graveyard :: NetOps, task)
Infrastructure & Operations Graveyard
NetOps
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: michael.thompson, Assigned: dcurado)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/600.7.12 (KHTML, like Gecko) Version/8.0.7 Safari/600.7.12
Expected results:
DNS entries for tableau[2-3].metrics.scl3.mozilla.com are pointing to two addresses each. Need one removed from each.
tableau2.metrics.scl3.mozilla.com
keep: 10.22.27.137
remove: 10.22.25.3
tableau3.metrics.scl3.mozilla.com
keep: 10.22.27.139
remove: 10.22.25.4
| Reporter | ||
Comment 1•10 years ago
|
||
C:\Users\serverops-admin>nslookup tableau2.metrics.scl3.mozilla.com
Server: ns1.private.scl3.mozilla.com
Address: 10.22.75.40
Name: tableau2.metrics.scl3.mozilla.com
Addresses: 10.22.25.3
10.22.27.137
C:\Users\serverops-admin>nslookup tableau3.metrics.scl3.mozilla.com
Server: ns1.private.scl3.mozilla.com
Address: 10.22.75.40
Name: tableau3.metrics.scl3.mozilla.com
Addresses: 10.22.27.139
10.22.25.4
| Assignee | ||
Comment 2•10 years ago
|
||
OK, delete the A records you asked to be deleted.
Let's see if that screws up the inventory -> dhcp configurations.
(hopefully not)
The change should go through within 30 minutes I believe.
I will check up on this and update this bug.
Assignee: network-operations → dcurado
| Assignee | ||
Comment 3•10 years ago
|
||
DNS looks good now:
[dcurado@admin1a.private.scl3 ~]$ host tableau3.metrics.scl3.mozilla.com
tableau3.metrics.scl3.mozilla.com has address 10.22.27.139
[dcurado@admin1a.private.scl3 ~]$ host tableau2.metrics.scl3.mozilla.com
tableau2.metrics.scl3.mozilla.com has address 10.22.27.137
However, you may want reboot those VMs and ensure that DHCP still works correctly.
Or do a DHCP renew ...
| Reporter | ||
Comment 4•10 years ago
|
||
Everything looks great. One thing I'm seeing though is that when the servers are rebooted, upon the first post-boot login, it stalls for 15 minutes, displaying "Please wait for Group Policy client..." Is this in any way related?
| Assignee | ||
Comment 5•10 years ago
|
||
Sounds like the systems need something, and have a 15 minute timeout while they wait for it.
However, I have no idea of what a "Group Policy for the client" in this context.
My best suggestion is to contact the vendor and ask, "what is this?"
Sounds reasonable?
Thanks.
Flags: needinfo?(michael.thompson)
| Reporter | ||
Comment 6•10 years ago
|
||
Yes, that does sound reasonable. In fact, I now think it's actually related to another ticket.
For now, everything looks good from this perspective, so this ticket can be closed.
Thanks for your help.
Flags: needinfo?(michael.thompson)
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•