Starting zone checks for u-type.org
Checking zone name
Resolving name-server address-> ns2.idroot.com. 14400 IN A 173.0.49.116Checking existence of zone-> u-type.org. 86400 IN SOA ns1.idroot.com. host.idroot.com. ( 2011061802 ; Serial 86400 ; Refresh 7200 ; Retry 3600000 ; Expire 86400 ) ; Minimum TTLChecking NS records-> u-type.org. 86400 IN NS ns2.idroot.com. -> u-type.org. 86400 IN NS ns1.idroot.com.Checking nameserver authority and synchronization-> ns2.idroot.com. 14400 IN A 173.0.49.116### Error: ns2.idroot.com (173.0.49.116) has no reverse record [see RFC1912:2.1 for details]
Probing name server ns2.idroot.com (173.0.49.116)-> u-type.org. 86400 IN SOA ns1.idroot.com. host.idroot.com. ( 2011061802 ; Serial 86400 ; Refresh 7200 ; Retry 3600000 ; Expire 86400 ) ; Minimum TTL -> u-type.org. 86400 IN NS ns2.idroot.com. -> u-type.org. 86400 IN NS ns1.idroot.com. -> ns1.idroot.com. 14400 IN A 119.235.250.226### Error: ns1.idroot.com (119.235.250.226) has no reverse record [see RFC1912:2.1 for details]
Probing name server ns1.idroot.com (119.235.250.226)-> u-type.org. 86400 IN SOA ns1.idroot.com. host.idroot.com. ( 2011061802 ; Serial 86400 ; Refresh 7200 ; Retry 3600000 ; Expire 86400 ) ; Minimum TTL -> u-type.org. 86400 IN NS ns2.idroot.com. -> u-type.org. 86400 IN NS ns1.idroot.com.Decided to use ns2.idroot.com (173.0.49.116) for zone check
Checking whether ns2.idroot.com knows an A record for its own name-> ns2.idroot.com. 14400 IN A 173.0.49.116Checking whether ns2.idroot.com is able to reverse-map its own IP address
Checking connectivity with other nameservers
### Warning: ns2.idroot.com is unable to resolve www.ucw.cz (maybe it's non-recursive)
### Warning: ns2.idroot.com is unable to resolve atrey.karlin.mff.cuni.cz (maybe it's non-recursive)
### Warning: ns2.idroot.com is unable to resolve www.google.com (maybe it's non-recursive)
Checking mapping of localhost
### Warning: ns2.idroot.com is unable to resolve localhost [see RFC1912:4.1 for details]
### Warning: Reverse mapping of 127.0.0.1 at ns2.idroot.com doesn't work [see RFC1912:4.1 for details]
Summary: 2 errors, 5 warnings