Recent searches
No recent searches
Proxy error: DNS resolution error
Posted Jul 31, 2023
We're using Zendesk's Secure Settings feature, but it fails in error, "Proxy error: DNS resolution error". The domain is subdomain of openai.azure.com, like oursubdomain.openai.azure.com.
- secure:true in ZAFClient request options
- set "domainWhitelist" in manifest.json
- without secure:true option, it works. This means the subdomain and parameters are correct.
- installed the app as private app
What can we do next to solve this error?
0
8
8 comments
Greg Katechis
Hi Megumi! Do you have CORS set to false in your request options? If you do, could you share the full request snippet, along with the options?
1
Megumi Nakamura
Hi Greg, thank you for the comment.
I tried with `cors: false`, but it also failed in the same DNS error. This is the request I am using.
The "api-key" param is `{{setting.api_key}}` (api_key param is in the parameters of manifest.json), but I tried both with the raw value and `{{setting.api_key}}`.
If I remove the line "cors: false" (means use only secure:true), this failed in DNS error.
If I remove the line "secure: true" and use api-key with raw value (means use only cors:false), this request works.
Can you find something?
0
Greg Katechis
dig +trace e...openai.azure.com
or on Windowsnslookup -debug e...openai.azure.com
, you'll see the full resolution path.Since this is working when you're not passing it through our proxy (by removing
secure: true
), I'm assuming that there is something deeper that occurs on this particular path, so I'm going to bring my findings to that team to hear what they have to say. I'll drop you a line when I hear back from them, hopefully later this week.0
Megumi Nakamura
Hi Greg, thank you for the update :)
0
Greg Katechis
For the time being, the only workaround that I can think of would be building out a middleware layer that you can use to pass the secure request to, let that layer send out the request to Azure and receive the response back and then pass it back to the app. I know that's not a great solution, it's just the only thing I can think of it right now.
Looking forward to your response on business impact!
0
Megumi Nakamura
Hi Greg, Thank you for information.
This investigation is for our customer and the customer has asked to support in ticket 11779265. The business impact of this issue is as described in the ticket.
And thank you for about workaround. I hope this issue fixed, but if we need to implement before that, I consider the workaround.
0
Greg Katechis
I'll keep an eye on that work as it progresses and I'll update you down the road. Let me know if you have any other questions in the interim.
0
Megumi Nakamura
thank you!
0