[boeki]

^ so, how'd it go?

[purplespider]

boeki, on 05 August 2011 - 01:45 PM, said:

^ so, how'd it go?

Not a great first experience. I enabled the new "built in" cPanel VPS.NET cluster feature, and then did a "Synchronize DNS Records" action just to make sure everything was in sync, but once it had finished I noticed it had broken lots of my DNS records!

It seemed to append the domain name onto the end of each record. So for example.com I had a perfectly good:

mail	14400	IN	CNAME	example.com.

But it decided to change it to:

mail	14400	IN	CNAME	example.com.example.com.

Which obviously completely broke the record.

It did this for loads of my sites, and even changed:

example.com.	14400	IN	MX	0	aspmx.l.google.com.

Into:

example.com.	14400	IN	MX	0	aspmx.l.google.com.example.com.

So my only option was to restore my named zone files from my rsync backup. I disabled the cluster sync option, and haven't had a chance (or been brave enough) to try it again.

[cPanel Matt]

Quote

Not a great first experience. I enabled the new "built in" cPanel VPS.NET cluster feature, and then did a "Synchronize DNS Records" action just to make sure everything was in sync, but once it had finished I noticed it had broken lots of my DNS records!

I'm sorry to hear you're having trouble, I spent several hours trying to recreate this error in my testing environments and was unable to. If you could either provide steps to reproduce or (ideally) open a ticket w/ some basic info on the problem at https://tickets.cpanel.net/submit/ I'd be very interested in taking a look at this problem and seeing what we can do to resolve it. If you could put "Attn: Matt" in the subject of the ticket, that will ensure that I get it.

[danielb]

May I ask where can I enable the Built-in cPanel module for VPS.NET and what are the advantages of using it instead of VPS.NET's plugin?

Also, do we require to uninstall VPS.NET's plugin?

Thank you very much!.

[mk1200]

Just ran into my first fraudulent order with the WHMCS VPS.Net plugin. The fraudster was able to buy a node and upgrade to 2 nodes. Guess who had to pay for the nodes? All me, love it. Maxmind flagged the orders as fraudulent, but the WHMCS VPS.Net plugin lets the orders roll right through.

Can't believe this hasn't been fixed yet.

 1st_order.gif (40.25K)
Number of downloads: 31
 2nd_order.gif (17.41K)
Number of downloads: 36
 vps_net_nodes.gif (9.75K)
Number of downloads: 31

[Root]

danielb, on 29 August 2011 - 09:48 PM, said:

May I ask where can I enable the Built-in cPanel module for VPS.NET and what are the advantages of using it instead of VPS.NET's plugin?

Also, do we require to uninstall VPS.NET's plugin?

Thank you very much!.

I would disable (or uninstall) the earlier VPS.NET WHM plug-in; after that's completed, you can switch to the built-in, native VPS.NET DNS clustering module using the steps outlined below:

• Access WebHost Manager via the following path: WHM: Main >> Cluster/Remote Access >> Configure Cluster
  
• Under Add a new server to the cluster, use the Type drop-down menu to select VPS.NET.
  
• Click Configure -- this will load the next page for your VPS.NET DNS Remote Configuration.
  
• Input your VPS.NET API username and key.
  
• Select your preferred method for handling NS records.
  
• Select the DNS role, such as either Synchronize Changes or Write-only; (the default DNS role is Standalone, which doesn't synchronize or write DNS changes to the remote DNS server).
  
• Click Submit.

This post has been edited by Root: 16 September 2011 - 06:44 AM

[danielb]

Root, on 16 September 2011 - 06:44 AM, said:

I would disable (or uninstall) the earlier VPS.NET WHM plug-in; after that's completed, you can switch to the built-in, native VPS.NET DNS clustering module using the steps outlined below:

• Access WebHost Manager via the following path: WHM: Main >> Cluster/Remote Access >> Configure Cluster
  
• Under Add a new server to the cluster, use the Type drop-down menu to select VPS.NET.
  
• Click Configure -- this will load the next page for your VPS.NET DNS Remote Configuration.
  
• Input your VPS.NET API username and key.
  
• Select your preferred method for handling NS records.
  
• Select the DNS role, such as either Synchronize Changes or Write-only; (the default DNS role is Standalone, which doesn't synchronize or write DNS changes to the remote DNS server).
  
• Click Submit.

Thank you very much for such a detailed explanation, better than any support reply
May I ask you what are the advantages of using cPanel's cluster plugin instead of VPS.NET's one?

Thank you.

[danielb]

I've completed the steps, but all records created have this input: "localhost A 127.0.0.1" in VPS.NET DNS (Domain) manager when I update or create a record in WHM

[Root]

danielb, on 17 September 2011 - 01:04 AM, said:

I've completed the steps, but all records created have this input: "localhost A 127.0.0.1" in VPS.NET DNS (Domain) manager when I update or create a record in WHM

The localhost record should only exist once in each zone; if each record is appearing that way I would believe something may not be working quite right.

What's your cPanel&WHM version number (displayed in the top-right of WHM, or as seen in '/usr/local/cpanel/version')?
Via CLI/SSH:

# cat /usr/local/cpanel/version

I would consider submitting a (free) support request directly to cPanel with "Attn: Matt" in the subject, (like cPanelMatt suggested a few posts earlier in this thread).