LeaderSetu LeaderSetuWebsite • CRM • JanSampark

CUSTOM DOMAIN HELP

Connect your own domain to your public website

Your domain can stay with GoDaddy, Hostinger, Cloudflare, Namecheap or another provider. LeaderSetu only needs the DNS record required to route the chosen hostname to your customer website.

BEFORE YOU START

Keep ownership of your domain

You do not need to transfer the domain registration to LeaderSetu. You only need access to the DNS settings for the hostname you want to publish, such as www.yourdomain.in. Never share your registrar password with support staff.

01

Add the domain

Open Account → Domain in the customer application and enter the complete hostname you want to connect. Use the exact hostname you plan to publish rather than a shortened label.

02

Copy the DNS values

The customer application shows the DNS information required for that domain. Copy the displayed record type, name and target exactly instead of guessing a value from a generic tutorial.

03

Create the record at your provider

Open the DNS management screen at your current provider and add the record shown by LeaderSetu. Remove or correct only conflicting records for the same hostname; unrelated email or verification records should be left untouched.

04

Wait for DNS verification

DNS changes can become visible quickly, but cached records may take longer to expire. The domain status moves through the platform verification flow after the expected record is visible.

05

Allow SSL activation

After the hostname resolves correctly, HTTPS certificate status can move from pending to active. Keep the required DNS record in place while the website remains published.

COMMON TROUBLESHOOTING

What to check when the old page still appears

Seeing a registrar parking page after a DNS change does not necessarily mean the website deployment failed. Check the DNS path before redeploying application code.

01

Old parking or previous hosting page

Your browser, device, ISP or recursive DNS resolver may still have the previous address cached. Verify that the authoritative DNS record is correct and allow the previous record's cache lifetime to expire.

02

Conflicting records

A hostname should not have incompatible records competing for the same name. Compare the provider's DNS screen with the exact value shown in the customer application before deleting or changing anything.

03

Root domain versus www

yourdomain.in and www.yourdomain.in are separate DNS names. Configure the hostname requested by the platform and use your DNS provider's supported method when you also want the other version to redirect or resolve.

04

DNS works but HTTPS is pending

Domain verification and certificate activation are separate stages. Do not repeatedly change a correct DNS record simply because SSL provisioning has not completed yet.

Need assistance? Use “Request Domain Setup Assistance” in the customer application and share the domain plus provider name. Support should never ask for the password to your GoDaddy, Hostinger, Cloudflare, Namecheap or other registrar account.