# Wildcard DNS

Wildcard DNS is beneficial for networks that need to dynamically generate subdomains for different servers or purposes, such as `xyz.domain.com`, `cracked.domain.com`, etc., without the need for individual DNS entries for each subdomain. This setup will guide you through the process and ensuring that all subdomains are secured and directed appropriately.<br>

## Step 1: Verify your root domain:

Follow this [step](https://docs.tcpshield.com/panel/panel-configuration#step-4-add-domains) in our documentation to verify your root domain. This step is crucial as it verifies ownership and controls DNS settings, which are needed for proper configuration and protection.

## Step 2: Adding your subdomain:

On your DNS manager (we will be using Cloudflare in this demonstration), add a new CNAME record with this configuration:

* Name: \*
* Target: your protected CNAME target
* Proxy status OFF

<figure><img src="/files/7EkBFh3m8y2VviuMDgQ9" alt=""><figcaption><p>Example of a wildcard subdomai on Cloudflare</p></figcaption></figure>

And that's all you have to do.

{% hint style="info" %}
If your configuration doesn't work immediately, it might be due to DNS [propagation](https://docs.tcpshield.com/miscellaneous/pages/zPcw0psLWpTEYm0nnIGl#id-3.-how-dns-propagation-works).
{% endhint %}

By following the steps outlined above, you can ensure that all subdomains under your domain are protected against DDoS attacks while maintaining flexibility in how you manage your DNS settings.


---

# 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.tcpshield.com/miscellaneous/wildcard-dns.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.