Document Managed by Network Operations

NetDB Documentation Navigation

1. Introduction
2. Network Contact Groups
3. Query Operations
4. Hostmaster Functions
   • Single Host Edits
   • Bulk Host Edits
   • XML Operations
5. Custom Access Control Lists
6. Errata

1. Single Host Edits

   
    

   • NetDB contains a series of web interfaces for creating, removing and editting simple DNS entries. Namely:
     • Add A New Host: adds a new host record (and reverse if checked) based on supplied information
     • Delete A Host: deletes a host record assuming the operator has sufficient permissions (reverse remains)
     • Rename A Host: moves a host and updates the appropriate new reverse DNS record
     • Clone Host: creates a new host based on information from an existing host
     • Add an Alias: creates an alias (cname) record to an existing host
     • Add who entry (to be deprecated): adds a 'who entry', a rutgers-specific dns record for staff record-keeping purposes
        
2. Add A New Host

   The 'Add A New Host' dialogue adds a single new host record using user-supplied information for all fields.

   • The 'Add new host' dialogue consists of 2 screens. The first needs the following information
     • Hostname: (will check for availability and return an error if the hostname is in use)
     • Domain Name: (rutgers.edu in 99% of cases)
     • NCG: (the NCG you'd like the host to belong to)
        

     
      

   The second screen finalizes host detail:

   • Owner Contact is optional, as are notes
   • TTL (unless you plan on making a service-impacting host move within the near future, this should be left at 86400 seconds)
   • Views dictate where the host will be visible (inside for inside the university, outside for out, both are selected by default)
   • The Address field is where the host's desired IP address should go - clicking *'include reverse'*will create a reverse record where possible
     • There are no restraint checks on the A record besides a dotted quad sanity check (can include external IPs)
     • Reverses can only be created if the reverse does not currently exist
   • The Mail Exchanger Preference Value should be zero in the case of all hosts with only one MX record
   • The Mail Exchanger field should contain a full-qualified domain name (trailing period included - example: rci.rutgers.edu.)
     • Adding additional MX values must be done via the XML interface
   • The RP Email field needs a full-qualified domain name, just replace the '@' sign in your email address with a dot
     • example: help@nbcs.rutgers.edu would become help.nbcs.rutgers.edu.
   • The RP Who field requires a fully qualified 'who' record
     • If you do not have a who record, you may create one from the main hostmaster page
     • You may also simply choose enter your NCG name (no spaces) followed by .who.rutgers.edu (example: chemistry.who.rutgers.edu.)
   • The Text Data fields are optional but have been traditionally used for location data (one line each for campus, building and room number)

   Once all fields are fill out appropriately, click submit to create the host (and reverse if checked). A message will be returned after a few seconds indicating success or failure.

   
    

3. Rename A Host

   'Rename A Host' changes the IP address associated with an existing hostname and updates it's reverse. The dialogue works as follows:

   • Takes an existing hostname (old) and a desired hostname (new) as input
   • deletes the old hostname
   • creates the new hostname using the same information as the old hostname (besides the host record name itself)
   • modifies the reverse pointer to point to the new hostname

   
    

4. Clone Host

   The 'Clone Host' function creates a new host record, cloning the host info of an existing host (besides hostname and IP). The dialogue works as follows:

   • Asks for a 'source host' to clone your new host from
   • Looks up the old hostname after pressing submit

   
    

   • Asks for the new hosts' desired hostname, domain, NCG and IP address
   • Requires you select checkboxes for each of the following:
     • Include forward host: required to actually create host
     • Overwrite Target Forward: if target hostname already exists, overwrites it
     • Include Reverse Host: Creates appropriate reverse
     • Overwrite Target Reverse: if target reverse already exists, overwrite it

   
    

5. Add an Alias (or Cname)

   The 'Add an Alias' dialogue creates a host (alias host) which points to an existing host (the Cname host).

   The following are required by the form:

   • Alias host name and domain name names for the desired new host name
   • Cname host name and domain name: the name of an existing host to which the new host will point
   • The ttl, class type and views are incorrectly labeled as belonging to the Cname. They actually affect the new alias record.

   
    

6. Add a Who Entry

   The 'Add Who Entry' dialogue adds a host into the domain 'who.rutgers.edu'. This host should be either a NetID, NCG name or department/group/academic unit name. The purpose of a who record is to store TXT records detailing information about a user or group. These records are used to contact the person or unit should a host misbehave.

   The dialogue consists of two forms:

   • Form 1 requires only a hostname (the NetID, NCG or unit name discussed above) and an NCG
   • Please do not alter the domain name

   
    

   • Form 2 fleshes out your contact information
   • Pay special attention to the 'views' selection here - selecting outside makes your contact information globally query-able

   

Back to NetDB Navigation