Closed
Bug 870340
Opened 11 years ago
Closed 11 years ago
new DNS zones
Categories
(Infrastructure & Operations :: Infrastructure: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: bhourigan)
References
Details
The servo project needs a few new DNS zones, and I'm not sure what the proper way to do this is at this point (inventory, edit files, issues with the DNSSEC signing stuff) or how the forward records should be split out hierarchically in the directory structure, so I'm going to ask you guys to set this one up. :} NETBLOCK SUBDOMAIN 10.26.80.0/23 build.servo.releng.scl3.mozilla.com There are also two AWS zones, which I'm pretty sure should be done through inventory (and bhearsum is looking into that and will ping uberj with questions if he has any). 10.134.80.0/23 build.servo.releng.use1.mozilla.com 10.134.82.0/23 srv.servo.releng.use1.mozilla.com
Reporter | ||
Comment 1•11 years ago
|
||
Oh, we will also need DHCP support for 10.26.80.0/23 in inventory. It's releng VLAN 280 in scl3.
Assignee | ||
Comment 2•11 years ago
|
||
I've created dnsconfig/mozilla.com/scl3/releng/servo where you can add records for SCL3. I've created thw two use1 zones in inventory: build.servo.releng.use1.mozilla.com https://inventory.mozilla.org/en-US/mozdns/domain/390/ srv.servo.releng.use1.mozilla.com https://inventory.mozilla.org/en-US/mozdns/domain/391/
Assignee | ||
Comment 3•11 years ago
|
||
DHCP scope scl3-releng-vlan280 created. thanks :bhearsum for adding the reverse zones
Assignee: server-ops-infra → bhourigan
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: Infrastructure → Infrastructure: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•