Domain name architecture

Domain name registration

HeartAI is registered as a second-level domain with the following second-level domain name:

Domain name Description
heartai.net HeartAI second-level domain name

Global name server implementation

The HeartAI global name servers are hosted with Cloudflare DNS. The following name servers are active:

Global name server Name server host Description
Cloudflare DNS angela.ns.cloudflare.com HeartAI global domain name server
Cloudflate DNS stirling.ns.cloudflare.com HeartAI global domain name server

HeartAI DNS records are managed through Cloudflare DNS and HeartAI global fully qualified domain names (FQDN) are resolvable by requesting name resolution to the above name servers.

The following table shows some examples of globally resolvable HeartAI FQDNs:

Example global FQDN Description Networks resolvable from
www.heartai.net HeartAI website hosted by GitHub Pages. Globally across the public internet.
postman.heartai.net HeartAI implementation of Postman. Globally across the public internet.

Private name server implementation

In addition to global domain name server functionality, HeartAI also implements private network domain name resolution. This occurs at two primary levels of the HeartAI networking stack:

Private name server Name server host Description
Azure Private DNS 168.63.129.16 Private DNS functionality implemented with Azure Private DNS. Provides domain name resolution from within the HeartAI Azure environment. Does not expose IP addresses to the public internet.
OpenShift SDN DNS dns-default.openshift-dns.svc.cluster.local Private DNS functionality implemented with Red Hat OpenShift. Provides domain name resolution from within the HeartAI OpenShift software-defined network (SDN). As the HeartAI instance of Red Hat OpenShift is provided by Microsoft Azure Red Hat OpenShift and exists within corresponding Azure Private DNS zones, private OpenShift SDN DNS name resolution typically occurs as a sub-tree of the Azure Private DNS.

Similarly to global name resolution, private FQDNs are resolvable from within networks that have access to the corresponding private name servers that resolve those FQDNs. Unlike global name resolution, private name servers may also provide authoritative DNS records for resolvable FQDNs that are not globally a sub-domain of heartai.net. For example. the sub-domains svc.cluster.local and example.subdomain are resolvable FQDNs that are authoritatively resolvable from within their corresponding private DNS zones. This approach is often used in combination with the OpenShift and Kubernetes DNS capabilities to provide location transparent name resolution for the virtual IP addresses that exist within these environments.

The following table shows some examples of privately resolvable HeartAI FQDNs:

Example private FQDN Description Networks resolvable from
sah.heartai.net HeartAI Azure Private DNS zone. Corresponding Azure Private DNS zone and OpenShift DNS zones.
sah-heartai-kv-prod.vault.azure.net HeartAI Azure Key Vault Private DNS Zone Corresponding Azure Private DNS zone and OpenShift DNS zones.
api.aro.sah.heartai.net HeartAI Red Hat OpenShift control plane API. Corresponding Azure Private DNS zone and OpenShift DNS zones.
*.apps.aro.sah.heartai.net HeartAI Red Hat OpenShift endpoint routes. Corresponding Azure Private DNS zone and OpenShift DNS zones.
hello.prod.apps.aro.sah.heartai.net HeartAI hello world production environment endpoint route. Corresponding Azure Private DNS zone and OpenShift DNS zones.
heartai-hello-world.heartai-hello-world-prod.svc.cluster.local HeartAI hello world production environment endpoint service. Corresponding OpenShift DNS zones.
heartai-hello-world HeartAI hello world production environment endpoint service. Corresponding OpenShift DNS zones only from within the heartai-hello-world-prod OpenShift namespace.

Cloudflare implementation

The HeartAI global name servers are hosted with Cloudflare DNS. For the components of HeartAI that are hosted on the public internet (this website and the Postman API reference), all traffic is proxied through Cloudflare as an edge network.

The following image shows an overview of analytics collected over a one-week period for connections that are proxied through Cloudflare:

heartai-cloudflare-all-pages-analytics.png