• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Converting to MS DNS

S

shane01

Guest
Hi Guys,

I am currently working with BIND for my Plesk Hosting server. I would like to convert this over to using MS DNS. However, I can't find any information on how to go about this.

How is it done? What are the potential issues associated with it? Has anyone done it successfully? Has any one had any problems doing it?

Also, what structure would it use? We would like it to create a single zone (ie: ".") and then add all the relevant DNS entries under that (ie: "test.com.")... that way we can use our offsite DNS servers to replicate the entire "." zone.

Any information would be helpful.

Shane
 
I think the only way you can convert from Bind to MSDNS is with a migration or restore to a new server with only MSDNS installed.

I've never used Bind on Windows as I prefer MSDNS over it. You create a Master Zone for each domain where all the records are then kept in. (kinda like a folder structure) You can set the server or domain to allow transfers to other secondary servers (you can set this in Plesk or MSDNS).
All of our servers, linux and windows, are set to do transfers to a central Windows DNS server that acts as our secondary namesesrver.
 
Wouldn't that mean manually creating a DNS zone on the secondary for each new primary zone created in Plesk?
 
How do you make sure in a new install that MSDNS is used and not BIND?
 
If MS DNS is installed it will be visible within the Server -> Component Management area.

You would click the heading and within the next page you can switch the radio button to MS DNS, Plesk will recreate the relevant DNS zones and switch to the server running MS DNS.
 
Is one better then the other? I am redoing my plesk server as we speak and i remember last time having a shitload of issues with BIND and would like to avoid them this time.
 
Originally posted by shane01
Wouldn't that mean manually creating a DNS zone on the secondary for each new primary zone created in Plesk?
Click to expand...

Yes, this is a manual process for me, but takes less than 5 mins so I don't mind.
 
You must log in or register to reply here.

Similar threads

G
Issue DNSSEC configuration still gets broken by dnsmng --update – possibly related to PPPM-15337
Replies
1
Views
678
Sebahat.hadzhi
Sebahat.hadzhi
ChristophRo
Bug - DNS service resets to service plan default for all subscriptions on any change to plan
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
nethubonline
Forwarded to devs plesk repair mail fails with "Unable to find row with id 0 in dns_zone table" when DKIM is enabled and no DNS server is installed
Replies
1
Views
966
Sebahat.hadzhi
Sebahat.hadzhi
N
Issue Enabling DNSSec for existing keys -- Workaround for double plesk bug.
Replies
2
Views
476
GCM
G
K
Forwarded to devs SPF record is checked on local zone active while zone is remote
Replies
2
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top