Closed
Bug 1502194
Opened 7 years ago
Closed 7 years ago
Please update DNS records for KMS03 in MDC2
Categories
(Infrastructure & Operations :: Infrastructure: Tools, task)
Infrastructure & Operations
Infrastructure: Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: markco, Assigned: rtucker)
Details
Attachments
(1 file)
|
142.77 KB,
image/jpeg
|
Details |
For kms03.ad.db.mdc2.mozilla.com we need an A record pointed to kms03.ad.mozilla.com and the _vlmcs._tcp srv record pointed to kms03.ad.mozilla.com. Currently the _vlmcs._tcp pointed to an old server that was in scl3.
C:\windows\system32>nslookup -type=srv _vlmcs._tcp
Server: infoblox1.private.mdc2.mozilla.com
Address: 10.50.75.120
_vlmcs._tcp.mozilla.com SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = kms1.ad.mozilla.com
This should have the same records set up that kms02.ad.mozilla.com has in mdc1.
This isn't quite correct we do not strictly need the srv record to point to the ad address.
We do need srv records in the sub domains that any of the mdc2 windows clients might use as a native suffix ( wintest, private, mdc2, etc) to point to kms03 either to the ad.db or ad A record.
| Assignee | ||
Comment 2•7 years ago
|
||
Can you please provide the exact records you need created and I'll get them made asap?
| Reporter | ||
Comment 3•7 years ago
|
||
Q: should that then be repeated in MDC1 as well? From what I can tell there is only the ad address record for _vlmcs._tcp ?
Flags: needinfo?(q)
| Reporter | ||
Comment 4•7 years ago
|
||
Could we start with the _vlmcs._tcp srv record for kms03.ad.mozilla.com in MDC2?
| Assignee | ||
Comment 5•7 years ago
|
||
(In reply to Mark Cornmesser [:markco] from comment #4)
> Could we start with the _vlmcs._tcp srv record for kms03.ad.mozilla.com in
> MDC2?
Please get me the exact record you need and I'll make it
| Reporter | ||
Comment 6•7 years ago
|
||
In MDC2:
service._proto.name = _vlmcs._tcp
priority = 0
weight = 0
port = 1688
svr hostname = kms03.ad.mozilla.com
What other info is needed for the record?
| Assignee | ||
Comment 7•7 years ago
|
||
I need the FQDN of the record to be made, here is an example of an entire record where _kerberos._tcp.dc._msdcs.ad.mozilla.com is the FQDN:
_kerberos._tcp.dc._msdcs.ad.mozilla.com. 600 IN SRV 0 100 88 dc11.ad.mozilla.com.
| Assignee | ||
Comment 8•7 years ago
|
||
I dug through some previous entries I've created for Q and my best guess is that you need the following record:
_vlmcs._tcp.mdc2.mozilla.com. 60 IN SRV 0 0 1688 kms03.ad.mozilla.com.
| Assignee | ||
Comment 9•7 years ago
|
||
:markco,
Please confirm the record mentioned in comment #8 is what you need.
Thanks
Flags: needinfo?(mcornmesser)
| Assignee | ||
Comment 11•7 years ago
|
||
dig srv _vlmcs._tcp.mdc2.mozilla.com @10.48.75.120
_vlmcs._tcp.mdc2.mozilla.com. 60 IN SRV 0 0 1688 kms03.ad.mozilla.com
Is this good to go?
Assignee: infra → rtucker
| Reporter | ||
Comment 12•7 years ago
|
||
Yes. ty!
| Assignee | ||
Comment 13•7 years ago
|
||
Awesome!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 14•7 years ago
|
||
Screenshot of test in MDC2.
You need to log in
before you can comment on or make changes to this bug.
Description
•