M
madguy24
Guest
Plesk's release note says 9.5.1 support 5.2 version of MS DNS (http://download1.parallels.com/Plesk/Panel9.5/Windows/9.5.0/plesk-9.5.0-for-windows.htm) . May I know whether 9.5.1 supports, MS DNS 6.0 version, or do we need to think about downgrading the version (not sure whether it is possible even).
We have the same issue reported, but unfortunately, no error logs when switching the DNS. This is the second server we are seeing where BIND DNS stop working all on a sudden without anything in the event logs. First one was a 2003 server and this one is 2008. Switching to MS DNS on 2003 did fix the issue, but switching in 2008 is not working.
Ran,
defpackagemng.exe --fix --type=dnsserver without any errors
dnsmng.exe REMOVE * also worked without any errors
dnsmng.exe UPDATE * also worked without any errors
But switching doesn't happen, even though the zones are created. No message in Plesk's log or in DNS server's log. What exactly happens as per the logs are..
1. MS DNS is started - Informational logs
2. It converts the forward zones - Information logs
3. It converts the reverse zones - Informational logs
4. MS DNS is stopped - Informational logs
Why did it stop ?
We are welcomed with the message -
================
Set default component failed: defpackagemng failed: Execute dnsmng.exe REMOVE * failed:
Execute dnsmng.exe UPDATE * failed:
================
Also, we tried to configure the default from cmd prompt
"%plesk_bin%\defpackagemng.exe" --set --type=dnsserver --default=msdns
and that also resulted in
===================
Execute dnsmng.exe REMOVE * failed
Execute dnsmng.exe UPDATE * failed
===================
And if we run dnsmng.exe REMOVE * and dnsmng.exe UPDATE * independently, it works.
Unfortunately, these error messages doesn't give a clue. I work for a support firm, SupportSages.com and is trying to help a client who is facing the issue. Few of our engineers did work on this issue and unfortunately the upstream provider of our client doesn't seem to be big enough to get official support from Plesk or refused to open a ticket on behalf of us. We continue to work on this, but still would like a confirmation.
Can we get a confirmation from the team that, Plesk 9.5.1 support 5.2 and above (including 6.0.6002.18005) and not just =5.2 version.
We have the same issue reported, but unfortunately, no error logs when switching the DNS. This is the second server we are seeing where BIND DNS stop working all on a sudden without anything in the event logs. First one was a 2003 server and this one is 2008. Switching to MS DNS on 2003 did fix the issue, but switching in 2008 is not working.
Ran,
defpackagemng.exe --fix --type=dnsserver without any errors
dnsmng.exe REMOVE * also worked without any errors
dnsmng.exe UPDATE * also worked without any errors
But switching doesn't happen, even though the zones are created. No message in Plesk's log or in DNS server's log. What exactly happens as per the logs are..
1. MS DNS is started - Informational logs
2. It converts the forward zones - Information logs
3. It converts the reverse zones - Informational logs
4. MS DNS is stopped - Informational logs
Why did it stop ?
We are welcomed with the message -
================
Set default component failed: defpackagemng failed: Execute dnsmng.exe REMOVE * failed:
Execute dnsmng.exe UPDATE * failed:
================
Also, we tried to configure the default from cmd prompt
"%plesk_bin%\defpackagemng.exe" --set --type=dnsserver --default=msdns
and that also resulted in
===================
Execute dnsmng.exe REMOVE * failed
Execute dnsmng.exe UPDATE * failed
===================
And if we run dnsmng.exe REMOVE * and dnsmng.exe UPDATE * independently, it works.
Unfortunately, these error messages doesn't give a clue. I work for a support firm, SupportSages.com and is trying to help a client who is facing the issue. Few of our engineers did work on this issue and unfortunately the upstream provider of our client doesn't seem to be big enough to get official support from Plesk or refused to open a ticket on behalf of us. We continue to work on this, but still would like a confirmation.
Can we get a confirmation from the team that, Plesk 9.5.1 support 5.2 and above (including 6.0.6002.18005) and not just =5.2 version.