DNS

DNS #

AppDat provides DNS registration for all AppDat hosted systems under the root AppDat domain: appdat.jsc.nasa.gov. By convention hosted systems that require DNS routing are setup as follows:

  • For Staging: “https://{project-name}.staging.appdat.jsc.nasa.gov”
  • For Production: “https://{project-name}.appdat.jsc.nasa.gov”

Special cases #

There are often reasons why a specific system or set of systems requires a break from the above convention, this cases are handled on a case by case basis directly with system owners.

Migrating Existing Agency DNS #

Often systems migrating to AppDat have existing DNS entries in the NASA DNS registries. The following process details the actions required for migrating existing agency DNS entries to newly hosted AppDat versions.

  1. Open a new AppDat Support Agency DNS Request launch
  2. Open a new ESD “DNS Service Request” ticket launch
  3. An AppDat SRE will ready a “Merge Request” with updates to the “Ingress” specification of the applicable application.
  4. Once the DNS Change is made by the agency DNS team, readied “Merge Request” then merged and change deployed to production.

Public DNS only #

Currently AppDat utilizes public Lets Encrypt SSL certificates for providing platform wide SSL certification management for all hosted systems. This requires that the LetsEncrypt can verify the correct ownership of the DNS which requires registration with a public DNS registry. If the application you are migrating to AppDat currently only has an internal agency DNS entry, you will have to also submit an “ADD” type DNS Service Request ticket to have it added to the agency’s public DNS registry in addition to the CNAME based modification ticket described step #2 above.