• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Finally

S

sieb@

Guest
Finally, real forums! First post! :D

I have a suggestion, use the real Bind config files so I can make it work in a DMZ, or give the option to make bind use port 53.
 
Dug up from google:

BIND 8.1 will *not* use port 53 for UDP queries by default, thus the
responses are probably blocked by your firewall. You can get the old
behavior with

options {
query-source address * port 53;
};

This options is missing in the config with 6.5 though, actually, most of the config is missing. I haven't tried adding it yet to see if it works or not.
 
Don't install the Windows DNS

Here's just a tip.

When installing your Windows box, Don't install the Windows DNS system.
If you do, Plesk will install perfectly.
However, your DNS system will not work as it should. Because Plesk installs BIND and does not warn you for the Windows DNS already been installed.

To correct this problem: just uninstall the Windows DNS and BIND will perfectly take over everything.

So my suggestion: Plesk installer should detect the running Windows DNS system and shut it down.
 
Good tip. But thats just why I was stumbling around because there is only a simple statement saying you should install on a "clean" system. Excuse me?!... Now what does that mean? To the developer it could be one thing and to the end user another.

This is what I'd like to see. A clear A-Z of what a clean system represents. Example being... "Install ABC .... do not install XYZ" Which ports are necessary for operation. I know I know its like spoon feeding a baby but thats where I'm at and so are a lot of others who wish to delegate authority to somone with even less experience. I'll power up the server for another stab at this because its been off now since I gave up.
 
Back
Top