# Plan

When you create an[ Infrastructure](/docs/automation-platform/application-focused-interface-duplocloud-architecture/infrastructure.md) in DuploCloud, a Plan is automatically generated. A Plan is a placeholder or a template for configurations. These configurations are consistently applied to all Tenants within the Plan (or Infrastructure). Examples of such configurations include:

* Certificates available to be attached to Load Balancers in the Plan's Tenants
* Machine images
* WAF web ACLs
* Common IAM policies and SG rules to be applied to all resources in the Plan's Tenants
* Unique or shared DNS domain names where applications provisioned in the Plan's Tenants can have a unique DNS name in the domain
* Resource Quota that is enforced in each of the Plan's Tenants
* DB Parameter Groups
* Policies and feature flags applied at the Infrastructure level to the Plan's Tenants

The figure below shows a screenshot of the Plan constructs:

<figure><img src="/files/WdS9QxFCA0H9CnjchQ7U" alt=""><figcaption><p>The <strong>Capabilities</strong> tab for the <strong>NONPROD</strong> Plan in the DuploCloud Portal</p></figcaption></figure>

## DuploCloud Plans and DNS Considerations

When creating DuploCloud Plans and DNS names, consider the following to prevent DNS issues:

* Plans in different portals will delete each other's DNS records, so each portal must use a distinct subdomain for its Plans.
* DuploCloud Plans in the same portal can share a DNS domain without deleting each other's records. DuploCloud-created DNS names will always include the Tenant name, which prevents collisions.
* The recommended practice for most portals is to set all Plans to the same DNS name, including the `default` Plan.
* Ideally, custom subdomains will be set in the Plans before turning on Shell, Monitoring, or Logging. If the DNS is changed later, those services may need to be updated.


---

# Agent Instructions: 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:

```
GET https://docs.duplocloud.com/docs/automation-platform/application-focused-interface-duplocloud-architecture/plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.