DNSreport for laposte.net
Generated by www.DNSreport.com at 23:34:04 GMT on 30 Jul 2007.
| 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:ns2.laposte.net. [83.145.100.45] [TTL=172800] [FR][These were obtained from g.gtld-servers.net] | |
| 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. | |
| PASS | Glue at parent nameservers | OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names. | |
| 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:ns3.laposte.net. [80.118.33.250] [TTL=300]
|
| PASS | Open DNS servers | OK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be 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). | |
| PASS | Number of nameservers | OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7. | |
| PASS | Lame nameservers | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | |
| PASS | Missing (stealth) nameservers | OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers. | |
| PASS | Missing nameservers 2 | OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers. | |
| PASS | No CNAMEs for domain | OK. There are no CNAMEs for laposte.net. 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. | |
| PASS | Nameservers on separate class C's | OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. 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. | |
| WARN | Single Point of Failure | WARNING: Although you have at least 2 NS records, they may both point to the same server (one of our two tests shows them being the same, the other could not complete the test), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2. | |
| INFO | Nameservers versions | [For security reasons, this test is limited to members] | |
| PASS | Stealth NS record leakage | Your DNS servers do not leak any stealth NS records (if any) in non-NS requests. |
| SOA | INFO | SOA record | Your SOA record [TTL=300] is:Primary nameserver: ns4.laposte.net.
|
| PASS | NS agreement on SOA serial # | OK.
All your nameservers agree that your SOA serial number is 2007072700.
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 DNSreport 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: ns4.laposte.net.. 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: postmaster@laposte.net. (techie note: we have changed the initial '.' to an '@' for display purposes). | |
| PASS | SOA Serial Number | OK. Your SOA serial number is: 2007072700. 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 27 Jul 2007 (and was revision #0). This number must be incremented every time you make a DNS change. | |
| PASS | SOA REFRESH value | OK. Your SOA REFRESH interval is : 21600 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 : 3600 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: 3600 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. |
| MX | INFO | MX Record | Your 3 MX records are:10 smtp1.laposte.net. [TTL=300] IP=81.255.54.11 [TTL=300] [FR] |
| 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). | |
| PASS | Multiple MX records | OK. You have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you. | |
| 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. | |
| FAIL | Reverse DNS entries for MX records | ERROR:
The IP of one or more of your mail server(s) have no reverse DNS (PTR)
entries/* (if you see "Timeout" below, it may mean that your DNS
servers did not respond fast enough)*/. 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. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff
site if you recently changed your reverse DNS entry (it contacts your
servers in real time; the reverse DNS lookups in the DNS report use our
local caching DNS server). The problem MX records are: 238.54.255.81.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)] 239.54.255.81.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)] |
| PASS | Connect to mail servers | OK: I was able to connect to all of your mailservers. | |
| WARN | Mail server host name in greeting | WARNING:
One or more of your mailservers is claiming to be a host other than
what it really is (the SMTP greeting should be a 3-digit code, followed
by a space or a dash, then the host name). If your mailserver sends out
E-mail using this domain in its EHLO or HELO, your E-mail might get
blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821
4.3.1). Note that the hostname given in the SMTP greeting should have
an A record pointing back to the same server. Note that this one test
may use a cached DNS record.smtp1.laposte.net claims to be host smtp.laposte.net [but that
host is at 81.255.54.237 (may be cached), not 81.255.54.11].
<br />smtp2.laposte.net claims to be host smtp.laposte.net [but
that host is at 81.255.54.237 (may be cached), not 81.255.54.238].
<br />smtp3.laposte.net claims to be host smtp.laposte.net [but
that host is at 81.255.54.9 (may be cached), not 81.255.54.239].
<br /> | |
| 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@laposte.net (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@laposte.net. | |
| PASS | Acceptance of domain literals | OK: All of your mailservers accept mail in the domain literal format (user@[81.255.54.11]). | |
| FAIL | Open relay test | WARNING:
One or more of your mailservers appears to be an open relay. If so,
this means that you are allowing spammers to freely use the mailserver
to send out spam! It is possible that your mailserver accepts all
E-mail and later bounces it, or accepts the relay attempt and then
deletes the E-mail, but this is not common.WARNING: smtp1.laposte.net appears to be an open relay: 250 RCPT
TO:<Not.abuse.see.www.DNSreport.com.from.IP.82.67.59.175@DNSreport.com>
OK
<br />WARNING: smtp2.laposte.net appears to be an open relay: 250
RCPT
TO:<Not.abuse.see.www.DNSreport.com.from.IP.82.67.59.175@DNSreport.com>
OK
<br />WARNING: smtp3.laposte.net appears to be an open relay: 250
RCPT
TO:<Not.abuse.see.www.DNSreport.com.from.IP.82.67.59.175@DNSreport.com>
OK
<br /> | |
| 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.laposte.net A record is:www.laposte.net. CNAME www.lpn.fr. [TTL=300] |
| 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. | |
| WARN | CNAME Lookup | WARNING. Your web site (www.laposte.net) has a CNAME record pointing to www.lpn.fr.. That by itself is confusing, but acceptable. However, the CNAME record in this case causes an extra DNS lookup, which will slightly delay visitors to your website, and use extra bandwidth. | |
| INFO | Domain A Lookup | Your laposte.net A record is:laposte.net. A 195.154.98.97 [TTL=300] |
|
Legend:
|
