We are migrating domain DNS management from our legacy autoDNS platform to our new system, KeyDNS. If your domain uses iwantmyname's DNS service, this article explains what changes, whether it affects you, and what to do if you use a third-party or secondary nameserver setup.
Who this applies to
This applies to you if you received an email titled "Important: Nameserver update for [DOMAIN]" or a follow-up reminder. You've received this because our review found that your domain currently has nameservers configured that fall outside our standard iwantmyname/KeyDNS set — for example, Cloudflare, AWS Route53, or a hosting provider's nameservers, either alongside or instead of ours.
What is changing
On the migration date stated in your email, any domain still pointed at our DNS service will have its nameservers updated at both the DNS zone level and the domain registry level to our new standard KeyDNS nameservers:
dns1.iwantmyname.comdns2.iwantmyname.comdns3.iwantmyname.com
Any additional or third-party nameservers currently on the domain will not be carried across to KeyDNS. Only the three nameservers above will remain after migration.
Why this matters
There are generally two reasons a domain ends up with mixed/non-standard nameservers:
- Leftover or stale configuration — you (or a previous admin) partially moved DNS elsewhere in the past, and old entries were never fully cleaned up. In this case, the migration is unlikely to cause any disruption, since the extra entries weren't actively relied on.
- Intentional secondary/third-party DNS setup — you deliberately run a secondary DNS provider, split DNS, or a specific hosting configuration alongside ours. In this case, the migration could affect your live services (website, email, subdomains, etc.) if those extra nameservers are still in active use.
If you're not sure which situation applies to your domain, treat it as case 2 and get in touch before your migration date.
What you need to do
| Situation | Action |
|---|---|
| You recognise the extra nameservers and are actively using them | Contact support before your migration date so we can review your setup and agree the best approach before any change is made. |
| You don't recognise the extra nameservers, or believe they're no longer needed | No action needed — the migration will proceed and clean these up automatically. |
| You're unsure | Contact support — we're happy to review your configuration with you at no cost. |
What happens if I do nothing
If you don't respond and you fall into the "stale configuration" group, nothing changes for you operationally your domain will simply be tidied up to point solely at KeyDNS. If you fall into the "actively using third-party DNS" group and take no action, any services relying on the removed nameservers may stop resolving correctly after the migration date. This is why we strongly recommend reaching out if you have any doubt.
Frequently Asked Questions
Q: Will this change my domain's registration, ownership, or renewal date? A: No. This only affects DNS/nameserver delegation, not registration or ownership.
Q: Will my email stop working? A: Only if your email (MX records or similar) depends on the non-standard nameservers being removed. If email is managed entirely through our DNS zone already, it won't be affected. If unsure, contact support before your migration date.
Q: I use a secondary DNS provider on purpose — can I keep it? A: In many cases, yes, depending on your setup. Contact support before the migration date so we can review and configure this correctly rather than having it dropped automatically.
Q: What if my migration date has already passed? A: Contact support with your domain name and we'll review the current nameserver configuration with you and help restore any required third-party entries.
Q: How do I know if this applies to my domain? A: You will only have received the notification email if our review flagged your specific domain. If you haven't received an email, no action is required.