Hi,
Recently our websites (www.kortingcamera.nl, www.gogotrip.com) are moved to another webhost server, in the meantime we also tried to use cloudflare, but has stopped to use it.
We can access our website without any problem if we use shared mobile phone 4g for our computers. Of if we use the internet from t-mobile glassfiber, and use proxy, also can access.
But if we use the internet from t-mobile glassfiber directly, it can not access. We have contacted with the webhost provider, they checked it and told us that we have to contact with our internet provider, there might be some cache on t-mobile side that still forward the request to the old server.
In the meantime we also tried 3 different computers, restarted the router and computers, but did not make it work.
Below are some tests we did on our side.
> Using normal internet connection, can not connect to
> www.kortingcamera.nl
> -----------------------------------------------------------------------
> â ~ ping www.kortingcamera.nl
> PING www.kortingcamera.nl (69.163.166.216): 56 data bytes
> Request timeout for icmp_seq 0
> Request timeout for icmp_seq 1
> Request timeout for icmp_seq 2
> Request timeout for icmp_seq 3
> Request timeout for icmp_seq 4
> ^C
> --- www.kortingcamera.nl ping statistics ---
> 6 packets transmitted, 0 packets received, 100.0% packet loss
> â ~ traceroute www.kortingcamera.nl
> traceroute to www.kortingcamera.nl (69.163.166.216), 64 hops max, 52
> byte packets
> 1 192.168.1.1 (192.168.1.1) 2.516 ms 1.694 ms 3.255 ms
> 2 1-2-201-31.ftth.glasoperator.nl (31.201.2.1) 5.424 ms 5.516 ms
> 4.853 ms
> 3 10.10.80.149 (10.10.80.149) 9.643 ms 9.902 ms 9.627 ms
> 4 amsix-200gbps.core1.ams1.he.net (80.249.209.150) 11.219 ms
> 11.298 ms 11.007 ms
> 5 100ge16-1.core1.lon2.he.net (72.52.92.213) 16.718 ms 16.119 ms
> 15.868 ms
> 6 100ge13-2.core1.nyc4.he.net (72.52.92.166) 84.645 ms 86.238 ms
> 85.269 ms
> 7 100ge9-1.core2.chi1.he.net (184.105.223.161) 99.783 ms 99.749
> ms 100.013 ms
> 8 100ge14-2.core1.msp1.he.net (184.105.223.178) 108.129 ms
> 107.366 ms 108.921 ms
> 9 100ge10-1.core1.sea1.he.net (184.105.223.193) 140.595 ms
> 140.388 ms 139.267 ms
> 10 100ge11-1.core1.pdx1.he.net (184.105.64.138) 144.295 ms 145.522
> ms 145.575 ms
> 11 dreamhost.10gigabitethernet10-5.core1.pdx1.he.net (65.49.80.226)
> 145.218 ms 145.377 ms 145.610 ms
> 12 pdx1-cr-1.sd.dreamhost.com (66.33.200.2) 145.470 ms
> pdx1-cr-2.sd.dreamhost.com (66.33.200.3) 145.611 ms 146.712 ms
> 13 pdx1-a3u27-acc.sd.dreamhost.com (66.33.200.10) 147.750 ms
> 147.079 ms 147.149 ms
> 14 * * *
> 15 * * *
> -----------------------------------------------------------------------
>
> Using 4g connection from my mobile phone, can connect without any
> problem
> -----------------------------------------------------------------------
> â ~ ping www.kortingcamera.nl
> PING www.kortingcamera.nl (69.163.166.216): 56 data bytes
> 64 bytes from 69.163.166.216: icmp_seq=0 ttl=44 time=174.664 ms
> 64 bytes from 69.163.166.216: icmp_seq=1 ttl=44 time=173.139 ms
> 64 bytes from 69.163.166.216: icmp_seq=2 ttl=44 time=171.555 ms
> 64 bytes from 69.163.166.216: icmp_seq=3 ttl=44 time=175.002 ms
> ^C
> --- www.kortingcamera.nl ping statistics ---
> 4 packets transmitted, 4 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 171.555/173.590/175.002/1.369 ms
> â ~ traceroute www.kortingcamera.nl
> traceroute to www.kortingcamera.nl (69.163.166.216), 64 hops max, 52
> byte packets
> 1 172.20.10.1 (172.20.10.1) 1.149 ms 0.618 ms 0.506 ms
> 2 * * *
> 3 * * *
Bladzijde 1 / 1
I'm currently using the Cloudflare DNS (1.1.1.1 & 1.0.0.1) servers. I can reach both your websites and ping them by the way of a T-Mobile fiber connection.
As a test, change the DNS server IPs in your router (might also have to tick a check box to force use DNS setting somewhere). If everything starts to work afterward, it's probably something related to the T-Mobile default name servers.
As a test, change the DNS server IPs in your router (might also have to tick a check box to force use DNS setting somewhere). If everything starts to work afterward, it's probably something related to the T-Mobile default name servers.
Dear Divve,
Thank you very much for your kind reply.
I have login to the t-mobile router, and I can see the dns server ips, but there is no way to change them.
I tried to change the dns name on my computer by using google dns server 8.8.8.8 and 8.8.4.4, but still can not reach to my websites.
By the way, if the ping can already resolve the ip of my domain name, then does changing dns server ip still help?
Thank you very much for your kind reply.
I have login to the t-mobile router, and I can see the dns server ips, but there is no way to change them.
I tried to change the dns name on my computer by using google dns server 8.8.8.8 and 8.8.4.4, but still can not reach to my websites.
By the way, if the ping can already resolve the ip of my domain name, then does changing dns server ip still help?
Hi,
Sometimes changes to network settings don't commit until a reboot. You might want to try that if you haven't already.
"By the way, if the ping can already resolve the ip of my domain name, then does changing dns server ip still help?"
Yes. Normally it also implies that you should also be able to reach the website.
In testing I did however notice that the response times of your sites are inordinately long. According to the Developer tools in Chrome, the response time for www.gogotrip.com is 32.19 seconds. It could be an indication of a server side configuration problem and that it's simply timing out during your tests.
Sometimes changes to network settings don't commit until a reboot. You might want to try that if you haven't already.
"By the way, if the ping can already resolve the ip of my domain name, then does changing dns server ip still help?"
Yes. Normally it also implies that you should also be able to reach the website.
In testing I did however notice that the response times of your sites are inordinately long. According to the Developer tools in Chrome, the response time for www.gogotrip.com is 32.19 seconds. It could be an indication of a server side configuration problem and that it's simply timing out during your tests.
I can reach both of them but kortingscamera seems to use an other (cloudflare) IP ?
And gogotrip.com is slowwww..... (DNS used here is 1.1.1.1)
PING www.kortingcamera.nl
Pinging www.kortingcamera.nl.cdn.cloudflare.net [104.28.16.89] with 32 bytes of data:
Reply from 104.28.16.89: bytes=32 time=7ms TTL=60
Reply from 104.28.16.89: bytes=32 time=6ms TTL=60
Reply from 104.28.16.89: bytes=32 time=7ms TTL=60
Reply from 104.28.16.89: bytes=32 time=7ms TTL=60
Ping statistics for 104.28.16.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 7ms, Average = 6ms
tracert www.kortingcamera.nl
Tracing route to www.kortingcamera.nl.cdn.cloudflare.net [104.28.17.89]
over a maximum of 30 hops:
1
And gogotrip.com is slowwww..... (DNS used here is 1.1.1.1)
PING www.kortingcamera.nl
Pinging www.kortingcamera.nl.cdn.cloudflare.net [104.28.16.89] with 32 bytes of data:
Reply from 104.28.16.89: bytes=32 time=7ms TTL=60
Reply from 104.28.16.89: bytes=32 time=6ms TTL=60
Reply from 104.28.16.89: bytes=32 time=7ms TTL=60
Reply from 104.28.16.89: bytes=32 time=7ms TTL=60
Ping statistics for 104.28.16.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 7ms, Average = 6ms
tracert www.kortingcamera.nl
Tracing route to www.kortingcamera.nl.cdn.cloudflare.net [104.28.17.89]
over a maximum of 30 hops:
1
thank you for your kind work.
We just enabled cloudflare for www.kortingcamera.nl, now we can access the website by using the t-mobile internet directly, and speed is really quick.
For gogotrip,com, we did not enable cloudflare for this website, so we still can not access it by using the t-mobile internet directly.
However, by using my mobile phone or another internet provider (not from t-mobile), open this website is no problem at all, and load speed is very quick (within 1-2 seconds).
I am glad that finally you can reproduce the load problem of gogotrip.com by using t-mobile internet. On your side, it takes more than 30 seconds. On our side, we got timeout error. So it seems that the problem is the same.
Based on these conditions, I think there is really something wrong with t-mobile internet.
For changing the dns names on t-mobile router, I mean there is no option to change them. The interface from the router does not have a button or link to change these dns names.
We just enabled cloudflare for www.kortingcamera.nl, now we can access the website by using the t-mobile internet directly, and speed is really quick.
For gogotrip,com, we did not enable cloudflare for this website, so we still can not access it by using the t-mobile internet directly.
However, by using my mobile phone or another internet provider (not from t-mobile), open this website is no problem at all, and load speed is very quick (within 1-2 seconds).
I am glad that finally you can reproduce the load problem of gogotrip.com by using t-mobile internet. On your side, it takes more than 30 seconds. On our side, we got timeout error. So it seems that the problem is the same.
Based on these conditions, I think there is really something wrong with t-mobile internet.
For changing the dns names on t-mobile router, I mean there is no option to change them. The interface from the router does not have a button or link to change these dns names.
I think T-Mobile is currently experiencing technical difficulties. https://community.t-mobile.nl/t-mobile-thuis-algemeen-490/is-er-een-storing-bij-t-mobile-thuis-op-internet-tv-of-vaste-telefonie-284385
Currently both your websites are responding properly again from my end (www.kortingcamera.nl about 350ms and www.gogotrip.com 700-1000ms). Perhaps, wait until everything has cleared up, before making any drastic changes.
Good Luck!
Currently both your websites are responding properly again from my end (www.kortingcamera.nl about 350ms and www.gogotrip.com 700-1000ms). Perhaps, wait until everything has cleared up, before making any drastic changes.
Good Luck!
sure, thanks for your answer, we will do a test after 1-2 days to see if the problem is solved.
the problem has bee resolved by flush the dns cache in the computer. thanks for your kind help.
Great topic and perfect replies! Thanks to you, @emukang for coming back here and explaining what your solution was. Greatly appreciated!
I used the solution from here
https://help.dreamhost.com/hc/en-us/articles/215680477-Flush-DNS-overview
So on windows, use this command
On mac, use this command
On iphone, turn on airplane mode, and turn off it.
https://help.dreamhost.com/hc/en-us/articles/215680477-Flush-DNS-overview
So on windows, use this command
code:
C:\Users\username> ipconfig /flushdns
On mac, use this command
code:
macbook$ sudo killall -HUP mDNSResponder;sudo killall mDNSResponderHelper;sudo dscacheutil -flushcache
On iphone, turn on airplane mode, and turn off it.
And that is the nice thing about Linux ... standard it does not enable DNS caching, so no flushing needed
But for those that have enabled it on Linux (by accident) read here the instruction
Reageer
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.