Computing at Cornell Resources for Technical Support Providers

Changes in NUBB, DNSDB Feb. 3

The following message was sent to the net-admin-l and telecoord-l mailing lists on Monday, January 17, 2005

On Feb. 3, the Network Registry (DNSDB) will become the database of record for most network billing information and will update NUBB. CIT is making these changes to comply with Cornell's Policy 5.7, Network Registry, and to create a single "data of record" source.

If you currently have subscriber IDs in NUBB that are not in DNSDB (Network Registry), please be advised that the information in the NUBB subscriber IDs will be deleted on Feb 3. Those people will be unable to access NUBB until they are registered in DNSDB.

If your hosts are currently in both NUBB and DNSDB, please be advised that these changes will occur on Feb. 3:

You can preview the new systems at dnsdb-test.cit.cornell.edu and test.nubb.cornell.edu from Jan. 13 - Feb. 3. We welcome your comments. The new systems will be deployed on Feb. 3 after the Jan. NUBB billing run.

Please read on for specific details on what is changing.

What will be affected for billing and telecommunications coordinators?

  1. You will continue to use NUBB to enter host account numbers, descriptions, and subnet accounts. Or your network administrator (if you have one) can be asked to do that via DNSDB (Network Registry).

  2. You will no longer be able to fill in the NUBB subscriber ID.

  3. Managers who want to see NUBB data will have to be added either as NUBB billing coordinators or as DNSDB network administrators.

  4. The following NUBB fields are affected:
    netadmin
    subscriber ID
    host description
    host account number
    default subnet account number
    See http://www.cit.cornell.edu/computer/support/hostreg/nubbsync.html for details.

What will be different for network administrators?

  1. NUBB network administrators who are not already DNSDB (Network Registry) network administrators will be added automatically. DNSDB will be the database of record for all fields except the NUBB account, description, and subnet account.

  2. You will now be able to use DNSDB to add or update NUBB accounts, descriptions, and subnet accounts. You can disable this feature, if desired, on a subnet by subnet basis by e-mailing hostmaster@cornell.edu.

  3. You will now be able to view the details of any of your hosts' top 100 conversations by clicking a new button on the NUBB netadmin (Subnet page). Please be advised that conversation details are regarded as confidential information and must be treated in accordance with Cornell's Policy 4.12, Data Stewardship and Custodianship.

  4. You can no longer list yourself as the DNSDB machine user or NUBB subscriber ID for a host unless you are the primary user or, if it's a shared device, you are the admninistrator. This is per Cornell's Network Registry policy.

  5. The DNSDB machine user and NUBB subscriber ID fields can no longer be different. In the past, some network administrators did that to protect privacy. However, the Network Registry policy prohibits that practice. Instead, the DNSDB machine user field will only be viewable by network administrators, CIT's Network Operations Center (NOC), and CIT's Security Team. The NUBB subscriber ID field will be viewable by those same groups plus the user.

  6. Managers who want to see NUBB data will have to be added either as NUBB billing coordinators or as DNSDB network administrators.

  7. The following NUBB fields are affected:
    netadmin
    subscriber ID
    host description
    host account number
    default subnet account number
    See http://www.cit.cornell.edu/computer/support/hostreg/nubbsync.html for details.

For more information