Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > Installation/Configuration

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #11  
Old 18th May 2007, 11:55
vassilis3 vassilis3 is offline
Junior Member
 
Join Date: May 2007
Posts: 9
Thanks: 0
Thanked 1 Time in 1 Post
Default

[QUOTE=edge]small note that if you use the ISPconfig Portscanner they always show open!

Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:

ns1.grikservers.com. [91.xxx.xxx.150 (NO GLUE)] [*U]
ns2.grikservers.com. [91.xxx.xxx.150 (NO GLUE)] [*U]
[These were obtained from grdns-us.ics.forth.gr]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
WARN Glue at parent nameservers WARNING. The parent servers (I checked with grdns-us.ics.forth.gr.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.
NS INFO NS records at your nameservers Your NS records at your nameservers are:

vasilis13.ath.cx.
ns1.grikservers.com. [91.xxx.xxx.150] [TTL=86400]
FAIL Open DNS servers 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 91.xxx.xxx.150 reports that it will do recursive lookups. [test] Server 91.xxx.xxx.150 reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers.
PASS Mismatched glue OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
PASS All nameservers report identical NS records OK. The NS records at all your nameservers are identical.
PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
FAIL Number of nameservers ERROR: You have 2 nameservers, but both are on the same IP! This is not a valid setup. You are required to have at least 2 nameservers, per RFC 1035 section 2.2.

PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
FAIL Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.

vasilis13.ath.cx.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.grikservers.com.
PASS No CNAMEs for domain OK. There are no CNAMEs for promos.com. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
WARN Nameservers on separate class C's WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
PASS TCP Allowed OK. All your DNS servers allow TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems.
FAIL Single Point of Failure ERROR: Although you have at least 2 NS records, they both point to the same server, resulting in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.

INFO Nameservers versions Your nameservers have the following versions:

91.xxx.xxx.150: "9.3.4"
91.xxx.xxx.150: "9.3.4"

FAIL Stealth NS record leakage Your DNS servers leak stealth information in non-NS requests:

Stealth nameservers are leaked [vasilis13.ath.cx.]!

This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.
SOA INFO SOA record Your SOA record [TTL=86400] is:

Primary nameserver: vasilis13.ath.cx.
Hostmaster E-mail address: admin.promos.com.
Serial #: 2007051704
Refresh: 28800
Retry: 7200
Expire: 604800
Default TTL: 86400
PASS NS agriment on SOA serial # OK. All your nameservers agri that your SOA serial number is 2007051704. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS Report only checks the NS records listed at the parent servers (not any stealth servers).
WARN SOA MNAME Check WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: vasilis13.ath.cx.. However, that server is not listed at the parent servers as one of your NS records! This is legal, but you should be sure that you know what you are doing.
PASS SOA RNAME Check OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: admin@promos.com. (techie note: we have changed the initial '.' to an '@' for display purposes).
PASS SOA Serial Number OK. Your SOA serial number is: 2007051704. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. So this indicates that your DNS was last updated on 17 May 2007 (and was revision #4). This number must be incremented every time you make a DNS change.
PASS SOA REFRESH value OK. Your SOA REFRESH interval is : 28800 seconds. This seems normal (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.
PASS SOA RETRY value OK. Your SOA RETRY interval is : 7200 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
PASS SOA EXPIRE value OK. Your SOA EXPIRE time: 604800 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
PASS SOA MINIMUM TTL value OK. Your SOA MINIMUM TTL is: 86400 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
continue...
Reply With Quote
Sponsored Links
  #12  
Old 18th May 2007, 11:56
vassilis3 vassilis3 is offline
Junior Member
 
Join Date: May 2007
Posts: 9
Thanks: 0
Thanked 1 Time in 1 Post
Default

MX INFO MX Record Your 1 MX record is:

10 srv.grikservers.com. [TTL=86400] IP=91.xxx.xxx.150 [TTL=86400] [*U]
PASS Low port test OK. Our local DNS server that uses a low port number can get your MX record. Some DNS servers are behind firewalls that block low port numbers. This does not guarantee that your DNS server does not block low ports (this specific lookup must be cached), but is a good indication that it does not.
PASS Invalid characters OK. All of your MX records appear to use valid hostnames, without any invalid characters.
PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).

PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
INFO Multiple MX records NOTE: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you. In the past, mailservers would usually re-try E-mail for up to 48 hours. But many now only re-try for a couple of hours. If your primary mailserver is very reliable (or can be fixed quickly if it goes down), having just one mailserver may be acceptable.
PASS Differing MX-A records OK. I did not detect differing IPs for your MX records (this would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records).
PASS Duplicate MX records OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.

PASS Reverse DNS entries for MX records OK. The IPs of all of your mail server(s) have reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. Note that this information is cached, so if you changed it recently, it will not be reflected here (see the www.DNSstuff.com Reverse DNS Tool for the current data). The reverse DNS entries are:

150.206.132.91.in-addr.arpa cust-206-150.on2.ontelecoms.gr. [TTL=10768]

Mail PASS Connect to mail servers OK: I was able to connect to all of your mailservers.
PASS Mail server host name in griting OK: All of your mailservers have their host name in the griting:

srv.grikservers.com:
220 srv.grikservers.com ESMTP Postfix (Debian/GNU)
PASS Acceptance of NULL <> sender OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts).
PASS Acceptance of postmaster address OK: All of your mailservers accept mail to postmaster@promos.com (as required by RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1).

PASS Acceptance of abuse address OK: All of your mailservers accept mail to abuse@promos.com.
INFO Acceptance of domain literals WARNING: One or more of your mailservers does not accept mail in the domain literal format (user@[0.0.0.0]). Mailservers are technically required RFC1123 5.2.17 to accept mail to domain literals for any of its IP addresses. Not accepting domain literals can make it more difficult to test your mailserver, and can prevent you from receiving E-mail from people reporting problems with your mailserver. However, it is unlikely that any problems will occur if the domain literals are not accepted (mailservers at many common large domains have this problem).

srv.grikservers.com's postmaster@[91.xxx.xxx.150] response:
>>> RCPT TO:<postmaster@[91.xxx.xxx.150]>
<<< 554 5.7.1 <postmaster@[91.xxx.xxx.150]>: Relay access denied
PASS Open relay test OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.

srv.grikservers.com OK: 554 5.7.1 <Not.abuse.see.www.DNSreport.com.from.IP.91.xxx.xx x.150@DNSreport.com>: Relay access denied
WARN SPF record Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).
WWW INFO WWW Record Your www.promos.com A record is:

www.promos.com. A 91.xxx.xxx.150 [TTL=86400] [*U]
PASS All WWW IPs public OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
PASS CNAME Lookup OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for www.promos.com, which is good.
INFO Domain A Lookup Your promos.com A record is:

promos.com. A 91.xxx.xxx.150 [TTL=86400]
Reply With Quote
  #13  
Old 18th May 2007, 17:19
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,735 Times in 2,571 Posts
Default

Quote:
Originally Posted by vassilis3
May 17 20:17:40 server1 postfix/smtp[9908]: warning: no MX host for fragemporium.net has a valid address record
The MX for fragemporium.net doesn't have an A record:

Code:
dig mx fragemporium.net

; <<>> DiG 9.3.4 <<>> mx fragemporium.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20639
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;fragemporium.net.              IN      MX

;; ANSWER SECTION:
fragemporium.net.       3600    IN      MX      10 mail200.hoo--yah.com.

;; Query time: 209 msec
;; SERVER: 145.253.2.75#53(145.253.2.75)
;; WHEN: Fri May 18 19:18:28 2007
;; MSG SIZE  rcvd: 70
As you see, mail200.hoo--yah.com doesn't exist:

Code:
dig mail200.hoo--yah.com

; <<>> DiG 9.3.4 <<>> mail200.hoo--yah.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62127
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail200.hoo--yah.com.          IN      A

;; AUTHORITY SECTION:
hoo--yah.com.           3600    IN      SOA     dns1.bigapple-isp.net. noc.ns1.bigapple-isp.net. 2004070920 1800 900 604800 3600

;; Query time: 210 msec
;; SERVER: 145.253.2.75#53(145.253.2.75)
;; WHEN: Fri May 18 19:18:37 2007
;; MSG SIZE  rcvd: 103
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #14  
Old 18th May 2007, 17:41
vassilis3 vassilis3 is offline
Junior Member
 
Join Date: May 2007
Posts: 9
Thanks: 0
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by falko
The MX for fragemporium.net doesn't have an A record:

Code:
dig mx fragemporium.net

; <<>> DiG 9.3.4 <<>> mx fragemporium.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20639
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;fragemporium.net.              IN      MX

;; ANSWER SECTION:
fragemporium.net.       3600    IN      MX      10 mail200.hoo--yah.com.

;; Query time: 209 msec
;; SERVER: 145.253.2.75#53(145.253.2.75)
;; WHEN: Fri May 18 19:18:28 2007
;; MSG SIZE  rcvd: 70
As you see, mail200.hoo--yah.com doesn't exist:

Code:
dig mail200.hoo--yah.com

; <<>> DiG 9.3.4 <<>> mail200.hoo--yah.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62127
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail200.hoo--yah.com.          IN      A

;; AUTHORITY SECTION:
hoo--yah.com.           3600    IN      SOA     dns1.bigapple-isp.net. noc.ns1.bigapple-isp.net. 2004070920 1800 900 604800 3600

;; Query time: 210 msec
;; SERVER: 145.253.2.75#53(145.253.2.75)
;; WHEN: Fri May 18 19:18:37 2007
;; MSG SIZE  rcvd: 103

!!!!!!!!!
what do you mean?
this mail address isn't mine!!!!
Reply With Quote
  #15  
Old 18th May 2007, 19:57
vassilis3 vassilis3 is offline
Junior Member
 
Join Date: May 2007
Posts: 9
Thanks: 0
Thanked 1 Time in 1 Post
Default

never I send email to this address.
is it possible to be from spam?
Reply With Quote
  #16  
Old 19th May 2007, 14:34
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,735 Times in 2,571 Posts
 
Default

Quote:
Originally Posted by vassilis3
is it possible to be from spam?
Yes, that's possible. Please make sure your mail server isn't an open relay.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Sendmai can send mails but unable to receive mails satimis Server Operation 10 20th February 2007 17:10
HotSaNIC domino Tips/Tricks/Mods 23 6th November 2006 05:19
Howto suggestion suse PhP ver 4 + Ver 5 wwparrish Suggest HOWTO 11 7th August 2006 13:29
I can't receive emails but send tom Installation/Configuration 21 13th April 2006 23:40
Unable to receive emails?!!! nandhu HOWTO-Related Questions 7 23rd October 2005 23:49


All times are GMT +2. The time now is 07:44.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.