topic Re: Name lookup timing out in Integration and Testing

Name lookup timing out

junger — Sun, 03 Jun 2012 16:45:35 GMT

Hi all -

I'm having a issue where, all of a sudden, my shopping cart (Shopp) is spitting back an error saying "Authorize.net name lookup timed out".

There's no Auth.net response code (which the live chat people say they need in order to assist). This is what's showing up in my error logs:

[Sun Jun 03 09:30:01 2012] [error] [client MY.IP.ADDRESS] * name lookup timed out, referer: https://www.globalbeads.com/shop/confirm-order/

[Sun Jun 03 09:30:01 2012] [error] [client MY.IP.ADDRESS] * Couldn't resolve host 'secure.authorize.net', referer: https://www.globalbeads.com/shop/confirm-order/

It was working totally fine last week. There were no changes to the site that would have caused this.

Is something going on with the Auth.net DNS? Is there something new I need to set to "allow" transactions from my domain?

(MediaTemple shared server, PHP 5.2.17, Wordpress)

Thanks for your help.

Re: Name lookup timing out

RaynorC1emen7 — Sun, 03 Jun 2012 20:16:09 GMT

Can you get on the https://secure.authorize.net/gateway/transact.dll on a browser from your PC? from the site server?

Re: Name lookup timing out

junger — Mon, 04 Jun 2012 00:03:56 GMT

@RaynorC1emen7 wrote:
Can you get on the https://secure.authorize.net/gateway/transact.dll on a browser from your PC? from the site server?

I can via my browser, yes - with the following error:

The following errors have occurred.

(13) The merchant login ID or password is invalid or the account is inactive.

What's the best way to test from the site server?

Re: Name lookup timing out

RaynorC1emen7 — Mon, 04 Jun 2012 11:38:43 GMT

The following errors have occurred.

(13) The merchant login ID or password is invalid or the account is inactive.

Mean you get to the URL ok. Can you do the same on the hosted site server? Try another DNS server?

Re: Name lookup timing out

junger — Mon, 04 Jun 2012 15:59:07 GMT

@RaynorC1emen7 wrote:
The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive.
Mean you get to the URL ok. Can you do the same on the hosted site server? Try another DNS server?

I get their from my browser, yes, but that's obviously not the same as the server.

SSHing into the server and running curl resulted in this (from MediaTemple)

------

As a courtesy, I went ahead and ran the following command to try and connect to secure.authorize.net:

curl secure.authorize.net

This was unsuccessful, however, I was able to connect to https://secure.authorize.net when using the curl command. You may need to contact authorize.net for more information on why your script is not working correctly.

-------

Re: Name lookup timing out

RaynorC1emen7 — Mon, 04 Jun 2012 16:22:55 GMT

Does it have something like the ping command in windows? or is curl it?

can you try other website like curl www.google.com?

Re: Name lookup timing out

junger — Mon, 04 Jun 2012 18:46:19 GMT

@RaynorC1emen7 wrote:
Does it have something like the ping command in windows? or is curl it?
can you try other website like curl www.google.com?

First, thanks for your help in responding to this. It's been really tough to deal with, so I appreciate it.

I SSH'd into the site and ran curl for www.google.com, and it was fine. I also curled secure.authorize.net and was unsuccessful in getting to it. I was able to successfully curl https://secure.authorize.net - so I'm thinking maybe it has something to do with the secure site?

I'm not sure. Thanks for your help in advance.

Re: Name lookup timing out

RaynorC1emen7 — Mon, 04 Jun 2012 19:34:30 GMT

There is the https://accounts.google.com

What about curl to http://www.authorize.net/ on the server?

authorize.net seem to start with 64.94.118.x

Re: Name lookup timing out

eolsen — Mon, 04 Jun 2012 22:01:41 GMT

I am experiencing the same problem (also with Shopp.) It just started on 5/31/12 and I've not changed any settings or files. I spoke with MediaTemple (my host) and they were able to successfully reach "https://secure.authorize.net/gateway/transact.dll" but it gave the "Error 13" which says "(13) The merchant login ID or password is invalid or the account is inactive."

I also spoke with Authorize.net support but they didn't help at all.

I've triple-checked the LoginID and the URL and it's all correct. What else could it be?

Re: Name lookup timing out

RaynorC1emen7 — Mon, 04 Jun 2012 23:07:31 GMT

Can you look at the web broswer page source if you are using SIM or DPM?

Or log the params just before you send to "https://secure.authorize.net/gateway/transact.dll" for AIM?

Re: Name lookup timing out

mogmachine — Sat, 09 Jun 2012 17:06:51 GMT

The fix for this is frustratingly simple, ..add:

define(SHOPP_GATEWAY_TIMEOUT, 75);

to wp-config.php ;) ....it is a timeout issue with mediatempleconnecting to the payment gateway, ...

MediaTemple ran several tests this past week and determined its on Authorizenet's end. However they weren't responsive.

The fix above basically commands Shopp to wait for an extended period of time for a response back from Authorizenet.

That is it, ..fixed, ..but if you wan the technical explanation from mt:

BEGIN -->

I looked into this and found something interesting. It looks like the timeout is actually occurring on the PTR record lookup for the IP that secure.authorize.net resolves too, not the domain itself. There seems to be an issue with the configuration of the '118.94.64.in-addr.arpa' sub domain that holds that PTR record.

The dns servers pointed too by the currently cached NS records that manage that /24's PTR records do not seem to respond with any results. They also do not respond properly with NS records for '118.94.64.in-addr.arpa' pointing to themselves. Even worse it also looks like the name servers for the parent sub domain are missing the glue records.

I can duplicate the slow response with any PTR record within 64.94.118.0/24, but not any IP outside of that. For now it looks like authorize.net is having some issues with the authoritative DNS for its PTR records and that is causing your slow curl times.

It should also be noted that secure.authorize.net resolves to two IPs, and the PTR record for one is currently cached on most of the local caches. However, if these issues aren't fixed then once that record drops of our caches this issue may become even more frequent.