# Introduction
You can connect your custom domain to Funnelish as a **main domain** or as a **subdomain**.
But what's the difference between the two? Imagine your domain like a shopping mall with a main entrance:
* The main entrance is the **main domain** (e.g., `example.com`)
* Inside the mall you can find different stores (e.g. a pet store, a clothing store, a beauty store etc). These stores would be like the **subdomains** (e.g., `petstore.example.com`). Each store will its own purpose, but they’re all part of the same mall.
Just like the mall’s main entrance can’t lead to two separate malls at the same time, a main domain can’t point to two completely different IP's at the same time. So if you want to have the main domain for example point to your Shopify Store, you can create a subdomain for Funnelish.
| Differences | Main Domain | Subdomain |
| ---------------------------------------- | -------------------------------------- | ----------------------------------------------------- |
| **Structure example** | example.com | petstore.example.com |
| **How does it show in my DNS settings?** | A RECORD | CNAME RECORD |
| **Points to an IP or url path?** | Points to an IP Address (23.227.38.65) | Points to a Url Path
(shops.myshopify.com)
|
| **What shows under "Name"** | @ | The prefix of the subdomain for example "petstore" |
When you're ready to connect your custom domain to Funnelish, click on your domain provider below to see the step by step guide.
---
# 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.funnelish.com/start/connect-your-domain/introduction.md?ask=
```
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.