How can we improve WHMCS?

Share, discuss and vote for what you would like to see added to WHMCS

When transferring a domain into WHMCS give option to retain current nameservers



When clients transfer a domain to us, it would be really useful to allow those clients to retain their current nameserver settings.

When a transfer order is placed, the customer is prompted to enter a list of nameserver addresses to use. By default, these boxes are pre-filled with ours. This screen suggests that when the transfer completes, we'll reset the domain's nameservers to whatever the customer fills in here.
This makes sense with a domain registration order but not so much with a transfer. The customer may not have the technical knowledge to fill in their current nameservers here. This may end up causing downtime for the customer if they haven't correctly replicated their DNS records onto our system.
Please provide the radio button options to "retain current nameservers" or "specify name servers below" with provider defaults filled in.

13 Comments

Login to post a comment.

This is a really useful suggestion, especially for avoiding DNS downtime during transfers. I used a free prompt generator to draft my thoughts..Related Links: https://generateprompt.net/ru/ai/ai-prompt-generator
This would be a really useful option, especially for websites where uninterrupted access matters. Keeping the existing nameservers during a transfer could help prevent unexpected DNS issues and downtime. For example, <a href="https://txrhlive.me can depend on a stable domain setup.
This would be a really useful option, especially for websites where uninterrupted access matters. Keeping the existing nameservers during a transfer could help prevent unexpected DNS issues and downtime. For example, <a href="https://txrhlive.me/">Txrhlive" Login</a> can depend on a stable domain setup.
A safer domain transfer setup would leave the current nameservers unchanged unless the user decides otherwise. Rather than switching to the new provider’s nameservers automatically, the transfer form could offer a choice between keeping the existing DNS settings and entering custom nameservers. Custom fields could appear only when that option is chosen. This would help prevent accidental configuration errors while still allowing experienced users to make manual changes. https://dgmeportal.com/
The domain transfer process could be improved by keeping the existing nameservers active unless the user chooses to change them. Instead of replacing them automatically with the new provider’s settings, the page could offer an option to retain the current nameservers or enter custom ones. The custom fields would appear only when selected. This would reduce accidental DNS changes for less experienced users while still giving advanced users full control. https://ipaybyplatema.com/
A better domain transfer process would keep the current nameservers in place by default, helping prevent unexpected DNS issues. Rather than automatically applying the new provider’s nameservers, the transfer page could let users choose between keeping the existing settings or entering custom nameservers. Custom fields would only appear when that option is selected. This approach would make the process safer for beginners while still allowing experienced users to manage DNS settings manually. https://mydollartreecompass.com/
This is a practical suggestion for improving the domain transfer process. The existing nameservers should remain selected by default to reduce the risk of DNS disruption. Instead of automatically inserting the new provider’s nameservers, users could be given two options: “Keep current nameservers (recommended)” or “Use custom nameservers.” Choosing the custom option could then display editable fields. This would help less technical users avoid accidental DNS changes while still giving experienced users full control. https://mytxrhlive.net/
This is a clear feature request. The key issue is that a domain transfer should generally preserve the customer's existing DNS configuration unless they explicitly choose otherwise. https://nextemployeeportal.online/
During domain transfer, retain the current nameservers by default (recommended) and provide an optional "Specify custom nameservers" choice to prevent accidental DNS downtime while still allowing advanced users to make changes. https://fmc4me.cloud/
This is a very valid improvement suggestion because during a domain transfer the current nameservers should ideally be preserved by default to avoid accidental DNS downtime; instead of pre-filling provider nameservers, the flow should offer a clear choice with a radio button such as “retain current nameservers (recommended)” selected by default and an optional “specify custom nameservers” option that reveals editable fields, ensuring less technical users don’t unintentionally misconfigure DNS while still giving advanced users full control when needed. https://www.fmc4me.com.co
Retaining current nameservers during a domain transfer would prevent unnecessary downtime for the web properties linked to my https://atlantaindustrialcleaning.com/ network.
The challenge with this request is that not every domain registrar offers the option to initiate a transfer and retain the current nameservers in their Domain Transfer APIs. On a quick look, at least 3 of our most popular registrars do not have this. It might be possible in some cases to obtain the existing nameservers on the software side, but that's not guaranteed to always work or be available either.
This request might be better directed to the domain registrars themselves.
Thanks for the idea. Everyone needs this option.