codeheld-terminal-dns | Stripe Developers | Page 1

crisp compass Feb 7, 2022, 2:20 PM

#

Hi there 👋 I've not run into this personally, but it seems expected if your DNS is blocking local IP addresses from resolving.

Have you tried changing the DNS that your route is using?

Reference: https://support.stripe.com/questions/the-stripe-terminal-sdk-is-encountering-dns-errors-when-connecting-to-an-internet-reader

karmic elbow Feb 7, 2022, 2:22 PM

#

Changing the DNS would work, but I don't want to do that for all our customers 😉

#

Does anyone know when and how the random-string in *.[random-string].device.stripe-terminal-local-reader.net changes?

crisp compass Feb 7, 2022, 2:50 PM

#

I'm not sure off the top of my head, can you help me understand why you're asking?

karmic elbow Feb 7, 2022, 3:03 PM

#

I'd try to implement a fixed CNAME ("customerid.ourdomain.com") to that stripe-terminal-local-reader.net domain - so that I can whitelist our CNAME domain in the router setting. I cannot whiteliste the stripe domain because it doesnt support wildcards.

crisp compass Feb 7, 2022, 3:26 PM

#

Gotcha, unfortunately I'm not sure when those values change and have not been able to locate anything on it.

karmic elbow Feb 7, 2022, 3:28 PM

#

thanks anyway

crisp compass Feb 7, 2022, 3:32 PM

#

Any time, sorry I couldn't be of more assistance.

full ledge Feb 7, 2022, 3:34 PM

#

@karmic elbow if you're still around, can you explain more about how you're trying to handle this? Ultimately you need to ensure the *.terminal-local-reader.net hostnames resolve, as those are what the Terminal SDKs will be using internally. Those full hostnames include both a random string and the local IP address.

#

You might also want to look at our newer Server Driven integration pattern: https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=server-driven&reader-type=simulated

#

Which doesn't depend on any such local device connections

#codeheld-terminal-dns