Sonic Netblocks

[wa2ibm]

I've recently changed my network somewhat to move from a single multi-WAN router to two single-WAN routers to handle both my Cable connection and my Sonic DSL connection. The primary router is connected to my cable connection and has DHCP enabled. The second router has DHCP turned off and resides at a different LAN address. My web/mail/file server has its network hard coded to point to the Sonic router (since Comcast doesn't like servers).

However, when another machine on my network addresses a Sonic address block, I have static routes in the primary router that will send those requests to the Sonic router. My question is, how to determine what netblocks Sonic owns? I'm primarily concerned with the address blocks used for servers at Sonic. I've deduced eight blocks so far. Are there other major blocks that I'm missing?

64.142.0.0/17
69.12.128.0/17
70.36.128.0/17
75.101.0.0/17
76.191.128.0/17
173.228.0.0/17
200.201.224.0/24
209.204.128.0/18

Thanks!

[wa2ibm]

Thanks for the quick offline response. . .

[dane]

The challenge here is that it's a moving target - the address space is constantly changing or expanding. So, no way to really statically list these that will be useful in the long term.

[wa2ibm]

Dane:
Yes, I realize that. I'm really interested in the primary blocks where your servers are located. I know those can move as well, but I'm sure that I'll notice those soon enough and be able to modify my routing tables. It's not as if I won't be able to access the servers if they move, it'll just be via a more indirect route. Unless, if course, any of the servers are locked out from access off-network. My mail server will be still be able to send mail OK, since it's tied directly to the router on the Sonic connection.

Thanks for pointing it out, however.