Whose Idea was this?

[GordonH]

All our boxes updated from cpanel and now have this box ticked in tweak settings:

"When adding a new domain, if the domain is already registered, ignore the configured nameservers, and set the NS line to the authoritative (registered) ones."

We did not ask for this to be done.

Can anyone guess what the problem might be with that box being ticked?

Answer:
If someone adds a new domain to the server that is currently hosted elsewhere, the current name servers get added to the SOA records on our server.
Then once the customer has changed the name servers to our ones, the domain still points to their old host.

This is a total nightmare.
It seems to have been like this on most servers for several days.
We didn't change it so cpanel must have done it during an update.
Fortunately we use our own DNS for a lot of the servers but the reseller ones are now badly misconfigured on many domains and it will take a week to go through them and sort them out.

Why would anyone think that having that box ticked would be a good thing?
Why would anyone want to auto update that on all the servers?

[Rafaelfpviana]

I agree with you, I had many problems because of this pointless feature.

[kernow]

Ditto ....
And if we must have it then the default should be Off.

[brianoz]

The feature makes some sense if it looks at the toplevel delegated nameservers for the domain and uses those when setting the domain up. It makes no sense *at all* for it to check for the existing nameservers and save those.

What actually would be useful would be a WARNING if the delegated nameservers are different from the default nameservers. It would also be useful to log or backup the existing nameservers (as in the existing NS records) in case of future problems (sometimes you do need these to verify what DNS records were setup).

[GordonH]

The feature makes some sense if it looks at the toplevel delegated nameservers for the domain and uses those when setting the domain up. It makes no sense *at all* for it to check for the existing nameservers and save those.

What actually would be useful would be a WARNING if the delegated nameservers are different from the default nameservers. It would also be useful to log or backup the existing nameservers (as in the existing NS records) in case of future problems (sometimes you do need these to verify what DNS records were setup).

It makes no sense at all if it means the account will not work without manual intervention to fix the NS records.

[adept2003]

Maybe cPanel can put the script to good use by modifying it so that it flags up accounts that have nameservers that are different to the ones configured in WHM?

[GordonH]

Maybe cPanel can put the script to good use by modifying it so that it flags up accounts that have nameservers that are different to the ones configured in WHM?

Or one that scans the domains on the server and tells you which ones are hosted elsewhere.
I have a script that does that but its not on the servers so I have to pull the list of domains out of /etc/localdomains to run it.

[elevenx]

For some reason I thought that it would keep checking the nameservers and once customer updates them at their registrar it would update to the new server and everything would fall into place.

That would be useful.

[DewKnight]

It's possibly the stupidest option I've ever seen.