Make every record intentional
DNS management for websites, mail, and services
Plan authoritative records, safer changes, and validation for domains connected to HostGanga hosting or other internet services.
- Record-by-record guidance
- Controlled DNS changes
- Mail and verification planning
DNS is the map users and systems follow
A small DNS mistake can interrupt a website, mail delivery, or certificate validation. Good management starts with knowing which provider is authoritative, documenting every destination, and understanding how record type and time-to-live affect a change.
HostGanga supports domain and hosting workflows, while the exact DNS interface and supported record options may depend on the domain or service. Check your domain in the live tool, and contact the team for complex migration requirements.
Core record planning
Use A, AAAA, CNAME, MX, TXT, and other supported records for their intended purpose.
Safer migrations
Lower TTL in advance where appropriate, stage destinations, then verify from independent resolvers.
Email alignment
Coordinate MX records with SPF, DKIM, and DMARC information supplied by the mail provider.
Prepare a clean zone
Inventory current records before changing nameservers. Mark which entries serve the apex, www hostname, mail, verification, and third-party tools. Avoid copying stale records without knowing their owners, and never place private credentials in public TXT records.
- Keep an export or screenshot before migration
- Check apex and subdomains separately
- Confirm mail records before switching authority
Verify the result end to end
DNS propagation is distributed rather than an instant global switch. Check authoritative answers, public resolver responses, website TLS, mail routing, and application callbacks. Keep the old destination available until important clients have moved when the migration allows it.
Supported DNS records and management access vary by domain and hosting product.
Frequently asked questions
Can I point a HostGanga domain to another provider?
That depends on the domain controls available to your account. Confirm nameserver or record-management access for the product you use.
What TTL should I choose?
Use a value that balances change speed and query caching. Lower it before a planned migration, then raise it after the destination is stable.
Why does my website work in one place but not another?
Resolvers may still hold older answers. Also check that authoritative nameservers agree and that the destination accepts the requested hostname.