On 2010-05-17 11:07, Matthias Hertzog wrote: Any technical output like the below which shows it works? If your latency went up, check the route that it passes over. 'mtr' can be very useful there. Greets, Jeroen $ dig +trace www.cablecom.ch ; <<>> DiG 9.5.1-P3 <<>> +trace www.cablecom.ch ;; global options: printcmd . 371842 IN NS k.root-servers.net. . 371842 IN NS d.root-servers.net. . 371842 IN NS b.root-servers.net. . 371842 IN NS a.root-servers.net. . 371842 IN NS e.root-servers.net. . 371842 IN NS i.root-servers.net. . 371842 IN NS c.root-servers.net. . 371842 IN NS j.root-servers.net. . 371842 IN NS f.root-servers.net. . 371842 IN NS l.root-servers.net. . 371842 IN NS h.root-servers.net. . 371842 IN NS g.root-servers.net. . 371842 IN NS m.root-servers.net. ;; Received 449 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms ch. 172800 IN NS e.nic.ch. ch. 172800 IN NS h.nic.ch. ch. 172800 IN NS f.nic.ch. ch. 172800 IN NS d.nic.ch. ch. 172800 IN NS c.nic.ch. ch. 172800 IN NS b.nic.ch. ch. 172800 IN NS a.nic.ch. ;; Received 373 bytes from 192.203.230.10#53(e.root-servers.net) in 183 ms cablecom.ch. 3600 IN NS ns2.cablecom.net. cablecom.ch. 3600 IN NS ns1.cablecom.net. ;; Received 81 bytes from 2001:620::4#53(a.nic.ch) in 23 ms www.cablecom.ch. 600 IN A 62.2.16.94 ;; Received 49 bytes from 213.47.222.133#53(ns2.cablecom.net) in 25 ms