[nickn]

Hi All,

Our team has just released a cPanel/WHM Plugin that will allow you to use our free (and fully redundant) DNS system with cPanel with absolutely no additional configuration beyond changing a DNS server!

You can download the plugin here:
http://www.vps.net/p...t-dns-1.2.5.tgz

To install, simply wget that to your server, untar and run "sh install.sh" in the directory.

After this, login to WHM, and go to "VPS.NET DNS" and enter your API key and username, and you're good to go, if you're currently running DNS on the server you may have to change your nameservers, or the IPs of your nameservers but that's it!

"So nick, why switch?"

The VPS.NET DNS system:

- Is Faster (DNS servers in 13 cities, the fastest always responds!)
- More redundant (Cities can go offline without affecting DNS)
- DDoS Protected (Immune to DNS attacks)
- Reduces resources on your server (No longer does your server need to worry about DNS)

There's many other great features coming, so check it out, and if you have any questions, let us know!

[anthonysomerset]

this works pretty darn well :)

[georgetasioulis]

So basically all I have to do after installing the plugin, is change the nameservers at the bottom of WHM -> Server Configuration -> Basic cPanel/WHM Setup to dns1.vps.net & dns2.vps.net and immediately change the nameservers on all domains I'm hosting on cPanel through each domains registrar control panel, correct?

[anthonysomerset]

yes OR

continue to use your branded nameservers, and the just change the glue records for the branded nameservers to point the ip's for dns1.vps.net and dns2.vps.net for a full white label approach :) which is what i am doing

[georgetasioulis]

oh yes that it :D

So that way I don't even have to inform any customers etc. :D

[anthonysomerset]

thats my plan and it almost worked despite one domain refusing to serve correctly in some parts of the world, luckily its only my personal blog domain but open dns seing SERVFAIL is worrying, luckily all my other domains are running fine and i am fairly confident its totally unrelated

PS i have already submitted a ticket about my dns issue (36739)

[brucelet]

If I change my glue records, don't I also have to change the nameserver IP addresses in cPanel? Also, if I want some on my server's DNS server and some on vps.net for multiple redundancy, do I just add two new nameserver records to my registrar? I'm thinking of ns1 and ns2 on my cPanel DNS server and ns3 and ns4 on vps.net.

[brucelet]

Also, what are the IP addresses to use for vps.net DNS in my domain registrar settings? I can't seem to find them anywhere.

[georgetasioulis]

brucelet said:

Also, what are the IP addresses to use for vps.net DNS in my domain registrar settings? I can't seem to find them anywhere.

ping?

C:Userswintech2003>ping dns1.vps.net


Pinging [B]dns1.vps.net [67.228.254.4][/B] with 32 bytes of data:

Reply from 67.228.254.4: bytes=32 time=160ms TTL=241


C:Userswintech2003>ping dns2.vps.net


Pinging [B]dns2.vps.net [67.228.255.5][/B] with 32 bytes of data:

Reply from 67.228.255.5: bytes=32 time=167ms TTL=241

[anthonysomerset]

brucelet said:

If I change my glue records, don't I also have to change the nameserver IP addresses in cPanel? Also, if I want some on my server's DNS server and some on vps.net for multiple redundancy, do I just add two new nameserver records to my registrar? I'm thinking of ns1 and ns2 on my cPanel DNS server and ns3 and ns4 on vps.net.

yes in edit dns zone only

i would reccomend that you make vps.net the ns1 and ns2 and put only ns3 on your server (its pointless to give it 2 bites on nameservers when its the same box - you only do that when it is the only nameserver)

the vps.net dns already has multiple redundancy so would be much better just chucking it all on the softlayer dns via vps.net

[georgetasioulis]

brucelet said:

If I change my glue records, don't I also have to change the nameserver IP addresses in cPanel? Also, if I want some on my server's DNS server and some on vps.net for multiple redundancy, do I just add two new nameserver records to my registrar? I'm thinking of ns1 and ns2 on my cPanel DNS server and ns3 and ns4 on vps.net.

If you change your glue records to point to the vps.net DNS servers IPs then you don't need to change the nameservers under basic settings in WHM since they'll be pointing to the vps.net DNS servers anyway.
Regarding you second question, I'd rather not mess with bot vps.net DNS servers AND my own setup. I think it's too much. Redundancy IS the reason to change to vps.net's DNS server system, since it's spread across 13 cities. You will just make management more difficult, when there's no reason to.

[Waves]

anthonysomerset said:

yes OR

continue to use your branded nameservers, and the just change the glue records for the branded nameservers to point the ip's for dns1.vps.net and dns2.vps.net for a full white label approach :) which is what i am doing

Could you share one of your domain names where you have this white-labeled solution working?

TIA

[Waves]

nickn said:

The VPS.NET DNS system:

- Is Faster (DNS servers in 13 cities, the fastest always responds!)
- More redundant (Cities can go offline without affecting DNS)
- DDoS Protected (Immune to DNS attacks)
- Reduces resources on your server (No longer does your server need to worry about DNS)

There's many other great features coming, so check it out, and if you have any questions, let us know!

Which cities are those. Are all of them in US, UK & NL ?

[anthonysomerset]

Waves said:

Could you share one of your domain names where you have this white-labeled solution working?

TIA

i self host my domains on stshosting.co.uk (site WIP) (glue setup)

my other sites mentioned in my sig are hosted on stshosting's nameservers which are glue setup on the vps.net/softlayer setup

in whm, under basic settings my nameservers are set to ns1 and ns2.stshosting.co.uk

in the dns zone for stshosting.co.uk the A records for ns1 and ns2 are set to vps.net's

and then obviously i have the records setup in glue at my domain registrar

NOTE: the reason i am happy publishing my domains/nameservers is because its information that anyone with a brain can easily and freely lookup, with just a single domain and they are posted in my sig all over this forum :lol:

[mrtorrent]

So what happened to the plugin? Getting a 404 on the archive.

[nickn]

mrtorrent said:

So what happened to the plugin? Getting a 404 on the archive.

Had to update the version to resolve the trailing period bug on create/recreate

[nickn]

nickn said:

Had to update the version to resolve the trailing period bug on create/recreate

Just to confirm, everyone should now be running at 1.0.3 for the best possible experience.

We're working on a few other things now, but once we are done with this, we'll go back to the DNS plugin and add an update/version system among other things.

[mrtorrent]

Thank you!

[anthonysomerset]

just a couple of feature requests for next version

display the current version number on the plugin page

auto updater? can do it like CSF, download tgz extract and install

[nickn]

anthonysomerset said:

just a couple of feature requests for next version

display the current version number on the plugin page

auto updater? can do it like CSF, download tgz extract and install

Glad we're on the same page..

"We're working on a few other things now, but once we are done with this, we'll go back to the DNS plugin and add an update/version system among other things. "