Link to home
Create AccountLog in
Avatar of ZuZuPetals
ZuZuPetalsFlag for United States of America

asked on

The remote name could not be resolved: 'api-aa-3t.paypal.com'

I'm using the PayPal SDK for .Net and when we attempt to charge a credit card we get this error message:
The remote name could not be resolved: 'api-aa-3t.paypal.com'
It only fails 1/3 of the time.  

I assume "remote name could not be resolved" is a DNS problem?

Is it safe to assume that 1/3 of the time our local code is contacting a DNS server that does NOT have an entry for api-aa-3t.paypal.com  and the other 2/3 of the time it his a different DNS server that DOES have an entry?

Can anyone speculate why this error would happen periodically/randomly?
Avatar of Chris Dent
Chris Dent
Flag of United Kingdom of Great Britain and Northern Ireland image

What are you using to resolve the name? System.Net.Dns?

If so, it's likely that you are using the DNS servers configured on that system (ipconfiguration). You can test each of those individually if that is the case.

Chris
SOLUTION
Avatar of Kirti_Singh
Kirti_Singh

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of ZuZuPetals

ASKER

Gosh, I'm not very technical when it comes to DNS/NS stuff.  I'm just using the PayPal library written in .Net.  No idea what class it's calling.

According to the DNS properties of the server, the primary and secondary DNS servers we use from Time Warner/Road Runner are:

24.25.5.60
24.25.5.61
Here is something important:
When I do a trace route I get timeouts.  Can you try to see if you guys get timeouts?

One thing that baffles me is that this tracert fails every time, yet 60% of the time we can process the credit card payments using the PayPal library... you'd think *that* would fail every time, too.
C:\>tracert api-aa-3t.paypal.com

Tracing route to api-aa-3t.paypal.com [66.211.168.125]
over a maximum of 30 hops:

  1    12 ms     9 ms     7 ms  10.108.64.1
  2     8 ms     7 ms     8 ms  chrlncmh-qt62.carolina.rr.com [24.93.75.110]
  3     6 ms     8 ms     8 ms  ge-2-2-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.141]
  4    12 ms    13 ms    12 ms  ae-3-0.cr0.atl20.tbone.rr.com [66.109.6.82]
  5    17 ms    16 ms    16 ms  ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
  6    12 ms    12 ms    22 ms  216.156.108.65.ptr.us.xo.net [216.156.108.65]
  7    42 ms    27 ms    29 ms  vb2002.rar3.washington-dc.us.xo.net [207.88.13.162]
  8    35 ms    37 ms    35 ms  te-3-0-0.rar3.nyc-ny.us.xo.net [207.88.12.73]
  9    53 ms    58 ms    53 ms  207.88.14.62.ptr.us.xo.net [207.88.14.62]
 10    78 ms   244 ms    81 ms  207.88.184.6.ptr.us.xo.net [207.88.184.6]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.

Open in new window

ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Thanks for all your support!!!

This was the problem: We have a firewall that is not allowing larger DNS responses through.  When the reply size increased due to DNSSEC responses it stopped working.