> ## Documentation Index
> Fetch the complete documentation index at: https://moengage-user-guide.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Proxy Sub Domains

To bypass ad blockers and ensure consistent data tracking, MoEngage utilizes a DNS delegation process. This involves carving out a specific subdomain of your primary domain and authorizing MoEngage to manage the DNS records for that subdomain. This approach ensures reliable data capturing and campaign delivery by appearing as first-party traffic.

## Recommendations for Choosing a Subdomain

To maximize the effectiveness of this feature and avoid being flagged by ad-blocking lists, follow these recommendations when selecting your subdomain:

* **Avoid Tracking Keywords:** Do not use names like *track*, *ads*, or *moengage*. Many ad blockers use keyword-based filtering.
* **Use Neutral Terms:** Consider using random strings or unrelated dictionary words (e.g., `cn.example.com`, `data.example.com`, or `mx-events.example.com`).
* **Keep it Short:** Aim for a length of 5–8 characters to maintain efficient URL structures.

## The Onboarding Process

Setting up DNS delegation is a collaborative process between your technical team and MoEngage Support.

1. **Select your subdomain:** Choose a subdomain based on the recommendations above (for example, `xyz.example.com`).
2. **Inform MoEngage:** Share the chosen subdomain with your MoEngage account team or [raise a support ticket](/user-guide/contact-support/raise-a-support-ticket-from-the-moengage-login-page).
3. **Receive Name Servers:** The MoEngage SRE team will create a DNS Zone and provide you with a list of Name Server (NS) records.
4. **Update Parent Domain:** Add the provided NS records to your parent domain's DNS configuration. This action delegates control of the subdomain to MoEngage for traffic routing.
5. **Verification:** MoEngage will monitor the delegation status. Once verified, the necessary infrastructure endpoints will be mapped to your custom subdomain.
6. **Configure the SDK:** After successful delegation and verification, update your SDK initialization logic to use the custom proxy domain. Refer to the specific implementation guides below:
   * [Android SDK](https://www.moengage.com/docs/developer-guide/android-sdk/sdk-integration/advanced-or-optional/custom-proxy-domain-android)
   * [iOS SDK](https://www.moengage.com/docs/developer-guide/ios-sdk/sdk-integration/advanced/Custom-Proxy-Domain-iOS)
   * [Web SDK](https://www.moengage.com/docs/developer-guide/web-sdk/web-sdk-integration/advanced-integration/custom-proxy-domain-web)

<Info>
  **Note on Propagation**

  DNS changes can take between 24 to 72 hours to propagate globally. You can verify the status of your NS records using online tools like DNSChecker.
</Info>

## Specific Provider Instructions

Most major DNS providers support subdomain delegation via NS records. Refer to your provider's documentation for specific instructions on "NS Record Management" or "Subdomain Delegation":

* [Cloudflare](https://developers.cloudflare.com/dns/manage-dns-records/how-to/subdomains-outside-cloudflare/)
* [AWS Route53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingDevelopingManagingDNS.html)
* [Akamai](https://techdocs.akamai.com/cloud-computing/docs/ns-records)
* [IBM NS1](https://www.ibm.com/docs/en/ns1-connect?topic=zones-subdelegations-child#subdelegations_child_zones__title__2)