Changes between Version 4 and Version 5 of allocate_new_ip_block


Ignore:
Timestamp:
May 14, 2013, 9:17:11 AM (8 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • allocate_new_ip_block

    v4 v5  
    66 * Add the block to puppet - in the manifests/globals.pp file.
    77 * Run: `freepuppet-helper GenerateIPsFromRoutes` to add the new IPs to puppet. git add and git commit the new files created.
     8 * We run a caching DNS server on every physical host. These hosts only respond to requests from IP addresses in our network. After committing the new IP addresses to our puppet repository, you have to push those changes to the physical hosts you want to respond to DNS requests. Eventually, they will get pushed to all hosts with the next tag is signed. You can manually push to any hosts that you need to work immediately.
    89 * Add IP addresses to our DNS servers (for reverse lookups).
    9    * For Bandcon: Login to {{{mayfirst@hay.mayfirst.org}}}. Edit ~/bin/create-reverse-ip to modify the first two variables to reflect the IP range you are adding.
    10    * For HE: edit viewsic.mayfirst.org:/etc/tinydns/root/special-records and then type make. Keep track of #7166 for changes.
     10  * For Bandcon: Login to {{{mayfirst@hay.mayfirst.org}}}. Edit ~/bin/create-reverse-ip to modify the first two variables to reflect the IP range you are adding.
     11  * For HE:
     12   * Until #7166 is resolved, use the Bandcon method.
     13   * After #7166 is resolved, edit viewsic.mayfirst.org:/etc/tinydns/root/authority to add the new block and then type make