> For the complete documentation index, see [llms.txt](https://bryan-guner.gitbook.io/my-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bryan-guner.gitbook.io/my-docs/lambda-labs/architecture/dns.md).

# DNS

### (DNS-100) Product Domain <a href="#dns-100-product-domain" id="dns-100-product-domain"></a>

Each product will have a single registered domain that will be used for all endpoints in all services and for all projects.

* Domain name registration for products will be handled by Labs Engineering Managers
* Nameservers will be provided by an AWS Route 53 Hosted Zone
* Naming Standard
  * Alphanumeric characters only
  * Use the `dev` TLD only
  * Examples:
    * `bridgestoprosperity.dev`
    * `ecosoap.dev`

Rationale:

* DNS is the root of many network operations and having a consistent naming convention across our products will help manage the complexity.

Alternatives:

* None

Exceptions:

* None

### (DNS-200) Product Subdomains <a href="#dns-200-product-subdomains" id="dns-200-product-subdomains"></a>

Subdomains should be used for various endpoints of a product: e.g. DS API, Web Front-end, etc.

* Naming
  * All lowercase
  * Alphanumeric characters only
  * Web Frontend
    * Use the format: `<team letter>.<product domain>`
      * `c.bridgestoprosperity.dev`
      * `a.ecosoap.dev`
  * Web API
    * Use the format: `<team letter>-api.<product domain>`
      * Examples:
        * `c-api.bridgestoprosperity.dev`
        * `a-api.ecosoap.dev`
  * Data Science API:
    * Use the format: `<team letter>-ds.<product domain>`
      * `c-ds.bridgestoprosperity.dev`
      * `a-ds.ecosoap.dev`

Rationale:

* DNS is the root of many network operations and having a consistent naming convention across our products will help manage the complexity.

Alternatives:

* None

Exceptions:

* None

[<br>](https://docs.labs.lambdaschool.com/standards/platforms-and-services/data-persistence)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bryan-guner.gitbook.io/my-docs/lambda-labs/architecture/dns.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.