if the whole network is not reachable and even a ip resolving of one of the main serveradresses is not working i don´t have to try any other tools to know that everything is down :-)
see also: http://www.heise.de/newsticker/Serverausfall-beim-Hoster-Intergenia--/meldun...
bernd
-----Original Message----- From: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] On Behalf Of Jeroen Massar Sent: Wednesday, July 16, 2008 1:16 PM To: swinog@swinog.ch Subject: Re: [swinog] name-server slowdown?
Spiess Bernd wrote:
we noticed, server4you.de was and is still not reachable
U:>tracert www.server4you.de Der Zielname www.server4you.de konnte nicht aufgelöst werden.
Using tracert as a diagnostic tool for DNS?
Please take a look at one of the following for resolving your most likely local problems:
- dig - zonecheck (http://www.zonecheck.fr)
Just in case the result of the first is:
www.server4you.de. 86400 IN A 217.172.191.67 server4you.de. 86400 IN NS ns2.server4you.de. server4you.de. 86400 IN NS ns1.server4you.de. ;; Received 119 bytes from 217.172.162.246#53(ns1.server4you.de) in 10 ms
Thus at least the hostname works. ICMP's seem to be blocked in that direction though.
8<---------------------------------------------------- $ telnet www.server4you.de. 80 Trying 217.172.191.67... Connected to www.server4you.de. Escape character is '^]'. GET / HTTP/1.1
HTTP/1.1 400 Bad Request Date: Wed, 16 Jul 2008 11:15:40 GMT Server: Apache/2.0.52 (CentOS) Content-Length: 309 Connection: close Content-Type: text/html; charset=iso-8859-1 ... ---------------------------------------------------->8
Looks like it is working to me...
Greets, Jeroen