# Connect a Subdomain to BotPenguin Using Hostinger DNS

### Overview

This guide explains how to connect a **subdomain** (for example, `panel.yourdomain.com`) to your **BotPenguin Agency Panel** using **Hostinger as your DNS provider**.

For subdomains, **only a CNAME record is required**.

***

### Prerequisites

Before you begin, make sure you have:

* A domain purchased on **Hostinger**
* Access to **Hostinger hPanel**
* Access to **BotPenguin Agency Panel**
* **CNAME target value** provided by BotPenguin

📘 **Reference:**\
Hostinger DNS Overview\
<https://support.hostinger.com/en/articles/1583227-how-to-manage-dns-records>

***

### Step 1: Get Subdomain Mapping Details from BotPenguin

1. Log in to the **BotPenguin Agency Panel**
2. Go to:\
   **Settings → White Label / Custom Domain**
3. Copy the **CNAME target domain** provided

📘 **BotPenguin References:**

* Agency Panel Overview\
  <https://botpenguin.com/help/agency-panel>
* Custom Domain Setup\
  <https://botpenguin.com/help/custom-domain>

***

### Step 2: Log in to Hostinger hPanel

1. Open **Hostinger Dashboard**
2. Log in using your credentials
3. Select your domain
4. Click **DNS / Nameservers**
5. Open **DNS Zone Editor**

📘 **Hostinger Reference:**\
How to open DNS Zone Editor\
<https://support.hostinger.com/en/articles/1583226-how-to-open-dns-zone-editor>

***

### Step 3: Add CNAME Record for Subdomain (Required)

#### Example Subdomain

```
panel.yourdomain.com
```

#### Steps

1. Click **Add Record**
2. Select **CNAME**
3. Enter the following details:
   * **Name / Host:** `panel`
   * **Points to / Target:** *(CNAME provided by BotPenguin)*
   * **TTL:** Auto
4. Click **Save**

📘 **Hostinger Reference:**\
How to add a CNAME record\
<https://support.hostinger.com/en/articles/1583304-how-to-add-a-cname-record>

***

### Step 4: (Optional) Add CAA Record for SSL (Recommended)

Adding a CAA record ensures SSL certificates are issued smoothly.

#### Steps

1. Click **Add Record**
2. Select **CAA**
3. Enter:
   * **Host:** `@`
   * **Flag:** `0`
   * **Tag:** `issue`
   * **Value:** `letsencrypt.org`
   * **TTL:** Auto
4. Click **Save**

📘 **Reference:**\
<https://www.cloudflare.com/learning/ssl/what-is-caa/>

***

### Step 5: Wait for DNS Propagation

* DNS changes usually take **5 minutes to 24 hours**
* In rare cases, it may take up to **48 hours**

📘 **Reference:**\
What is DNS propagation?\
<https://support.hostinger.com/en/articles/1583318-what-is-dns-propagation>

***

### Step 6: Verify Subdomain in BotPenguin

1. Return to the **BotPenguin Agency Panel**
2. Navigate to **White Label / Custom Domain**
3. Enter your subdomain (for example, `panel.yourdomain.com`)
4. Click **Verify / Save**

***

### SSL Activation (HTTPS)

* SSL is **automatically enabled** by BotPenguin
* If SSL status shows **Pending**:
  * Wait for DNS propagation
  * Retry verification later

📘 **Reference:**\
What is SSL?\
<https://www.cloudflare.com/learning/ssl/what-is-ssl/>

***

### Example Configuration

**Subdomain Mapping**

```
panel.mycompany.com → BotPenguin Agency Panel
```

***

### Important Notes

* ✅ Use **only CNAME** for subdomains
* ❌ Do **not add an A record** for the same subdomain
* Use **Auto TTL**
* Do not delete existing unrelated DNS records
* One subdomain can map to **only one Agency Panel**

***

### Completion 🎉

Once verification and SSL are complete, your **BotPenguin Agency Panel** will be accessible securely via your custom subdomain.

#### Need Help?

Please feel free to reach out to us at <mark style="color:$primary;"><support@botpenguin.com></mark>, in case of any questions or concerns.


---

# 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://partners.botpenguin.com/partner-platform-guidelines/connect-a-subdomain-to-botpenguin-using-hostinger-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.