This week we updated the DNS entries for our streaming endpoints, including stream.twitter.com, sitestream.twitter.com, and userstream.twitter.com. We are planning on turning off the old IPs tomorrow: Thursday, April 26, 2012.
If you are currently maintaining long lived connections to any of our streaming services and caching DNS entries make sure that you've picked up the new value or else you may have issues reconnecting after Thursday.
Please use this discussion thread if you have any questions.
Replies
Can you tell us what the old IPs vs the new IPs are, just so we can be certain that we're picking up the new DNS entries? :-)
You should see:
* sitestream.twitter.com: 199.59.148.228
* stream.twitter.com: 199.59.148.229
* userstream.twitter.com: 199.59.148.241
Keep in mind that these IPs should not be hardcoded into your application.
Fantastic thanks - just wanted to make sure that no old IPs were being cached. Hate seeing hardcoded IPs ;-)
199.59.148.241
thanx
same
I don't see those IPs currently:
$ dig sitestream.twitter.com @ns4.p34.dynect.net.
; <<>> DiG 9.6-ESV-R4 <<>> sitestream.twitter.com @ns4.p34.dynect.net.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5341
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;sitestream.twitter.com. IN A
;; ANSWER SECTION:
sitestream.twitter.com. 30 IN A 199.59.148.137
;; AUTHORITY SECTION:
twitter.com. 86400 IN NS ns1.p34.dynect.net.
twitter.com. 86400 IN NS ns2.p34.dynect.net.
twitter.com. 86400 IN NS ns3.p34.dynect.net.
twitter.com. 86400 IN NS ns4.p34.dynect.net.
;; Query time: 13 msec
;; SERVER: 204.13.251.34#53(204.13.251.34)
;; WHEN: Fri Jun 29 11:12:25 2012
;; MSG SIZE rcvd: 142
Can u explain what that means?
If your application caches DNS entries, you should clear the cache and reconnect to the Streaming API. Whether you are affected will depend on the infrastructure you use. For example, JVM based applications (typically using Java) may need to restart the JVM to be able to reconnect (see http://www.verisigninc.com/assets/stellent/030957.pdf for info).
Could i get RT information by API like your service(RT Counts & RT User info.)??
Its all confusing I don't understand the meaning can you please explain the meaning