The Stripe Terminal SDK is encountering DNS errors when connecting to an Internet Reader
- When a Stripe Terminal reader is assigned an IP address by your router’s DHCP server, the reader will connect to Stripe to obtain an SSL certificate associated with a hostname (similar to 192-168-1-55.abc123.device.stripe-terminal-local-reader.net). The Stripe Terminal SDKs will use that hostname to communicate with the reader.
- Stripe hosts a DNS server that resolves our reader-specific hostnames to IP addresses on your LAN.
- For example, the DNS server would resolve the above hostname to 192.168.1.55.
- Some DNS servers - (usually set up by ISPs), block authoritative DNS listings that resolve to local IP addresses. This means that the Stripe Terminal SDKs will not be able to communicate with the reader, even if the reader is accessible on the local network. You might see this manifest as a DNS error or a connectivity error from the Terminal SDKs.
- To test whether the reader is accessible on the local network, you can ping the reader’s IP address from the command line: $ ping 192.168.1.55
- To test whether your DNS provider can resolve Stripe Terminal device hostnames, you can run nslookup from the command line: $ nslookup 192-168-1-55.device.stripe-terminal-local-reader.net
- If the nslookup command fails but the ping command succeeds, it means your DNS provider is blocking local IP addresses from resolving.
- To mitigate this, you can change the DNS provider either in your point of sale device’s network settings or in your router’s networking settings.
- Some DNS providers block DNS resolution of local IP addresses. Stripe Terminal uses the partially qualified domain name *.[random-string].device.stripe-terminal-local-reader.net which resolves to the local IP address of your card reader. If your DNS provider blocks local IP resolution, you should change your network settings to use one of the following DNS providers:
-
-
Cloudflare DNS (1.1.1.1 and 1.0.0.1)
-
Google Public DNS (8.8.8.8 and 8.8.4.4)
-
Instructions for changing your DNS provider vary by device and router; please consult the user manual for your device to learn more.
Your WiFi network must use WPA-Personal or WPA2-Personal encryption and be password protected. The WisePOS E does not support non-password-protected networks, enterprise networks and IPV6 networks. Follow the troubleshooting steps to diagnose issues with IPV6 networks. Non-password-protected networks or enterprise networks are not supported. If needed, you can set a static IP on the device from the Wireless settings screen.
FAQ
When a Customer's card declines, how do I cancel the transaction and begin again? There is no cancel button.
You will need to restart the device. To do that, press the button located on the right side of the terminal and select the "Restart" option. The device will take approximately 45 seconds to complete the restart process.