Alternative products have been around for a while. A steel based fiber reinforcement from the same lab @ UofM is commercially available from PolyTorx and offers even better performance in many applications. http://www.polytorx.com/
I'm amazed the loss rate isn't higher. The setup of their sms gateway for email is awful. I've sent in excess of a dozen messages over the past 4 years askign them simply to add a secondary mx and move on of the dns servers for mobile.att.net to another subnet. Everyone I've talked to has been clueless.
Infrastructure 101 teaches you the dangers of putting everything in a single subnet, yet despite the billions of dollars AT&T wireless has spent they can't pony up a few bucks for a secondary MX and modify their DNS setup to be safer:
; > DiG 8.3 > mobile.att.net mx;; res options: init recurs defnam dnsrch;; got answer:;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 2;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3;; QUERY SECTION:;; mobile.att.net, type = MX, class = IN;; ANSWER SECTION: mobile.att.net. 29m2s IN MX 10 mta01.cdpd.airdata.com.;; AUTHORITY SECTION: mobile.att.net. 29m2s IN NS mesdns02.cdpd.airdata.com. mobile.att.net. 29m2s IN NS mesdns01.cdpd.airdata.com.;; ADDITIONAL SECTION: mta01.cdpd.airdata.com. 29m3s IN A 199.88.234.33 mesdns02.cdpd.airdata.com. 1d15h24m54s IN A 199.88.234.125 mesdns01.cdpd.airdata.com. 1d14h12m1s IN A 199.88.234.61;; Total query time: 30 msec;; MSG SIZE sent: 32 rcvd: 164
There are some folks taking the modular approach and developing systems that offer a sub-set of these features. InfoMove http://www.infomove.com/ and Wingcast http://www.wingcast.com/ come to mind.
Slashdot Mirror
Alternative products have been around for a while. A steel based fiber reinforcement from the same lab @ UofM is commercially available from PolyTorx and offers even better performance in many applications. http://www.polytorx.com/
I'm amazed the loss rate isn't higher. The setup of their sms gateway for email is awful. I've sent in excess of a dozen messages over the past 4 years askign them simply to add a secondary mx and move on of the dns servers for mobile.att.net to another subnet. Everyone I've talked to has been clueless.
;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 2 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; QUERY SECTION: ;; mobile.att.net, type = MX, class = IN ;; ANSWER SECTION: ;; AUTHORITY SECTION: ;; ADDITIONAL SECTION: ;; Total query time: 30 msec ;; MSG SIZE sent: 32 rcvd: 164
Infrastructure 101 teaches you the dangers of putting everything in a single subnet, yet despite the billions of dollars AT&T wireless has spent they can't pony up a few bucks for a secondary MX and modify their DNS setup to be safer:
; > DiG 8.3 > mobile.att.net mx
mobile.att.net. 29m2s IN MX 10 mta01.cdpd.airdata.com.
mobile.att.net. 29m2s IN NS mesdns02.cdpd.airdata.com.
mobile.att.net. 29m2s IN NS mesdns01.cdpd.airdata.com.
mta01.cdpd.airdata.com. 29m3s IN A 199.88.234.33
mesdns02.cdpd.airdata.com. 1d15h24m54s IN A 199.88.234.125
mesdns01.cdpd.airdata.com. 1d14h12m1s IN A 199.88.234.61
There are some folks taking the modular approach and developing systems that offer a sub-set of these features. InfoMove http://www.infomove.com/ and Wingcast http://www.wingcast.com/ come to mind.