Skip navigation



Customization of Host Registration Service


The host registration process may be customized on a per network and/or per organization basis. This is accomplished by using hostreg templates which contain custom fields. A host registration template is just a NetDB node template which adheres to a specific naming convention. It contains four custom fields which dictate the host registration behavior.

Each network that opts into the system, will have to create at least one network template. All hostreg network templates are named hostreg-<network name>. The network name must match the name of the network record. For example, the network named polya-net, has the template named "hostreg-polya-net". Additionally, administrators may choose to create an organizational hostreg template. Those templates are named hostreg-<organization-id>-org. For example and organization template for "Information Technology Services" would be named "hostreg-CAAA-org"

Your organization code can be found at University Administration Organizational Hierarchy
The University Budget Office manages the organizational hierarchy. The hierarchy defines the parent-child relationships for group data on campus. An organization code is sometimes referred to an administrative id.

Multiple host registration templates are allowed. Names should take the form hostreg-*name-<1...n->net or hostreg-*name-<1...n->orgid

Opting into Self Host Registration

  • Contact your Network Consultant and ask that your network record be modified. You and your Network specialist will decide which private ip address range to use. Your network record will be modified to include address space from the following private networks:
    10.12.* --- Dorms only

  • In addition the following DHCP options may be enabled:

  • The LNA should use the node template "hostreg-netname" to create their custom hostreg template.

  • The LNA may use the node template "hostreg-orgid" to create an optional hostreg organizational template.

Host Registration Templates


IP Address Policy

If the user is registering via wired interface,

Interface Static IP DHCP Roam
1 Yes Yes Yes
2 No Yes Yes
..n No Yes Yes

(interface 1 is the wired nic)
If the user is registering via the wireless interface:

Interface Static IP DHCP Roam
1 No Yes Yes
2 No Yes Yes
..n No Yes Yes

Custom Fields

The following table describes the four custom fields along with the string values allowed. Modifying these values will override hostreg service default values. Multiple values should be comma separated. Typos in the custom fields will invalidate the custom field. An LNA may choose to leave all custom fields empty. In which case than the column labled "Default" is implemented.
Key Default Possible Values Definition
duration (No expiration set) time-to-expire=N Set expiration field to date + N months
-9999 means no expiration
node (Name field not editable) name=<yes | no>,
Allow users to set their computer name
Once registration is complete, send users to this url.
policy user-admin=no,
static-ip=(as described IP table above),
user-admin=<yes | no>,
proxy-reg=<yes | no>,
static-ip=<all |none| default>,
roam=<all | none | default>,
guest-reg=<yes | no | default>
Allow user to be designated as admin
Allow users to proxy register for other users
Use this option to override the default IP Policy. "None" means no static IP address are assigned.
Use this option to override the default Roaming Policy. "None" means no roaming options.
Allow guest registration on this network ( not implemented )
security bigfix=no,
bigfix=<yes | no>,
antivirus=<yes | no>,
ask-prop=<yes | no>,
ask-data=<yes | no>
Require users to download bigfix
Require users to download antivirus software
Ask user if the computer is owned by Stanford
Ask user if the data is restricted data.

Last modified Tuesday, 09 Jun 2006 01:38:01 PM

Stanford University Home Page