| | 1 | = Local network = |
| | 2 | |
| | 3 | == IP range == |
| | 4 | |
| | 5 | Our cabinet now has a local network: 10.9.67.0/24 |
| | 6 | |
| | 7 | Why such a random range? I don't want to accidentally conflict with other ranges people may encounter. If you try to access an IP in our range from a machine not in our cabinet, I would like it to consitently fail. |
| | 8 | |
| | 9 | And, because I want everything to happen for a reason, I picked this range because it's the date Che was killed (October 9, 1967). Best date I could find without spending more than 15 minutes looking... |
| | 10 | |
| | 11 | You can assign IPs to servers in this range [wiki:how-to/servers/add_ip_allocation the same way you assign all IPs]. I've assigned all physical servers and a handful of other servers, but more work is needed to cover all servers. |
| | 12 | |
| | 13 | == Local domain == |
| | 14 | |
| | 15 | I've also registered the domain mayfirst.cx specifically to be a local domain name. The .cx top level domain was chosen for no reason other than mayfirst.cx being available. |
| | 16 | |
| | 17 | We now have a local authoritative DNS server running on tubman.mayfirst.org which listens on 10.9.67.2. |
| | 18 | |
| | 19 | And, all of our caching DNS servers (which run on all physical hosts) have a "stub-zone" configured so that any requests made for mayfirst.cx is directed at tubman. |
| | 20 | |
| | 21 | Since all of our servers use our own caching DNS servers, it means any request made on any of our servers should be resolved via tubman and should result in an IP address in our 10.9.67.0/24 range. |
| | 22 | |
| | 23 | == Configuring Locally DNS == |
| | 24 | |
| | 25 | If you are an admin, then "Local DNS" shows up in the control panel at the Member level. All hosts are configured via the May First/People Link Membership. |
