Search results

I'm getting this, 502 Bad Gateway -------------------------------------------------------------------------------- nginx But nginx is not installed on the server. The server also times out when file requests are made, appears to be trying to access nonexistent paths to resources...

Well, number 1. the NS.xxxx.xxx is obnoxious since PLESK decided that I HAVE to use NS instead of allowing me to choose my own Nameserver prefix. Number 2. http://kb.parallels.com/en/113119 didnt work, and I still have to add the records through shell. So, now I have PLESKS mandatory NS...

The problem is my additude. I don't know why I'm so irritated by this but when I updated in Nov, Plesk overwrote my DNS default template and it caused me major headaches. Since then, I've been bitter about the software. I would switch to something else, but haven't had the time or...

Ah, but there is not a missing NS record, Plesk just needs that little extra somethin-somethin to work... This was fine until one of your programers got it in their head to require the extra ns record. ns1.<domain>. NS ns1. nameserver.com. ns1.<domain>. A <xx.xx.xx.xx>...

Thanks Igor... Yeah Igor, that's it. I understand it's a very minor requirement, but I still like to be able to control my own DNS records... You see my gripe? I appreciate your taking the time to respond. I should remember to not make an elephant out of a fly

Bottom Line I lost clients over this, so these issues directly cost me money and damaged my reputation.

thats my gripe... I have the correct A records for ns1.domain.xxx through ns4.domain.xxx pointing to the correct nameservers. I have to create an additional A record for ns.newdomain.xxx to prevent named choking. Now the best part is if i restart the server without the extra A record, it...

sorry, that was a rage vent... Sorry to be semi-incoherent, like I said, my response was a rage post since this and a couple other issues have been irritating me since November. I've gotten pretty good at resolvingthem, but the bitterness grows everytime I have to deal with the problems...

*SOLVED* DNS errors? Issue resolved.

because they dont fu=king care Plesk is an unstable mess and every update adds more problems! For instance everytime i add an account i have to add this through shell: /usr/local/psa/bin/dns --add domainname.com -ns "" -nameserver ns.domainname.com I would have thought this would be fixed...

To be fair... SOLVED PLESK support does respond to support request and the techs do their best to resolve issue. However I don't feel I should have to deal with bind dying everytime i add an account or domain name. Fix is here /usr/local/psa/bin/dns --add <your.domain> -ns "" -nameserver...

Meh... Plesk 10.4.4 kills bind.

Plesk 10.4.4 & bind daily failure <SOLVED> PLESK 10.4.4 has a known issue that has been as far as i can tell, remained unresolved since at least Nov 25th. I have had daily issues with PLESK 10.4.4 due to a bug in the way it handles bind. I'm pretty upset since it's made my life hell for two...