Problem with "Advanced DNS zone editor"
Discussion in 'Bind/DNS/Nameserver' started by jp.vert, May 5, 2010.
This is my first post as a new cpanel user.
There is an error message when my customers want to use the "Advanced DNS zone editor" : "JSON parse failed." and below "no zone records found".
There is no problem with the "Simple DNS zone editor" and I can also access and edit the DNS zone as root with no problem. I did the named-checkzone and all is OK.
Where do I need to check ? Thank you by advance.
At what point are they receiving the JSON error?
1. Upon accessing the editor?
2. While inputing data in the form?
3. When submitting the form?
If 2 or 3 then could you provide some sample data that triggers the error? Also what is your full cPanel version number?
We have the error when accessing the editor.
" JSON parse failed. Please refresh the page and try again."
When he access the email account. I can confirm that. I will try to restart the services, just in case.
I tried a full reboot of the server with no luck, the errors are still there.
Please open a support request for this issue.
and in my case is happening after you fill out the A record information and click Submit.
Can you provide example data you are using to fill in the fields for the A record? Also, is this happening for all accounts or only one account?
Hi, have tested in two accounts and also in another acocunt in another server, same thing.
So, it's happening with A records or with CNAME records or with both? Just clarifying as initially you'd mentioned A records, while your example is a CNAME.
It is probably going to be easier to submit a ticket to check into it if you have root SSH to the machine. WHM > Support Center > Contact cPanel or I have a link on how to submit a ticket in my signature.
We've been getting JSON errors in multiple locations, including the Advanced DNS Zone Editor, on the single server which we have updated to CURRENT-11.28.5 Our other servers are RELEASE-11.26.20 and have no such errors. These errors have only started with the upgrade to 11.28.x on that server.
█ .:GG: Web Hosting -- The ultimate Web hosting!
We are seeing this error in Current while selecting a domain in the Advanced Zone Editor as well.
When is this going to be fixed. Your recent update broke a lot of things with people running custom themes (users can't add cron jobs, user's can't use the DNS editor, users's can't download MySQL backups). This is ridiculous.
We would really appreciate it if anyone who is experiencing the problem would open a ticket and post the # here. I have personally tried to replicate this on 4 servers and I could not get the JSON failure.
If my license is through cpanelsource.com then I have to submit the ticket through them, is that right?
just in case this help to anyone in my specific case this problem was an rvskin theme problem and not a cpanel one, is working ok on X3 theme.
by clicking "Submit a Support Request without Logging In" or you can do in from WHM under "Support Center" => "Contact cPanel"
If you don't have priority support and have not purchased your license directly, your ticket will be placed in the Complimentary Queue which has a longer wait time (usually 2 hours, but it can take 8+ hours depending on the queue).
I think I figured it out. It was what manokiss said.
My customer had Rvskin enabled also. But I figured this out. It had everything to do with the feature manager.
Even though the "Simple DNS Zone editor" Icon showed up in Rvskin, that feature was not enabled for our "Gold" package. So Rvskin is showing the icon and even the page, but cpanel is saying "Nope, dont think so"
So to fix it, I went in to my feature manager and added the "Simple DNS Zone Editor" to the features.
When I read what Manokiss said, I switched him over to x3 and the icon disappeared for "Simple DNS zone editor" in cpanel. I thought that was odd and went and looked in the feature manager and all features were enabled accept that one. I dont know what I was thinking when I set up those features.
So its working now with Rvskin. I hope this helps point others in the right direction. Maybe its not the fix for everyone but it worked for me. I have only gone as far as adding a CNAME but there was NO errors this time!