DNS Expert                              
                  Detailed Report for purenet.com.eg                  

2001-05-11, 21:07, using the analysis setting "Thorough"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           93
Primary name server:     ns1.purenet.com.eg.
Primary mail server:     mail.purenet.com.eg.
Number of records:       17 (2 NS, 1 MX, 12 A, 2 CNAME, 0 PTR,
                         0 Other)

Errors
----------------------------------------------------------------------
o The server "ns3.purenet.com.eg." did not reply
    The server "ns3.purenet.com.eg." did not reply when it was 
    queried for the name "purenet.com.eg.".  This indicates that the
    server is not running, or it is currently unreachable.

o An NS record for "purenet.com.eg." refers to 
  "proxy.purenet.com.eg." which is a CNAME record
    An NS record located in the zone "purenet.com.eg." refers to the 
    host "proxy.purenet.com.eg.".  The record "proxy.purenet.com.eg."
    is a CNAME record.  NS records should always refer to canonical
    host names.

o The reverse record "6.67.131.213.in-addr.arpa." does not refer to 
  the host "r2000.purenet.com.eg."
    The reverse record "6.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-6.link.net.", but it should refer to
    "r2000.purenet.com.eg.".

o The reverse record "41.67.131.213.in-addr.arpa." does not refer to 
  the host "purenet.com.eg."
    The reverse record "41.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-41.link.net.", but it should refer to
    "purenet.com.eg.".

o The reverse record "41.67.131.213.in-addr.arpa." does not refer to 
  the host "ns1.purenet.com.eg."
    The reverse record "41.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-41.link.net.", but it should refer to
    "ns1.purenet.com.eg.".

o The reverse record "41.67.131.213.in-addr.arpa." does not refer to 
  the host "mail.purenet.com.eg."
    The reverse record "41.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-41.link.net.", but it should refer to
    "mail.purenet.com.eg.".

o The reverse record "41.67.131.213.in-addr.arpa." does not refer to 
  the host "cww5.purenet.com.eg."
    The reverse record "41.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-41.link.net.", but it should refer to
    "cww5.purenet.com.eg.".

o The reverse record "41.67.131.213.in-addr.arpa." does not refer to 
  the host "ftp.purenet.com.eg."
    The reverse record "41.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-41.link.net.", but it should refer to
    "ftp.purenet.com.eg.".

o The reverse record "41.67.131.213.in-addr.arpa." does not refer to 
  the host "mrtg.purenet.com.eg."
    The reverse record "41.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-41.link.net.", but it should refer to
    "mrtg.purenet.com.eg.".

o The reverse record "41.67.131.213.in-addr.arpa." does not refer to 
  the host "www.purenet.com.eg."
    The reverse record "41.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-41.link.net.", but it should refer to
    "www.purenet.com.eg.".

o The reverse record "76.67.131.213.in-addr.arpa." does not refer to 
  the host "ns3.purenet.com.eg."
    The reverse record "76.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-76.link.net.", but it should refer to
    "ns3.purenet.com.eg.".

o The reverse record "76.67.131.213.in-addr.arpa." does not refer to 
  the host "address.purenet.com.eg."
    The reverse record "76.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-76.link.net.", but it should refer to
    "address.purenet.com.eg.".

o The reverse record "76.67.131.213.in-addr.arpa." does not refer to 
  the host "tftp.purenet.com.eg."
    The reverse record "76.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-76.link.net.", but it should refer to
    "tftp.purenet.com.eg.".

o The reverse record "80.67.131.213.in-addr.arpa." does not refer to 
  the host "ns2.purenet.com.eg."
    The reverse record "80.67.131.213.in-addr.arpa." refers to 
    "host-213-131-67-80.link.net.", but it should refer to
    "ns2.purenet.com.eg.".


Warnings
----------------------------------------------------------------------
o The zone contains more than one authoritative name server with the 
  same IP address
    The name servers "proxy.purenet.com.eg." and 
    "ns1.purenet.com.eg.", which are authoritative for
    "purenet.com.eg.", have the same IP address (213.131.67.10).

o "ns1.purenet.com.eg." does not contain the latest version of the 
  zone
    "ns1.purenet.com.eg." contains an old version of the zone.  The 
    latest version of the zone has the serial number "93", but the
    version contained at "ns1.purenet.com.eg." has the serial number
    "88".

o The primary name server "ns1.purenet.com.eg." contains old data.  
  "ns2.purenet.com.eg." was selected as the primary server
    The server "ns1.purenet.com.eg." which, according to the SOA 
    record, is the primary server for the zone, contains an old
    version of the zone.  The DNS Analyzer will use the zone data from
    the server "ns2.purenet.com.eg.", which contains a later version
    of the zone.

o The CNAME record "secure.purenet.com.eg." is a part of a CNAME chain
    The CNAME record "secure.purenet.com.eg." points to 
    "proxy.purenet.com.eg.", which is also a CNAME record.

o All name servers for the zone are on the same subnet.
    All name servers for the zone are on the same subnet 
    (213.131.67.*).  If the connection to the network breaks, your
    domain will become inaccessible.

o There is only one MX record in the zone
    The zone contains only one MX record.  This will cause mail 
    delivery problems if the primary mail server becomes unavailable. 
    For safety purposes, there should be two or more mail servers for
    every zone, the extra mail servers being used as backup
    (secondary) servers for the primary server.


----------------------------------------------------------------------
end of report

Reply via email to