Hi there,
We've encountered similar issues. This happens because WHM 11 now looks at registrar whois data to simplify your settings.
I believe when you say "V" you mean "Check Box". 
If it is checked, you will use the whois data information for the DNS. If it is NOT checked, you use the ones configured in your "Tweak Settings" area of your WHM. This feature works very well, however, an oversight can cause many problem.
Solution:
- Edit your DNS using the "Edit a DNS Zone" for each and every zone.
OR
- If your zones all have the same BAD DNS information, you can use a replace command in CLI (shell) as root, to resolve them.
I strongly recommend, if using the replace option, that you make a backup of ALLLL your zones first. Once this is done, you can issue the following:
Code:
[root@server ~] cd /var/named
[root@server named] replace "BAD DNS INFORMATION" "NEW DNS INFORMATION" -- *.db
[root@server named] service named reload
Keep in mind, when executing this, BAD DNS INFORMATION will be the bad dns host name and the NEW DNS INFORMATION will be the proper name.
Example:
Let's say your BAD DNS was: ns1.baddnsserver.com and ns2.baddnsserver.com
Let's say your GOOD DNS is: ns1.yourhostingcompany.com and ns2.yourhostingcompany.com
You would do:
Code:
[root@server ~] cd /var/named
[root@server named] replace "ns1.baddnsserver.com" "ns1.yourhostingcompany.com" -- *.db
[root@server named] replace "ns2.baddnsserver.com" "ns2.yourhostingcomany.com" -- *.db
[root@server named] service named reload
This would replace both bad DNS with good dns and then the reload would make the changes live.
I know there's a language barrier, based on the post, however, hopefully, I can manage to get through. 
MAKE A BACKUP FIRST... I can never say this enough. 
Have a great day, let me know how things go,