- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intermittent "the remote bane cannot be resolved" during Capture Transaction
Hello all,
We have recently been experiencing an issue where occasionally we receive an error of "The remote name could not be resolved: api2.authorize.net" when during a payment capture. We haven't made any changes to our actual API calls to the server, and this seems to be randomly happening as far as we can tell.
So far research has shown it may be a DNS issue, but I want to know if there any gotchas or some other reason this may be happen. Again, it's intermittent and there doesn't seem to be a rhyme or reason as far as I can tell.
โ03-01-2021 06:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We've started experiencing the exact same thing. Intermittent exceptions of "The remote name could not be resolved: 'api2.authorize.net'".
Can someone at Authorize.net please explain what is going on?
โ03-30-2023 07:41 AM

