Scott Small on Nostr: UVic was still doing this as late as 2009/2010 when I worked there. Anyone working in ...
UVic was still doing this as late as 2009/2010 when I worked there.
Anyone working in IT had access to a web service called the “NETS Tools”, which let you activate/deactivate Ethernet wall ports for any room on campus (except in the Engineering/CSC buildings, which were on an independent network). When you activated a wall port, you could pick any available IP address (starting with 142.104), and a hostname. The hostname would be a subdomain of the department whose building the wall port was in, rather than of UVic.ca directly.
i.e. I had an office in the HSD building, so I could create <subdomain>.hsd.uvic.ca that would point to one of the wall ports in my office.
The official policy was that the subdomain should be named for the wall port ID (or if none, the room number) - but there was nothing stopping you from picking something completely arbitrary. My office had six ports in it, and I think I named each one after a different type of local tree!
Anyone working in IT had access to a web service called the “NETS Tools”, which let you activate/deactivate Ethernet wall ports for any room on campus (except in the Engineering/CSC buildings, which were on an independent network). When you activated a wall port, you could pick any available IP address (starting with 142.104), and a hostname. The hostname would be a subdomain of the department whose building the wall port was in, rather than of UVic.ca directly.
i.e. I had an office in the HSD building, so I could create <subdomain>.hsd.uvic.ca that would point to one of the wall ports in my office.
The official policy was that the subdomain should be named for the wall port ID (or if none, the room number) - but there was nothing stopping you from picking something completely arbitrary. My office had six ports in it, and I think I named each one after a different type of local tree!