SA DNS SERVERS
Is iBurst having DNS issues... often when I try to browse a site, or google something my IPCop returns a Connection Error. (URL cannot be retrieved), but as soon as I get IPCop to use the Open DNS servers (280.67.222.222; 208.67.220.220) then it works fine. This has been happening for a week or so.
It is a frequent occurrence in using iBurst’s DNS servers; as they are not correctly configured each time iBurst changes backhaul ISP’s, so it’s best to stay clear from iBurst’s DNS servers as you will continually have issues. This has been happening since the Chinese technicians handed over the network to the local technicians...
Try these:
First do a tracert to netgear.com to establish which backbone ISP iBurst is utilising in your area, then pick the DNS server address below best suited to your connection. Ping the DNS server, to establish the best response time... see
How to: below!
Important Tip: Always use Open DNS or alternatively iBurst’s DNS server’s as a secondary server, since iBurst does not inform its subscribers when changing backhaul ISP’s; this will allow you to “stay online”.
Saix: << Follow the link for a more comprehensive list.
igubu.saix.net 196.25.1.1 Cape Town Closed
sangoma.saix.net 196.25.1.9 Cape Town Open
wblv-ip-dns-3.saix.net 196.25.1.11 Cape Town Caching only
induna.saix.net 196.43.1.14 Rosebank Open
rrba-dns2.saix.net 196.43.1.11 Rosebank Caching only
Mweb:
196.2.16.3 - Joburg
196.2.46.254 - Cape Town
iBurst:
196.46.70.1 - Cape Town
196.30.31.193 - Joburg
Verison:
196.7.0.138 - Cape Town
196.7.142.132 - Joburg
Open DNS: (ping dns ip's to verify best response time in your area)
208.67.220.220
208.67.222.222
Google DNS: (ping dns ip's to verify best response time in your area)
8.8.8.8
8.8.4.4
For best results on iBurst in Cape Town Area:
In Cape Town: wbs-ip-dns-4.saix.net 196.43.34.190 use Open DNS as secondary
For best results on iBurst in Johannesburg Area:
In Joburg: cache02.ns.iafrica.com 196.7.142.132 use Open DNS as secondary
Alternatively:
Internet Solutions:
Primary : 168.210.2.2 - Cape Town
Secondary : 196.14.239.2 - Cape Town
Open DNS:
Primary : 208.67.220.220 - San Francisco
Secondary : 208.67.222.222 - San Francisco
AfriNic:
Primary : 168.210.2.2 - Joburg
Secondary : 196.41.0.10 - Joburg
I haven't verified the server addresses or locations lately, so please feel free to post corrections or alternative DNS servers that work more efficiently in your area, so others can benefit from your settings.
Regards
Michael
How to:
{Open a command window - click start, run, type "cmd" (without the "") press enter, then in cmd window type, "tracert netgear.com" or "tracert 206.82.202.46" (without the "")press enter.
e.g. C:\Users\Michael>tracert netgear.com
Tracing route to netgear.com [206.82.202.46]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FUDGE [192.168.1.1] - (internal network)
2 71 ms 49 ms 49 ms wbs-41-208-224-1.wbs.co.za [41.208.224.1] - (iburst assigned gateway for your connection in [])
3 72 ms 49 ms 49 ms 192.168.2.1 - (iburst routing server)
4 147 ms 44 ms 49 ms 192.168.4.37 - (iburst routing/firewall server)
5 50 ms 49 ms 55 ms 196.25.133.117 - (go to
www.whois.sc and enter the ip; there you will see who the ip address belongs to, then choose the appropriate DNS sever)
Then ping the servers, type "ping 208.67.222.222" (without the ""), e.g.
C:\Users\Michael>ping 208.67.222.222
Pinging 208.67.222.222 with 32 bytes of data:
Reply from 208.67.222.222: bytes=32 time=352ms TTL=53
Reply from 208.67.222.222: bytes=32 time=307ms TTL=53
Reply from 208.67.222.222: bytes=32 time=321ms TTL=53
Reply from 208.67.222.222: bytes=32 time=295ms TTL=53
Ping statistics for 208.67.222.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 295ms, Maximum = 352ms, Average = 318ms
C:\Users\Michael>ping 208.67.220.220
Pinging 208.67.220.220 with 32 bytes of data:
Reply from 208.67.220.220: bytes=32 time=386ms TTL=53
Reply from 208.67.220.220: bytes=32 time=360ms TTL=53
Reply from 208.67.220.220: bytes=32 time=344ms TTL=53
Reply from 208.67.220.220: bytes=32 time=337ms TTL=53
Ping statistics for 208.67.220.220:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 337ms, Maximum = 386ms, Average = 356ms
Then choose the server with the lowest time= in this case 208.67.222.222 would be the appropriate primary server.}
Advanced Tip: For more accurate results, ensure that your iBurst connection is under load (downloading) when performing the ping requests use "pathping 208.67.220.220" or use this ping command; “ping 208.67.220.220 -l 1200 –t”; run for at least the duration of 500 packets. (Ctrl C to end)
Sign up with Google