DNS Failover in Pay.POS (en)
Smart DNS failover ensures Pay.POS automatically selects the fastest and most suitable DNS server for a reliable network connection.
Pay.POS uses an intelligent DNS failover mechanism to minimize network-related issues and maximize application availability.
For every DNS lookup, the application attempts the configured DNS servers in a fixed order. If a DNS server does not respond within 50 ms, Pay.POS automatically switches to the next server in the list. Once the TTL (Time To Live) of the DNS record expires, the process is repeated so the application can again select the fastest and most appropriate DNS server.
DNS server priority
Pay.POS uses the following DNS server order:
| Priority | DNS Server | Reason |
|---|---|---|
| 1 | 8.8.8.8 (Google Public DNS) | Preferred by default due to its excellent reliability, performance, and global availability. |
| 2 | Router DNS server (DHCP) | Improves compatibility with corporate networks that only allow DNS requests through the local DNS server. |
| 3 | 1.1.1.1 (Cloudflare DNS) | Provides an additional fallback if the previous DNS servers are unavailable. |
Why this order?
Google Public DNS is used as the primary DNS server because of its outstanding performance and reliability. However, some corporate networks only permit DNS traffic through the DNS server provided by the local router. For this reason, Pay.POS automatically falls back to the DNS server received via DHCP. If that server is also unavailable or unresponsive, the application switches to Cloudflare DNS.
This approach ensures that Pay.POS continues to operate reliably across both public internet connections and secured corporate networks without requiring any manual configuration.