What is the new IP for us2?

[Karl]

I lost connectivity from my app after the update last night and it has been down since - apparently you changed the IP but didn't keep the old one working long enough for propagation to happen, so now I have angry users. It appears that us2 is now at 50.23.108.136, but my server hasn't seen it yet, so I'm going to have to hard-code it for now. Please confirm this IP. I'm still seeing 74.86.17.106

[Karl]

I hard-coded the IP into hominid, then ran into an SSL check error (was using https), so hard-coded the protocol to http://, but now getting an authorization error (401)... ???

[jesse]

You need to be using dns hostnames so http headers are set correctly. If you must hard code stuff, put it in a hosts file or local dns, though for this exact reason we strongly recommend against doing that.


jesse

[Karl]

Fine, but what host IP am I trying to reach? I took my hosting tech's word for what he found for the correct IP, but just checked it via DNS tools and found it wasn't what he says, but shows the IP I'm seeing on my server. I need to know what the correct IP is now for us2 before I can troubleshoot or work around this...? I don't know at this point whether I just haven't seen the DNS update or have some other problem.

On Monday, May 14, 2012 11:25:39 AM UTC-4, Karl wrote:

[Karl]

Just to clarify, I have not been hard-coding the address previous to now - I'm trying to hard-code it as a work-around for the assumption that the IP change hasn't been seen by my server yet. My server resolves us2.api.mailchimp.com to 74.86.17.106, but I have no idea at this point if that is the correct IP and I have some connectivity problem, or it isn't the IP any more. It doesn't tcptraceroute from my server, and no, my host doesn't have whitelisting in place. Everything was working until about 3:40 am. There have been no changes on my end.

On Monday, May 14, 2012 11:25:39 AM UTC-4, Karl wrote:

[jesse]

That IP is correct. You can not hard code the IP into code and expect it to work - if you feel that's necessary, see my comments about internal/local dns or host file entries. If you really do have something that has not seen the new IP, you should talk with your hosting/dns provider or network techs about respecting TTLs.


jesse

[Karl]

I'm seeing that IP everywhere, but I can only get to us2.api.mailchimp.com from 1 of 4 network locations (not including the one I need to work). The traceroute/tcptraceoute usually dies several hops into networklayer.com. I don't know what to do now. My app has been down for hours.

[Karl]

It looks like traceroute, which is all I have to use from most locations, is not crossing the last hop from 

po2.fcr02.sr04.dal01.networklayer.com to your server - I'm assuming that's because your server only responds to tcp? I have tcptraceroute from the server that I need to work, but it doesn't get anywhere. Now that I know I'm getting the right IP I'll pursue that.

On Monday, May 14, 2012 11:25:39 AM UTC-4, Karl wrote:

[Stacey Mulcahy]

Is it possible that the IP change to us2 is either slow to propagate or has failed to propagate? Seems like multiple people are having this issue today.

[Karl]

DNS propagation was a red herring for me, at least as far as network locations that I can test from - there was some confusion for a while because I was given some bad info by a tech at my hosting provider, and didn't know what the correct new IP was. Now it appears that my provider has connectivity issues to the new us2 IP - I suppose that could be DNS issues somewhere in the network in between - but I don't get even two hops off of my server (which is at MediaTemple, BTW) towards the new IP.

On Monday, May 14, 2012 11:25:39 AM UTC-4, Karl wrote:

[Stacey Mulcahy]

Further, another site that was using this functionality for some time now ( the mail chimp api unmodified) is now experiencing problems, alongside another one that is in a staging environment. 

Both are experience problems and one has been previously functioning for some time with no changes to the code base. 

[Karl]

Got an answer from MediaTemple. It seems that Mailchimp picked a new IP for us2 that has a checkered past: "After investigation, it seems that the IP address of 74.86.17.106 had been blocked by our network security team for performing scans against our network." Might turn out to be a problem for others...