Search results

OK, thank you very much! I appreciate pointing me in the direction to get it resolved!

NS1 points to the DirectAdmin server at 168.235.104.53, and NS2 - NS4 point to servers at CloudNS.net. So maybe it's the configuration for the external name servers that's wonky all of a sudden. DirectAdmin only lists two nameservers for the server in their default configuration, right? SOA...

And I have a message into Proalix support, but I believe it's nighttime in Russia.

Need some help to get my server back up. It was failing with a domain having a bad httpd.conf file, so I deleted that domain after trying to rebuild apache and failing. Rebooted the server. Now what I'm getting are these errors for every domain: Sep 10 07:47:41 host1.hostkabob.com named[2018]...

Thanks so much! That was it. How I missed that I'll never know, as it is checked on all the other domains that are receiving mail normally. And thanks to all the rest of you for your suggestions. I really appreciate it.

I have the A records and MX record set to that (see image). Is there another place I should look (within DirectAdmin or something)?

I did see that McAfee has the domain website blacklisted, so I'm trying to clear that up. But the email is not blocked by anyone according to mxtoolbox.com

Thanks. It looks good, just 1kb or 1000MB used. Also checked the owner of the mail folders which are the username:mail, which is consistent with the other accounts on the server which are working.

Thanks for the response! It gives me a couple of additional items to check. It's odd because none of the incoming emails are allowed in, but other domains on the same server are not having the problem. As far as I can tell all the MX records, A records, etc. are in place, and spam filtering is...

Domain: acumenconsultingcompany.com Test Email address: [email protected] I can send email from this domain to my Gmail address. However, Gmail cannot send email TO any email address at this domain. The error message I get is: The DNS has an MX record for the domain, and...

I recreated the SPF txt record and tested to make sure email does come through. I'll watch to see if it was a malformed SPF perhaps.

Thanks, I do have an SPF record and DKIM signing, but I'll check the format and make sure its good.

I occasionally get a spam email from one of my accounts. This image is from the user's DA email usage. Note the IP addresses that are shown as the originator: How can I configure it so that email only originates from my server, and not these other IP addresses?

Thank you very much! Flush privileges did the trick and I can once again create databases.

Thanks for the recommendation! I appreciate the help. I think I have a more serious problem than the usual with this message. Output of those commands: I verified that mysqld was running in Direct Admin. Then tried to create a database again in the user account and get the same message:

I'm getting this error message when trying to create a new MySQL database in the Direct Admin interface: "Unable to add user xxxxx_xxxxxx. The MySQL server is running with the --skip-grant-tables option so it cannot execute this statement" However, looking in /etc/my.cnf I don't see the line...

Thanks for the permissions script. I ran it, but the issue still remains. I think I need to trace through how a user / domain is created manually and then see where I encounter problems.

Another issue has cropped up. I have a new VPS on the same network so I copied over the recent backups (taken last night), but cannot restore them to the new VPS. The error on trying to restore the backup files is "'/backup/user.conf' - cannot open. Permission denied". I'll try an older backup...

That's a good idea. I may try that. I have rebooted the VM to see if it sees any errors on boot. I'm not sure how to run fsck on a KVM instance and not screw something up, so I'll have to do some research on that.

It was installed via a script, and was working fine for a few weeks. Not sure what happened. I did have some issues getting Let's Encrypt working and went through some permissions issues at that time. Looks to me like perms are at -rw-r--r-- with root:root on all of these, but DA can't open...