[swinog] SwiNOG-BE85 - Beer Event 85 - 3rd of May 2010 @ Outback / ZH

2010-04-29 Diskussionsfäden Steven Glogger
hi everybody

here's the announcement for the next beer event.

the facts for the next event:
-
Date:   3rd of May 2010

Time:   starting around 18.30 o'clock

Location:   @ the "Outback" Bahnhof Stadelhofen

Registration deadline:  02.05.2010 16:00 (Sunday)

Registration:   http://swinog.mrmouse.ch

-

Please register here: http://swinog.mrmouse.ch/ since we have to make
reservations, i need to know who's coming and who not. If you cannot 
attend and you're registered please inform me asap (+41 79 277 92 35).

-steven

___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


Re: [swinog] Geolocating IP's

2010-04-29 Diskussionsfäden Philipp Nyffenegger
Hi, one of the most sophisticated Country to IP Databases i know of is at
http://ip.ludost.net

It even allows you to download the lists pre-formated in Cisco-ACLs,
Iptables, apache .htaccess and a lot of other differerent formats. Afaik
it's updated daily. Hope this helps.

Cheers,
Phippu

___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


Re: [swinog] DNS: Clueless: Strange problems resolving ch domains...

2010-04-29 Diskussionsfäden Alexander Gall
On Thu, 29 Apr 2010 13:58:07 +0200, "Christian 'wiwi' Wittenhorst" 
 said:

> Solution:
> Routing to 138.190.0.0/16 was broken (blackholed at upstream), so both 
> (dns[12].swisscom.com) were not reachable.

Ok, but I'd still say that you have a problem with your IPv6
connectivity.

> I will have to spend some time on the inner workings of dig...

Yes.  Think about it.  If you do a "dig swisscom.ch. ns @a.nic.ch",
you're only asking, well, a.nic.ch.  The Swisscom name servers are not
involved at all.  Therefore, your issue with 138.190.0.0/16 has
*nothing* to do with the problems you've described in your first
message (but everything with your customer's problem :)

So, let me elaborate a bit on your dig output.

On Thu, 29 Apr 2010 10:50:17 +0200, "Christian 'wiwi' Wittenhorst" 
 said:

> (820)[r...@svn /tmp]# sh ch
> dig swisscom.ch ns @A.nic.ch
> ;; Got referral reply from 130.59.1.80, trying next server

> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @A.nic.ch
> ;; global options:  printcmd
> ;; connection timed out; no servers could be reached

> dig swisscom.ch ns @B.nic.ch
> ;; Got referral reply from 130.59.211.10, trying next server

This is not standard behaviour of dig.  It appears that RedHat has
applied a patch that makes dig skip to the next server in its search
list if it encounters a referral, which is totally bogus.  In
particular, it appears to only be in effect if the search list
contains multiple entries (otherwise, it wouldn't display anything in
the IPv4-only case either).  Please use a regular version of dig for
diagnostics.

It also appears that your dig is not strictly preferring IPv6 over
IPv4.  That's why, for dual-stacked servers, you sometimes see the
"Got referral reply" message (IPv4 first then IPv6, which then times
out) and sometimes "connection timed out".  In the latter case, the
initial IPv6 query will time out.  There should be a retry with IPv4,
which should actually succeed, but maybe the RedHat patch breaks this,
too (the result is still a referral, of course; maybe because the
stupid patch even has a bug when the search list has more than one
entry and falls off the end of the list).

-- 
Alex



___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


Re: [swinog] DNS: Clueless: Strange problems resolving ch domains...

2010-04-29 Diskussionsfäden Matthias Hertzog

Hi there!

Maybe a client resolver issue. Have a look at: 
http://weblogs.asp.net/owscott/archive/2009/09/15/windows-server-2008-r2-dns-issues.aspx - 
that helped some clients already when they complained about unresolvable 
domains.


Best wishes,
Matthias



- Original Message - 
From: "Benoit Panizzon" 

To: 
Sent: Thursday, April 29, 2010 10:58 AM
Subject: Re: [swinog] DNS: Clueless: Strange problems resolving ch 
domains...



No Problems here..


From a to f all according:


$ dig NS swisscom.ch @f.nic.ch.

; <<>> DiG 9.5.1-P3 <<>> NS swisscom.ch @f.nic.ch.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6710
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

Mit freundlichen GrĂ¼ssen

Benoit Panizzon
--
I m p r o W a r e   A G-Leiter IT Customer Care
__

Zurlindenstrasse 29 Tel  +41 61 826 93 07
CH-4133 PrattelnFax  +41 61 826 93 02
Schweiz Web  http://www.imp.ch
__


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog




___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


Re: [swinog] DNS: Clueless: Strange problems resolving ch domains...

2010-04-29 Diskussionsfäden Christian 'wiwi' Wittenhorst

Solution:

Routing to 138.190.0.0/16 was broken (blackholed at upstream), so both 
(dns[12].swisscom.com) were not reachable.


I will have to spend some time on the inner workings of dig...

Thanks for the suggestions...

   wiwi


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


Re: [swinog] DNS: Clueless: Strange problems resolving ch domains...

2010-04-29 Diskussionsfäden Thomas Mueller
i too see this . But only on debian lenny bind9 installations, not on 
every host and only since a few days. Maybe some security update 
introduced a bug.


as a workaround i configured forwarders.

- Thomas


On 29.04.2010 10:50, Christian 'wiwi' Wittenhorst wrote:

I got some reports from customers that some CH domains no not
resolve... While testing if found: Only two of the [a-f].nic.ch seem
to give replies... The ones that answer are exactly the ones that do
not have IPv6 addresses...

Happens at least for ksz.ch and swisscom.ch. Anyone else sees this?

Any ideas?

(820)[r...@svn /tmp]# sh ch
dig swisscom.ch ns @A.nic.ch
;; Got referral reply from 130.59.1.80, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns
@A.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @B.nic.ch
;; Got referral reply from 130.59.211.10, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns
@B.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @C.nic.ch
;; Got referral reply from 147.28.0.39, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns
@C.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @D.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns
@D.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24625
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns2.swisscom.com.
swisscom.ch.3600IN  NS  dns1.swisscom.com.

;; Query time: 218 msec
;; SERVER: 200.160.0.5#53(200.160.0.5)
;; WHEN: Thu Apr 29 10:41:36 2010
;; MSG SIZE  rcvd: 79


dig swisscom.ch ns @E.nic.ch
;; Got referral reply from 204.61.216.47, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns
@E.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @F.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns
@F.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61901
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns1.swisscom.com.
swisscom.ch.3600IN  NS  dns2.swisscom.com.

;; Query time: 24 msec
;; SERVER: 194.146.106.10#53(194.146.106.10)
;; WHEN: Thu Apr 29 10:41:51 2010
;; MSG SIZE  rcvd: 79



dig ksz.ch ns @A.nic.ch
;; Got referral reply from 130.59.1.80, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @A.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @B.nic.ch
;; Got referral reply from 130.59.211.10, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @B.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @C.nic.ch
;; Got referral reply from 147.28.0.39, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @C.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @D.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @D.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59974
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;ksz.ch.IN  NS

;; AUTHORITY SECTION:
ksz.ch. 3600IN  NS  zug.ch.ns.progon.net.
ksz.ch. 3600IN  NS  udns1.ultradns.net.
ksz.ch. 3600IN  NS  udns2.ultradns.net.

;; Query time: 228 msec
;; SERVER: 200.160.0.5#53(200.160.0.5)
;; WHEN: Thu Apr 29 10:44:25 2010
;; MSG SIZE  rcvd: 107


dig ksz.ch ns @E.nic.ch
;; Got referral reply from 204.61.216.47, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @E.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @F.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @F.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1256
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;ksz.ch.IN  NS

;; AUTHORITY SECTION:
ksz.ch. 3600IN  NS  zug.ch.ns.progon.net.
ksz.ch. 3600IN  NS  udns2.ultradns.net.
ksz.ch.   

Re: [swinog] DNS: Clueless: Strange problems resolving ch domains...

2010-04-29 Diskussionsfäden Ihsan Dogan

Hello Wiwi,

On 04/29/10 10:50, Christian 'wiwi' Wittenhorst wrote:


I got some reports from customers that some CH domains no not resolve...
While testing if found: Only two of the [a-f].nic.ch seem to give
replies... The ones that answer are exactly the ones that do not have
IPv6 addresses...

Happens at least for ksz.ch and swisscom.ch. Anyone else sees this?


Works fine for me:

-
tzhdo...@bw121isd:~$ dig NS swisscom.ch @a.nic.ch

; <<>> DiG 9.3.6-P1 <<>> NS swisscom.ch @a.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 141
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns2.swisscom.com.
swisscom.ch.3600IN  NS  dns1.swisscom.com.

;; Query time: 1 msec
;; SERVER: 130.59.1.80#53(130.59.1.80)
;; WHEN: Thu Apr 29 11:31:43 2010
;; MSG SIZE  rcvd: 79

tzhdo...@bw121isd:~$ dig NS swisscom.ch @b.nic.ch

; <<>> DiG 9.3.6-P1 <<>> NS swisscom.ch @b.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2028
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns2.swisscom.com.
swisscom.ch.3600IN  NS  dns1.swisscom.com.

;; Query time: 6 msec
;; SERVER: 130.59.211.10#53(130.59.211.10)
;; WHEN: Thu Apr 29 11:31:49 2010
;; MSG SIZE  rcvd: 79

tzhdo...@bw121isd:~$ dig NS swisscom.ch @c.nic.ch

; <<>> DiG 9.3.6-P1 <<>> NS swisscom.ch @c.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 830
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns1.swisscom.com.
swisscom.ch.3600IN  NS  dns2.swisscom.com.

;; Query time: 175 msec
;; SERVER: 147.28.0.39#53(147.28.0.39)
;; WHEN: Thu Apr 29 11:31:51 2010
;; MSG SIZE  rcvd: 79

tzhdo...@bw121isd:~$ dig NS swisscom.ch @d.nic.ch

; <<>> DiG 9.3.6-P1 <<>> NS swisscom.ch @d.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1607
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns1.swisscom.com.
swisscom.ch.3600IN  NS  dns2.swisscom.com.

;; Query time: 237 msec
;; SERVER: 200.160.0.5#53(200.160.0.5)
;; WHEN: Thu Apr 29 11:31:54 2010
;; MSG SIZE  rcvd: 79

tzhdo...@bw121isd:~$ dig NS swisscom.ch @e.nic.ch

; <<>> DiG 9.3.6-P1 <<>> NS swisscom.ch @e.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1462
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns1.swisscom.com.
swisscom.ch.3600IN  NS  dns2.swisscom.com.

;; Query time: 18 msec
;; SERVER: 204.61.216.47#53(204.61.216.47)
;; WHEN: Thu Apr 29 11:31:57 2010
;; MSG SIZE  rcvd: 79

tzhdo...@bw121isd:~$ dig NS swisscom.ch @f.nic.ch

; <<>> DiG 9.3.6-P1 <<>> NS swisscom.ch @f.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 191
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns1.swisscom.com.
swisscom.ch.3600IN  NS  dns2.swisscom.com.

;; Query time: 6 msec
;; SERVER: 194.146.106.10#53(194.146.106.10)
;; WHEN: Thu Apr 29 11:32:00 2010
;; MSG SIZE  rcvd: 79

tzhdo...@bw121isd:~$ dig NS swisscom.ch @h.nic.ch

; <<>> DiG 9.3.6-P1 <<>> NS swisscom.ch @h.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1800
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns1.swisscom.com.
swisscom.ch.3600IN  NS  dns2.swisscom.com.

;; Query time: 1 msec
;; SERVER: 194.42.48.120#53(194.42.48.120)
;; WHEN: Thu Apr 29 11:32:20 2010
;; MSG SIZE  rcvd: 90
-


Are you sure that it's not on your side?




Ihsan


--
ih...@dogan.ch  http://blog.dogan.ch/


___
swinog mailing list
swinog@lists.swinog.ch

Re: [swinog] DNS: Clueless: Strange problems resolving ch domains...

2010-04-29 Diskussionsfäden Benoit Panizzon
No Problems here..

>From a to f all according:

$ dig NS swisscom.ch @f.nic.ch.

; <<>> DiG 9.5.1-P3 <<>> NS swisscom.ch @f.nic.ch.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6710
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

Mit freundlichen GrĂ¼ssen

Benoit Panizzon
-- 
I m p r o W a r e   A G-Leiter IT Customer Care
__

Zurlindenstrasse 29 Tel  +41 61 826 93 07
CH-4133 PrattelnFax  +41 61 826 93 02
Schweiz Web  http://www.imp.ch
__


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


[swinog] DNS: Clueless: Strange problems resolving ch domains...

2010-04-29 Diskussionsfäden Christian 'wiwi' Wittenhorst
I got some reports from customers that some CH domains no not resolve... 
While testing if found: Only two of the [a-f].nic.ch seem to give 
replies... The ones that answer are exactly the ones that do not have 
IPv6 addresses...


Happens at least for ksz.ch and swisscom.ch. Anyone else sees this?

Any ideas?

(820)[r...@svn /tmp]# sh ch
dig swisscom.ch ns @A.nic.ch
;; Got referral reply from 130.59.1.80, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @A.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @B.nic.ch
;; Got referral reply from 130.59.211.10, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @B.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @C.nic.ch
;; Got referral reply from 147.28.0.39, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @C.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @D.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @D.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24625
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns2.swisscom.com.
swisscom.ch.3600IN  NS  dns1.swisscom.com.

;; Query time: 218 msec
;; SERVER: 200.160.0.5#53(200.160.0.5)
;; WHEN: Thu Apr 29 10:41:36 2010
;; MSG SIZE  rcvd: 79


dig swisscom.ch ns @E.nic.ch
;; Got referral reply from 204.61.216.47, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @E.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig swisscom.ch ns @F.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> swisscom.ch ns @F.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61901
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;swisscom.ch.   IN  NS

;; AUTHORITY SECTION:
swisscom.ch.3600IN  NS  dns1.swisscom.com.
swisscom.ch.3600IN  NS  dns2.swisscom.com.

;; Query time: 24 msec
;; SERVER: 194.146.106.10#53(194.146.106.10)
;; WHEN: Thu Apr 29 10:41:51 2010
;; MSG SIZE  rcvd: 79



dig ksz.ch ns @A.nic.ch
;; Got referral reply from 130.59.1.80, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @A.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @B.nic.ch
;; Got referral reply from 130.59.211.10, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @B.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @C.nic.ch
;; Got referral reply from 147.28.0.39, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @C.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @D.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @D.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59974
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;ksz.ch.IN  NS

;; AUTHORITY SECTION:
ksz.ch. 3600IN  NS  zug.ch.ns.progon.net.
ksz.ch. 3600IN  NS  udns1.ultradns.net.
ksz.ch. 3600IN  NS  udns2.ultradns.net.

;; Query time: 228 msec
;; SERVER: 200.160.0.5#53(200.160.0.5)
;; WHEN: Thu Apr 29 10:44:25 2010
;; MSG SIZE  rcvd: 107


dig ksz.ch ns @E.nic.ch
;; Got referral reply from 204.61.216.47, trying next server

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @E.nic.ch
;; global options:  printcmd
;; connection timed out; no servers could be reached

dig ksz.ch ns @F.nic.ch

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> ksz.ch ns @F.nic.ch
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1256
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;ksz.ch.IN  NS

;; AUTHORITY SECTION:
ksz.ch. 3600IN  NS  zug.ch.ns.progon.net.
ksz.ch. 3600IN  NS  udns2.ultradns.net.
ksz.ch. 3600IN  NS  udns1.ultradns.net.

;; Query time: 24 msec
;; SERVER: 194.146.106.10#53(194.146.106.10)
;; WHEN: Thu Apr 29 10:44:41 2010
;; MSG SIZE  rcvd: 107


(825)[r...@svn /tmp]# dig -d swisscom.ch ns @A.nic.ch
main parsing swisscom.ch
clo