ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:
Server 71.74.*.* reports that it will do recursive lookups. [test] Server 71.74.*.* reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers.
---------------------------
i install APF and RUN to Server i don`t know my APF is Coorect or no!
root@server [/]# apf -t APF Status Log: Feb 01 01:57:54 server apf(11506): firewall initalized Feb 01 01:57:54 server apf(11565): {glob} default (ingress) input drop Feb 01 01:57:54 server apf(11565): {glob} default (egress) output drop
DigBuddy is an email deliverability and MX monitoring service. Customers sign up and input all of the email addresses at their domain and our monitoring system will check to make sure that these email addresses are able to receive email by logging in and attempting to send an email without actually sending one. It also checks the DNS, SPF records and a bunch of other stuff so our clients can be assured that they are able to send and receive email to a variety of networks without issue.
We need to set up monitoring servers on a number of networks across a number of countries that can be used to send and receive email. Basically all we need is a VPS with 512mb of ram and 19 IP's. It also must have an unblocked SMTP port 25 and the IP's must have a neutral or better senderbase score. We also need to make sure that the IP's have proper forward and reverse DNS entries.
I am in the process of setting up my server and have come to the stage where I am uploading my actual website scripts and files. I am a little confused however as to what permissions and file/directory ownership my website files should be set to.
My web root is set to 755 (rwx/r-x/r-x) with Owner as root, and Group as root. All files within the web root are set to 744 (rwx/r--/r--) with the owner and group the same as the web root. The permissions set allow php scripts to function but I am not sure if the group should be set to root on all these files, is this correct?
My site users have no ftp access if that makes any difference to ownership.
I use WHM/cPanel. Heres what i get from a dns report
MXDNS:
PassMX records for domain sphexa.comYour 1 MX records are:
0 sphexa.com ip=66.197.145.5 FailedMailserver connection test HELO, MAIL FROM, RCPT TO, QUITConnect to mailserver sphexa.com FAILED (could be greylisting)
PassPublic IPs testMX records are public IPs conform RFC 1918 FailedMailserver greetingThe server should have an A record which points to the mailserver for the hostname which is presented in the greeting
sphexa.com
PassOpen relay test for sphexa.comsphexa.com FAILED (VERY GOOD)
InfoReverse DNS entries for MX records5.145.197.66.in-addr.arpa -> music.bandlabel.com.
I'm working on a young site that will be changing its focus and its domain name to reflect the new focus. What is the correct way to change the domain name? In the past, I've simply created a new site in WHM/cPanel under the new domain name and copied the old site (and database) over, which was a great deal of work. Is there another way to do it that is less time consuming - without having to copy files? Are you not able to just change the domain name setting in WHM without having to copy the entire site over to a new directory on the server?
LCMlinux ~> uname -a Linux LCMlinux 3.2.29-smp #2 SMP Mon Sep 17 13:16:43 CDT 2012 i686 LCMlinux ~> httpd -v Server version: Apache/2.4.3 (Unix) Server built: Aug 23 2012 11:07:26 LCMlinux ~>
We are using this both for the Trac issue-tracking application and for a small, simple internal mirror web site. Trac is working perfectly; the web site works if exact URLs are provided (as in <a href=...>
I have two problems regarding Mailman Mailing Lists.
1) The Mailman Interface is usually located under lists.domain.tld/mailman (I changed the config from /cgi-bin/mailman/ to just /mailman/), but it seems the apache confs for this subdomain are not applied – I only see the servers default page when visiting this URL. domain.tld/mailman works, though. It would be great if lists.domain.tld/mailman would actually work and domain.tld/mailman wouldn't work.
How do I change/repair the configurations properly? I've installed the newest MU and already to reinstall mailman.
2) I get an Internal Server Error when visiting the domain.tld/mailman Interface. Reason is mod_suexec, which I need to disable for domain.tld/mailman, but where and how? All the vhost configurations are created automatically.
I could imagine this is related to my first problem and the mod_suexec thing is properly configured in the lists-subdomain config.
A Wordpress install on one of my domains was compromised a few months ago, and there was a 4-hour window in which the site contained an iframe injection that lead to a malware site.
The problem was corrected, and Google stopped flagging the site as malicious within a few hours after the fix. However, every once in a while I still hear of people having problems accessing the site, all of them I think from within large corporate networks.
Are there a few common list providers that these corporate networks are likely to be subscribing to? Is there a way I can submit the domain for reevaluation? If not, how long would you think a domain would have to be clean in order to repair its reputation on these lists?
I have a client who will be pointing their domain to my reseller server. I have already setup the account on my server and made the appropriate DNS changes with their domain registrar - so the domain should be pointing to my server soon.
However, what is the normal procedure for migrating email accounts, without loosing mail?
When should they change email account settings?
Should they use their current settings until they get an error, or no longer receive mail, then change settings to match my server?
How can I make it so only the system (scheduled task or the server itself) can access to the file to execute it. I tried placing CHMOD 700 to the PHP file but everyone is still able to access to it and executive it.
TEST 1: Without <FilesMatch> directive, the headers are set to all requested content as it should. This includes content served from apache server and content from a separate application server.
TEST 2: If I use the above configuration example, I can see that static content comes with correct headers only
I'm migrating sites from Plesk 9 to Plesk 12 using the migration manager. Since the migration manager doesn't migrate backups, are the backups compatible between Plesk 9 and Plesk 12? If so, is there an easy way to copy the backups in the correct directory structure since we are forced to use clients in plesk 12 and it changes the directory structure of the backups folders.
