Domain DNS record configuration
Review a DNS zone, plan the records needed to connect a domain to hosting or another service, and check responses after the update. Previous values are retained.
Discuss your projectConnecting a domain to new hosting or creating a subdomain can affect email and other working services. Siteman first identifies existing records and dependencies, then applies the agreed DNS changes. We work with businesses in Baku and Azerbaijan; the technical scope follows the domain setup rather than its location.
What is included
- Inventory the current DNS zone and dependent services
- Review A, AAAA, CNAME, MX and TXT records relevant to the task
- Point a domain or subdomain to the required destination
- Prepare nameserver changes where needed
- Retain previous values and check responses after the change
How the work proceeds
We identify where the zone is managed and which services depend on it. The destination provider's requirements are compared with the current records. Once the plan is agreed, we update records and check DNS responses and the selected services. Previous values are retained for recovery.
What we need to start
Share the domain, registrar, DNS provider, current hosting and destination service. Include active email and subdomains, plus the records requested by the new provider. Access arrangements are agreed separately; do not send passwords through the public form.
What determines the price
The scope depends on the number of domains and zones, how clearly the existing records are documented, any nameserver change and the services to be tested. Website file migration, mailbox migration and SSL configuration may be separate work.
Scope and limits
DNS updates do not move website files or create mailboxes. A complete email authentication setup is a separate service. Cache refresh timing depends on previous TTL values and providers. Simultaneous changes across every network and uninterrupted operation are not guaranteed.
Frequently asked questions
When will DNS changes become visible?
Different resolvers cache their answers. Refresh timing depends on the previous TTL and cache state. We check both DNS responses and the required services after updating the records.
Will email keep working when the website is pointed elsewhere?
We first identify the MX and TXT records used by email. A website-only record change may not require altering them. When nameservers change, working records must be prepared in the new zone in advance.
Can a subdomain point to a separate server?
Yes. The record is selected according to the destination service. The server must also accept the hostname, and HTTPS requirements need checking. Server configuration may be a separate scope.
Discuss your DNS task
Send the domain and the service you want to connect. We can establish the current zone, required records and verification steps.