On Windows - not really. What's good in DNS is that you can use it to control the other home devices (xbox/playstation/phones/tablets/whatever).
At the moment there's nothing we can do for Africa, though, we will in future. Also, when we finally publish the AG DNS source code, you'll be able to use it as a self-hosted solution.
This is quite interesting and will be much appreciated. I have long been a big fan of all things open source. Your team is constantly doing a great job on all of your software and projects.
More likely to be a routing issue.If you ever face this issue again, please try executing a traceroute command: Code: $ traceroute 176.103.130.130 traceroute to 176.103.130.130 (176.103.130.130), 64 hops max, 52 byte packets 1 192-168-10-125 (192.168.10.125) 1.170 ms 1.539 ms 0.959 ms 2 195.91.185.105 (195.91.185.105) 1.302 ms 1.308 ms 1.359 ms
New servers are live for a few days already. Live: US East/West Amsterdam Singapore Russia Coming soon: Sydney Known issues: Something is wrong with EU servers connectivity, traffic is routed mostly through the russian servers. We'll try to resolve it on Wednesday.
i noticed this a few days ago. thanks avatar im going to test it out. where is the server located in US West? My traffic is being routed through US east but i would think that us west would be closer to my location. Im in colorado, currently my pings are 54 ms
Awesome news. Thanks! Are these server IP's going to be added to your website? Only reason I ask is because I have noticed a slow down of late with the IP addresses currently posted there. Thanks.
Nope, you don't need to use those IP addresses directly. We have a single subnet 176.103.130.* which leads you to the closest server, that's what anycast IP is.
Thanks I was using your service for the past few weeks and ping/traceroute was good. But recently things began to slow down, so I had to switch back to something else for now. Hopefully speed improves down the road because I woudl love to come back! Thanks.
If I ping 176.103.130.130 I still get Minimum = 356ms, Maximum = 375ms, Average = 363ms. Is that right?
here is my ping C:\Windows\system32>ping 45.76.112.113 Pinging 45.76.112.113 with 32 bytes of data: Reply from 45.76.112.113: bytes=32 time=21ms TTL=51 Reply from 45.76.112.113: bytes=32 time=21ms TTL=51 Reply from 45.76.112.113: bytes=32 time=20ms TTL=51 Reply from 45.76.112.113: bytes=32 time=21ms TTL=51 Ping statistics for 45.76.112.113: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 21ms, Average = 20ms C:\Windows\system32>ping 176.103.130.130 Pinging 176.103.130.130 with 32 bytes of data: Reply from 176.103.130.130: bytes=32 time=358ms TTL=51 Reply from 176.103.130.130: bytes=32 time=357ms TTL=51 Reply from 176.103.130.130: bytes=32 time=358ms TTL=51 Reply from 176.103.130.130: bytes=32 time=357ms TTL=51 Ping statistics for 176.103.130.130: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 357ms, Maximum = 358ms, Average = 357ms