Skip to content

GridHPC Domain

In order to provide consistent and easy to remember servicepoints for the Vulcan cluster, we decided to internally resolve the TLD.gridhpc. This was done for the following reasons:

  • Internal services can be accessed via a consistent domain name, e.g. https://<service>.gridhpc.
  • Some self hosted applications generate unexpected behavior without a valid domain name, e.g. GitLab.
  • We can validate SSL certificates for internal services.
  • Communication between Vulcan nodes can be done via a consistent domain name, e.g. https://<node>.gridhpc.

  • We can map domains to MAC addresses of the nodes, which allows us to use the same domain name for a node even if its IP address changes.In order to provide consistent and easy to remember servicepoints for the Vulcan cluster, we decided to internally resolve the TLD.gridhpc. This was done for the following reasons:

  • Internal services can be accessed via a consistent domain name, e.g. https://<service>.gridhpc.

  • Some self hosted applications generate unexpected behavior without a valid domain name, e.g. GitLab.
  • We can validate SSL certificates for internal services.
  • Communication between Vulcan nodes can be done via a consistent domain name, e.g. https://<node>.gridhpc.
  • We can map domains to MAC addresses of the nodes, which allows us to use the same domain name for a node even if its IP address changes.