I've noticed some odd (to me, at least) behavior when verifying new applications in my software firewall. When a connection is created for the first time, I'm prompted with a dialog telling me the remote address & IP before I allow the application access.
With my previous ISP, these dialogs have never concerned me as it would normally display an address I'm aware of (eg. blizzard.com). However, ever since I switched to Sonic.net, I've noticed that some new connections will display *.static.sonic.net addresses rather than the endpoints I would expect. This is behavior I've never seen before and, while it doesn't raise any real caution flags to me, I'm curious as to why I would be seeing *static.sonic.net addresses in place of a connection's actual destination. With my limited knowledge of the ISP's workings, it sounds to me like some sort of proxy or other sorts of filtering. Should this sort of thing bother me or is it just something I should get used to seeing?
With my previous ISP, these dialogs have never concerned me as it would normally display an address I'm aware of (eg. blizzard.com). However, ever since I switched to Sonic.net, I've noticed that some new connections will display *.static.sonic.net addresses rather than the endpoints I would expect. This is behavior I've never seen before and, while it doesn't raise any real caution flags to me, I'm curious as to why I would be seeing *static.sonic.net addresses in place of a connection's actual destination. With my limited knowledge of the ISP's workings, it sounds to me like some sort of proxy or other sorts of filtering. Should this sort of thing bother me or is it just something I should get used to seeing?