All of the mentioned websites are hosted on the same IP address. The lookup looks the same on Google and Swisscom DNS. Swisscom DNS: ; <<>> DiG 9.16.13 <<>> @195.186.1.162 burger-meister.ch
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24249
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;burger-meister.ch. IN A
;; ANSWER SECTION:
burger-meister.ch. 3912 IN A 109.232.216.249
;; Query time: 6 msec
;; SERVER: 195.186.1.162#53(195.186.1.162)
;; WHEN: Mi Apr 28 23:06:25 CEST 2021
;; MSG SIZE rcvd: 62 Google DNS: ; <<>> DiG 9.16.13 <<>> @8.8.8.8 burger-meister.ch
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58842
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;burger-meister.ch. IN A
;; ANSWER SECTION:
burger-meister.ch. 14399 IN A 109.232.216.249
;; Query time: 43 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mi Apr 28 23:06:25 CEST 2021
;; MSG SIZE rcvd: 62 The IP for all domains (also including www.XXXXX) are the same on Google and Swisscom DNS. I do not know the Windows tool used by you, so I have no clue which protocol is used. However, as you can see in your output, the last IP from the Swisscom trace is the second last IP from the trace with your second provider. So up until that IP, everything works as expected. Now I used traceroute on Linux for my test and if called without any parameter, it uses UDP on random ports as protocol. This traceroute failed. [user@WS ~]$ traceroute 109.232.216.249
traceroute to 109.232.216.249 (109.232.216.249), 30 hops max, 60 byte packets
1 localgw (192.168.240.13) 0.510 ms 3.611 ms 3.576 ms
2 localnet (192.168.236.16) 3.551 ms 3.521 ms 3.498 ms
3 localnet (192.168.237.15) 3.469 ms 2.814 ms 3.037 ms
4 1.212.194.178.dynamic.wline.res.cust.swisscom.ch (178.194.212.1) 6.018 ms 6.175 ms 6.471 ms
5 * * *
6 * * *
7 i79zhb-015-ae6.bb.ip-plus.net (138.187.129.155) 8.648 ms 8.862 ms 9.211 ms
8 i00dcx-005-ae11.bb.ip-plus.net (138.187.130.61) 13.701 ms 13.865 ms 14.226 ms
9 frankfurt1.ln1.turktelekom.com.tr (80.81.192.82) 15.784 ms 9.713 ms 9.322 ms
10 00-ebgp-gayrettepe-k---301-fra-col-1.statik.turktelekom.com.tr (212.156.101.59) 41.453 ms 34-ebgp-acibadem-sr12e-k---301-fra-col-1.statik.turktelekom.com.tr (212.156.101.231) 42.486 ms 00-ebgp-gayrettepe-k---301-fra-col-1.statik.turktelekom.com.tr (212.156.101.211) 45.319 ms
11 34-acibadem-xrs-t2-2---34-ebgp-acibadem-sr12e-k.statik.turktelekom.com.tr (81.212.209.217) 43.656 ms 27-organize4-t4-1---27-mervesehir-t4-1.statik.turktelekom.com.tr (81.212.25.58) 47.446 ms 212.156.120.184.static.turktelekom.com.tr (212.156.120.184) 46.344 ms
12 00-gayrettepe-xrs-t2-2---34-acibadem-xrs-t2-2.statik.turktelekom.com.tr (81.212.212.253) 45.566 ms 00-gayrettepe-xrs-t2-2---00-ebgp-gayrettepe-k.statik.turktelekom.com.tr (81.212.202.18) 45.263 ms 34-acibadem-xrs-t2-2---34-ebgp-acibadem-sr12e-k.statik.turktelekom.com.tr (81.212.209.217) 49.384 ms
13 00-gayrettepe-t3-5---00-gayrettepe-xrs-t2-2.statik.turktelekom.com.tr (195.175.172.84) 49.217 ms 47.190 ms 47.374 ms
14 * * *
15 85.111.76.42.dynamic.ttnet.com.tr (85.111.76.42) 42.271 ms * 41.929 ms
16 85.111.76.42.dynamic.ttnet.com.tr (85.111.76.42) 46.772 ms * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * * The next step is a traceroute with ICMP, which was successfull. [user@WS ~]$ traceroute -I 109.232.216.249
traceroute to 109.232.216.249 (109.232.216.249), 30 hops max, 60 byte packets
1 localgw (192.168.240.13) 0.510 ms 3.611 ms 3.576 ms
2 localnet (192.168.236.16) 3.551 ms 3.521 ms 3.498 ms
3 localnet (192.168.237.15) 3.469 ms 2.814 ms 3.037 ms
4 1.212.194.178.dynamic.wline.res.cust.swisscom.ch (178.194.212.1) 8.667 ms 8.452 ms 9.280 ms
5 * * *
6 i79zhb-020-ae30.bb.ip-plus.net (193.134.95.172) 50.719 ms 48.065 ms 48.342 ms
7 i79zhb-015-ae6.bb.ip-plus.net (138.187.129.155) 6.381 ms 4.436 ms 4.691 ms
8 i00dcx-005-ae11.bb.ip-plus.net (138.187.130.61) 9.696 ms 11.988 ms 12.066 ms
9 frankfurt1.ln1.turktelekom.com.tr (80.81.192.82) 12.897 ms 9.929 ms 10.329 ms
10 34-ebgp-acibadem-sr12e-k---301-fra-col-1.statik.turktelekom.com.tr (212.156.101.231) 43.531 ms 43.913 ms 44.297 ms
11 34-acibadem-xrs-t2-2---34-ebgp-acibadem-sr12e-k.statik.turktelekom.com.tr (81.212.209.217) 44.768 ms 42.078 ms 42.266 ms
12 00-gayrettepe-xrs-t2-2---34-acibadem-xrs-t2-2.statik.turktelekom.com.tr (81.212.212.253) 42.254 ms 41.612 ms 41.555 ms
13 00-gayrettepe-t3-5---00-gayrettepe-xrs-t2-2.statik.turktelekom.com.tr (195.175.172.84) 42.761 ms 43.134 ms 43.330 ms
14 * * *
15 85.111.76.42.dynamic.ttnet.com.tr (85.111.76.42) 43.421 ms 43.149 ms 43.317 ms
16 88.218.128.14 (88.218.128.14) 41.905 ms 42.041 ms 42.714 ms
17 srvc249.trwww.com (109.232.216.249) 42.703 ms 42.308 ms 42.445 ms Last traceroute uses TCP with port 80 as Protocol and is also successful. [user@WS ~]$ traceroute -T 109.232.216.249
traceroute to 109.232.216.249 (109.232.216.249), 30 hops max, 60 byte packets
1 localgw (192.168.240.13) 0.424 ms 0.481 ms 0.473 ms
2 localnet (192.168.236.16) 1.079 ms 1.126 ms 1.231 ms
3 localnet (192.168.237.15) 3.223 ms 4.749 ms 5.793 ms
4 1.212.194.178.dynamic.wline.res.cust.swisscom.ch (178.194.212.1) 8.205 ms 10.145 ms 11.381 ms
5 * * *
6 * * *
7 i79zhb-015-ae6.bb.ip-plus.net (138.187.129.155) 23.575 ms 23.748 ms 23.915 ms
8 i00dcx-005-ae11.bb.ip-plus.net (138.187.130.61) 25.662 ms 26.160 ms 27.600 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 00-gayrettepe-t3-5---00-gayrettepe-xrs-t2-2.statik.turktelekom.com.tr (195.175.172.84) 49.316 ms 49.413 ms *
14 00-gayrettepe-t3-5---00-gayrettepe-xrs-t2-2.statik.turktelekom.com.tr (195.175.172.84) 55.521 ms * 49.537 ms
15 85.111.76.42.dynamic.ttnet.com.tr (85.111.76.42) 45.882 ms 45.599 ms *
16 88.218.128.14 (88.218.128.14) 45.431 ms 85.111.76.42.dynamic.ttnet.com.tr (85.111.76.42) 47.153 ms 88.218.128.14 (88.218.128.14) 42.778 ms
17 srvc249.trwww.com (109.232.216.249) 43.783 ms 45.854 ms 44.433 ms So all traceroutes were made from within the subnet 178.194.213.0/24 The same results were also achieved from within the subnet 178.193.212.0/24 and 178.192.42.0/24 However, I won't post all the output here because it is pretty much the same as above. From what I can see, there is no problem at the moment with any of the mentioned websites. If the problem is solved, maybe there was a temporary problem on the webserver. If the problem persists, maybe you could try a DNS lookup on your system and also check with what protocol/port your trace is operating and if necessary, change it to TCP/80 or ICMP and try again.
Mehr anzeigen