In rare cases, a customer needs to make the same change to many existing Host Database entries. Examples include replacing one Technical Contact with a different Technical Contact, or changing all entries which specify one building to specify instead a different building.
While such changes could be made to each entry individually using the standard Host Database Change Entry form via the Web, when the number of entries to be changed in this way is large (for example, 20 or more), it can become burdensome. In such cases, the customer may request that hostmaster make the changes in bulk on behalf of the customer.
To request such a bulk change, send email to email@example.com :
If the entries to be changed are not characterized in such a generic way, but instead should be specified individually, provide a list of the Host Database entry's canonical names (not aliases). Do not provide a list of their presently-assigned IP addresses or presently-registered hardware addresses.
To be authorized to change a Host Database entry, one must already be listed as one of the Technical Contacts for that entry, or be one of the Departmental Contacts associated with the Department Name listed in the entry. (Some OIT technicians are also authorized to make changes for others.)
If you are not someone authorized to change some of the entries, for each such entry, hostmaster will need to contact someone who is authorized to change that entry to see authorization to proceed. This can add considerable delay to the processing.
For example, we can "set the first IP address in the entry (regardless of its value) to be on subnet X (replacing any first IP address already present)," but we cannot "change any IP address in the entry presently on subnet X to subnet Y." A few examples of other changes we cannot perform as bulk changes include "change the second IP address in the entry to be on subnet X," "remove all wireless interfaces," "remove all Ethernet interfaces," "remove all IP addresses," and "remove all Ethernet addresses."