DNS report for zone umich.edu

This is a cached entry from 2011-12-30 11:29:38, press here to do a realtime lookup!

• Category Status Test Name Information
• NS
  • 
  • NS records from
    your nameservers

  • NS records got from your nameservers are:

    
    

    dns.cs.wisc.edu [128.105.2.10]
    dns2.itd.umich.edu [141.211.125.15]
    dns.itd.umich.edu [141.211.144.15]
    

• • 
  • Zone transfers

  • I could use the nameservers listed below to perform zone transfers. Zone transfers enables other parties to download a full list of all names under this zone. This might lead to unwanted information disclosure.
    
    The following servers allowed zone transfers (AXFR) for umich.edu:
    dns2.itd.umich.edu
    dns.itd.umich.edu

• • 
  • Recursive Queries

  • I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
    dns2.itd.umich.edu
    dns.itd.umich.edu

• • 
  • Mismatched NS records

  • OK. The NS records at all your nameservers are identical.

• • 
  • DNS servers responded

  • Good. All nameservers listed at the parent server responded.

• • 
  • Multiple Nameservers

  • OK. You have multiple nameservers. In most cases 2 are enough, however, RFC2182 section 5 states that you must have at least 3 nameservers, and no more than 7.

• • 
  • Nameservers are lame

  • OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

• • 
  • Domain CNAMES

  • OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other)
    record is present.

• • 
  • Different subnets

  • OK. Looks like you have nameservers on different subnets!

• • 
  • IPs of nameservers
    are public

  • Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like

• • 
  • DNS servers allow
    TCP connection

  • OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.

• SOA
  • 
  • SOA record

  • The SOA record is:
    Primary nameserver: dns.itd.umich.edu
    Hostmaster E-mail address: hostmaster@umich.edu
    Serial #: 2011122101
    Refresh: 1800
    Retry: 900
    Expire:2419200
    Default TTL: 1800

• • 
  • NSs have same SOA
    serial

  • OK. All your nameservers agree that your SOA serial number is 2011122101

• • 
  • SOA MNAME entry

  • OK. dns.itd.umich.edu That server is listed at the parent servers.

• • 
  • SOA Serial

  • Your SOA serial number is: 2011122101. Your SOA serial can pretty much be whatever you want, but most people prefer to have it in YYYYMMDD00-99 format.

• • 
  • SOA REFRESH

  • OK. Your SOA REFRESH interval is: 1800. That is OK

• • 
  • SOA RETRY

  • OK. Your SOA RETRY value is: 600. Looks ok.

• • 
  • SOA EXPIRE

  • OK. Your SOA EXPIRE value is: 2419200. Looks ok.

• • 
  • SOA MINIMUM

  • WARN. Your SOA MINIMUM interval is: 1800. We recommend that you raise it to be within the 3600 to 10800 range. (1 to 3 hours)

• MX
  • 
  • MX Records

  • Your MX records that were reported by your nameservers are:

    
    

    0 mx3.umich.edu
    0 mx1.umich.edu
    0 mx2.umich.edu
    

• • 
  • MX is not IP

  • OK. All of your MX records are host names.

• • 
  • Multiple MX

  • OK. You have multiple mailservers. (3 MX records detected)

• WWW
  • 
  • WWW Record

  • Your www.umich.edu record is:
    www.umich.edu [141.211.144.186, 141.211.13.224, 141.211.13.226, 141.211.144.182]
    

• • 
  • IPs are public

  • OK. All of your WWW IPs appear to be public IPs.

• • 
  • WWW CNAME

  • OK. No CNAME