Starting zone checks for st.nl
Checking zone name
Resolving name-server address-> ns03.2is.nl. 600 IN A 212.32.226.100Checking existence of zone-> st.nl. 3600 IN SOA ns03.2is.nl. domain-admin.2is.nl. ( 2010031700 ; Serial 14400 ; Refresh 3600 ; Retry 604800 ; Expire 3600 ) ; Minimum TTLChecking NS records-> st.nl. 600 IN NS ns04.2is.nl. -> st.nl. 600 IN NS ns03.2is.nl.Checking nameserver authority and synchronization-> ns03.2is.nl. 600 IN A 212.32.226.100 -> 100.226.32.212.in-addr.arpa. 600 IN PTR ns03.2is.nl.Probing name server ns03.2is.nl (212.32.226.100)-> st.nl. 3600 IN SOA ns03.2is.nl. domain-admin.2is.nl. ( 2010031700 ; Serial 14400 ; Refresh 3600 ; Retry 604800 ; Expire 3600 ) ; Minimum TTL -> st.nl. 600 IN NS ns04.2is.nl. -> st.nl. 600 IN NS ns03.2is.nl. -> ns04.2is.nl. 600 IN A 62.221.194.100 -> 100.194.221.62.in-addr.arpa. 600 IN PTR ns04.2is.be. -> ns04.2is.be. 600 IN A 62.221.194.100### Warning: 62.221.194.100 for ns04.2is.nl points back to ns04.2is.be [see RFC1912:2.1 for details]
Probing name server ns04.2is.nl (62.221.194.100)-> st.nl. 3600 IN SOA ns03.2is.nl. domain-admin.2is.nl. ( 2010031700 ; Serial 14400 ; Refresh 3600 ; Retry 604800 ; Expire 3600 ) ; Minimum TTL -> st.nl. 600 IN NS ns04.2is.nl. -> st.nl. 600 IN NS ns03.2is.nl.Decided to use ns03.2is.nl (212.32.226.100) for zone check
Checking whether ns03.2is.nl knows an A record for its own name-> ns03.2is.nl. 600 IN A 212.32.226.100Checking whether ns03.2is.nl is able to reverse-map its own IP address
Checking connectivity with other nameservers-> www.ucw.cz. 86400 IN CNAME jabberwock.ucw.cz. -> jabberwock.ucw.cz. 86400 IN A 89.250.246.4 -> atrey.karlin.mff.cuni.cz. 86400 IN A 195.113.26.193 -> www.google.com. 505239 IN CNAME www.l.google.com. -> www.l.google.com. 300 IN A 74.125.79.99 -> www.l.google.com. 300 IN A 74.125.79.104 -> www.l.google.com. 300 IN A 74.125.79.147Checking mapping of localhost
### Warning: ns03.2is.nl is unable to resolve localhost [see RFC1912:4.1 for details]
### Warning: Reverse mapping of 127.0.0.1 at ns03.2is.nl doesn't work [see RFC1912:4.1 for details]
Summary: 0 errors, 3 warnings