Retirement of Legacy OIT DNS Service (Domain Name Service)

Legacy OIT DNS Service (Domain Name Service) will be retired on June 11 2019 as announced by OIT.

The service previously was named OIT DNS Service. It transitioned to legacy status on November 29 2018.

Any devices still using this legacy service need to change to use its replacement service described in KB0011511.

Most devices which used Legacy OIT DNS Service (Domain Name Service) have already switched to using the replacement service, so will not be affected by the retirement of the legacy service. Some devices are still using the legacy servicel; they will need to take action to switch to use the replacement service before the legacy DNS service is retired.

Potentially affected devices fall into several categories:

Devices connected via wireless services provided by OIT:

These devices are supposed to use DHCP to obtain their IP configuration. That DHCP service tells these devices which DNS servers they should use, among other things.

These devices will not be affected by the retirement of the legacy DNS service. (The DNS servers supporting wireless services provided by OIT are not the legacy DNS servers.)

Devices connected via network wingnet:

These devices are supposed to use DHCP to obtain IP configuration. That DHCP service tells these devices which DNS servers they should use, among other things.

These devices will not be affected by the retirement of the legacy DNS service. (The DNS servers supporting network wingnet are not the legacy DNS servers.)

Devices attached to other networks where OIT provides DHCP or BootP service:

These devices may be using DHCP, BootP, or manual configuration to obtain their IP configuration:

If the device obtains its IP configuration via DHCP or BootP:

If the device reboots any time on or after November 28 2018, the device will be unaffected by the retirement of the DNS service.

In the past, the device's DHCP or BootP software learned of the legacy DNS service. But once the device boots on or after November 28 2018, its DHCP or BootP software automatically learns of the replacement DNS service. At that time, the device stops using the legacy DNS service, so the device will not be affected by the retirement of the legacy DNS service.

If the device has not rebooted since before November 28 2018, the customer should reboot the device so it automatically learns of the new DNS servers.

If the device obtains its IP configuration via manual configuration (not via DHCP or BootP):

These devices need to be manually reconfigured to use the replacement service. Someone responsible for such devices should reconfigure the devices before the legacy DNS service is retired.

See KB0011511.

Simply rebooting these devices will not cause them to automatically learn of the new DNS service.

If these devices remain configured to use the legacy DNS service after the legacy DNS service is retired, they will find themselves unable to use DNS after that time.

Devices attached to networks where OIT does not provide DHCP or BootP service:

Circumstances for these devices vary. For example:

• If the network is one that isn't able to use DNS services provided by OIT in the first place, the device will be unaffected by the retirement of the legacy OIT DNS service. (This is common, for example, for unrouted networks, unable to commnicate with any other networks.)

• If the network is one that obtains DNS service provided by some other department/group. the device won't be directly affected by the retirement of the legacy OIT DNS service. (The department/group operating the DNS service may need to reconfigure the DNS service they operate.)

• If the network is one relies on a DHCP or BootP service operated by other department/group, and the network is able to use DNS service provided by OIT, consult the department or individual operating that DHCP or BootP service for instructions as to whether any action is needed.