REF:
http://blackberry.org/developers/for...=1&thread=3889
I'm getting it too and the insinuation that it's a DNS issue is confirmed when you use an IP address instead of an URL. It seems one of CINGULARs pathways can't resolve DNS names causing every other time to come back with an exception. Probably just in certain regional area (Philly this one is in) and non-BES WAP gateway of course.
My biggest issue is lordy lord how long CINGULAR takes to fix it. I'll program around it for now to avoid hard coding IP addresses in the clients but let me know where to send Cingular my invoice...