Severe SAIX-related routing or DNS problem

[mstevens]

There is major SAIX problem affecting clients routing at least to Verizon in the UK. Getting SAIX to address the problem is a nightmare; tell us there's no problem (tell our clients that) and often don't even bother phoning you back.

Internet Solutions are not experiencing the same problem over their network.

The problem may be DNS related, however we cannot confirm this.

Using the following SAIX settings appears to assist some of our clients:

Server name: dsl-cache.saix.net
Port: 8080
Primary DNS: 196.25.255.34
Secondary DNS: 196.25.255.3

 

[iDenTiTy]

There is major SAIX problem affecting clients routing at least to Verizon in the UK. Getting SAIX to address the problem is a nightmare; tell us there's no problem (tell our clients that) and often don't even bother phoning you back.

Internet Solutions are not experiencing the same problem over their network.

The problem may be DNS related, however we cannot confirm this.

Using the following SAIX settings appears to assist some of our clients:

Server name: dsl-cache.saix.net
Port: 8080
Primary DNS: 196.25.255.34
Secondary DNS: 196.25.255.3

I'm using the following:

208.67.222.222
208.67.220.220

I'm on Saix, and not having any problems. These addresses are from OpenDNS so use them in the mean time...

 

[fragtion]

208.67.222.222
208.67.220.220

I would discourage use of those nameservers -- they're hosted internationally, meaning it's going to take longer to resolve names with them (side effect of seemingly slower browsing), and they won't work when capped, or on any type of local-only account. It may be a good idea to set one of them as a secondary dns server though, so if the primary (SAIX) has problems, your PC will resort to that as a backup.

Without any problems I use the following DNS servers to this day, on any SAIX-based setup:
Primary: 196.43.1.11
Secondary: 196.25.1.11
(If you're in Cape Town, switch them around for better performance.)

 

[iDenTiTy]

I would discourage use of those nameservers -- they're hosted internationally, meaning it's going to take longer to resolve names with them (side effect of seemingly slower browsing), and they won't work when capped, or on any type of local-only account. It may be a good idea to set one of them as a secondary dns server though, so if the primary (SAIX) has problems, your PC will resort to that as a backup.

Without any problems I use the following DNS servers to this day, on any SAIX-based setup:
Primary: 196.43.1.11
Secondary: 196.25.1.11
(If you're in Cape Town, switch them around for better performance.)

True. I figured because he mentioned "clients", it was unlikely that they were on local only, and since it was only meant to be a temporary fix, that the issue of it being an internationally hosted DNS was no "biggie".

 

[mstevens]

SAIX has now confirmed that the problem relates to a number of their nameservers being blocked by a number of SP's internationally because of DOS attacks eminating from those servers.... 12 days later they realise this! They are now trying to get their servers un-blocked.