Hostlelo nameservers:find the right values and change them safely

Where to find your current nameservers

The correct nameservers come from the service details in your current Hostlelo account or from the support team. Infrastructure and account assignments can change. This guide deliberately avoids publishing a fixed nameserver pair that might be wrong for your service.

Nameservers tell the internet which provider is authoritative for your domain’s DNS zone. They do not automatically move your website files or mailbox data. Plan those migrations separately, and make the new destination ready before changing the delegation.

Before you change anything

Sign in to your domain registrar and current DNS provider. Export the zone or write down every record, including A, AAAA, CNAME, MX, TXT, and CAA. Identify services that rely on TXT verification and review SPF, DKIM, and DMARC with your email provider.

Check whether DNSSEC is enabled. A DS record at the registrar that does not match the destination provider can make the domain fail validation. Coordinate the change according to both providers’ instructions rather than assuming it will correct itself.

When a coordinated signed migration is unavailable, follow the provider’s process to remove the old DS record and wait for its TTL to expire before changing nameservers. Keep the old DNS zone working during the wait. After the new delegation is stable, enable DNSSEC at the destination and publish the new DS record. This method has a temporary unsigned period; consult the linked DNSSEC guide if continuous validation is required.

A practical change checklist

1. Obtain the exact assigned nameservers from your active hosting service.
2. Create and verify the complete DNS zone at the new provider.
3. Back up the website and confirm the destination serves the domain.
4. At the registrar, open the domain’s nameserver or DNS-management section.
5. Replace the existing delegation with the assigned values and save.
6. Verify the delegation, website records, email records, and DNSSEC state.
7. Keep the old service available while cached answers expire.

Registrars use different labels and interfaces. The setting might be called Nameservers, Custom DNS, or Change DNS Servers. Updating an NS record inside an unrelated zone does not necessarily change the domain’s delegation at the registrar.

What to expect during the transition

Different networks may show different results for a while. Recursive resolvers can retain old answers until their TTL expires, and delegation records have their own caching behaviour. Do not interpret every temporary difference as a failed change.

Track the authoritative response first, then compare public recursive resolvers. If the destination is missing a record, fix that record. If the delegation is incorrect, correct it at the registrar. Waiting only helps when the authoritative configuration is already right.

Common problems and their causes

• Website works, email fails: inspect MX and authentication records in the new zone.
• Some visitors reach the old server: compare cached answers and check for a stale AAAA record.
• The domain fails only with validating resolvers: review DNSSEC and the registrar’s DS record.
• A certificate error appears: issue a valid certificate for the hostname at the destination.
• A default hosting page appears: confirm that the destination server is configured for your domain.

Once the transition is stable, keep a copy of the final zone and document who manages it. For a first-time domain connection, start with our DNS basics guide; for cached answers, read the propagation troubleshooting guide.