Frequently Asked Questions

« Previous
My Android device is running out of storage. What is using it?
Next »
How do I find the serial number on macOS?

windows ubuntu macos xibo network zenworks android storage

146. What is the point with the zone

See also: What is Rrsync (restricted rsync)? How do I access PCFS storage over rsync?
See also: How do I access PCFS over SMB using smbclient?
See also: How do I mount my home directory or shared storage at HNAS?

The initiative for the domain was taken in 2015-05 by BMC in order to get an aliases to file server shares with unique names.

For example, the file server share is named with the TLA-SHARENAME, like INV-Common. Then the CNAME will be or pointing to the current file server where the share is located.

The reasoning behind this is the following:

  1. Get a unique name in DNS to each file server share. This will faciliate migration of file server shares to new servers.

    We (the university) had a lot of troubles with migration from the old NetApp file server to the new HNAS file servers. This zone with an extra level of abstraction in front of the real file server names was intended as a proactive way of eliminating one part of the problem in preparation for the next file server migration. It also makes it easier for those users users (research groups or department) that wish to or have to move their share from one storage system to another.

  2. Make it work for all operating systems. There is a function in the Microsoft Active Directory (with a similar goal) called the DFS that put all file server shares in a single name space. This however do not work all the time in all operating systems, like non-AD connected Windows-clients, macOS (not all of the time), Linux (it depends a lot on the configuration it do not work for example in Ubuntu out of the box).
  3. Network agnostic Get access to the servers even from other networks where needed when the USER-AD ( is not accessible due to using split DNS and access restrictions, like UAS, SLU, UPPMAX, HPC-centers in Sweden and maybe mobile data. It is also not a requirement to use the university resolvers, it should work even if the local resolvers are down.


This entry was last modified 2017-12-07


This documentation is covered by GNU Free Documentation License. 11 ms