Connector DNAT Pooling With App Probing for DNS Load Balancing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional DNS load balancing methods fail to efficiently manage dynamic and complex traffic patterns, leading to inefficiencies and potential downtime when dealing with network architectures involving Zero Trust Network Access (ZTNA) connectors and network address translation (NAT) routers.

Innovation Solution

Implementing a system that combines dynamic DNAT pooling and application server probing to mimic DNS load balancing logic, ensuring traffic is distributed across multiple application servers based on health and availability, even when NAT is present.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional DNS load balancing methods are used, then DNS server queries are frequent, but load balancing efficiency deteriorates in complex network architectures with NAT routers

Engineering Contradiction:

Improveload balancing efficiencyVSAvoidDNS server query overhead

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary DNS resolution and caching of IP address mappings before actual traffic needs to be load-balanced. The NAT router pre-establishes the mapping between domain names and multiple IP addresses, storing them locally so that subsequent load balancing decisions can be made without repeated DNS server queries, thus reducing query overhead and improving efficiency

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The NAT router acts as an intermediary between the DNS server and the load balancing process. Instead of clients directly querying the DNS server for each load balancing decision, the NAT router intercepts DNS queries, resolves them locally, and maintains a cached mapping, thereby mediating between DNS resolution and actual traffic distribution to reduce server load

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If static DNAT entries are used, then configuration is simple, but adaptability to dynamic traffic patterns and server availability deteriorates

Engineering Contradiction:

Improveadaptability to dynamic traffic patternsVSAvoidDNAT pool management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system transitions from static DNAT entries to dynamic DNAT pool management where the mapping between domain names and IP addresses can change in real-time based on server availability and traffic conditions. The NAT router continuously monitors server health and dynamically updates the DNAT pool to reflect current operational status, enabling adaptation to dynamic traffic patterns and failover scenarios

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the NAT router monitors server response times and availability, and uses this information to dynamically adjust the DNAT pool composition. When servers become unavailable or respond slowly, the system receives feedback and automatically removes or weights them differently in the load balancing algorithm, maintaining adaptability through continuous monitoring and adjustment

Inventive Principle:

Principle #23Feedback

3Speed

If DNS re-resolution is performed frequently, then load balancing responsiveness improves, but network traffic overhead increases

Engineering Contradiction:

Improveload balancing responsivenessVSAvoidnetwork traffic overhead

Core Design Contradiction:

SpeedVSLoss of energy

Solution Approach 1:

The system performs DNS resolution in advance and caches the results locally at the NAT router. Instead of frequently querying the DNS server, the router pre-resolves domain names to multiple IP addresses and stores them in a local cache, providing fast load balancing decisions without repeated network queries, thus maintaining responsiveness while reducing traffic overhead

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements periodic DNS re-resolution at optimized intervals rather than continuous or frequent queries. The NAT router refreshes its DNS cache periodically based on TTL (Time To Live) values and cache expiration policies, balancing the need for up-to-date load balancing information with the cost of network traffic, achieving responsiveness without excessive overhead

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS20260032115A1Intelligent DNS load balancing using combination of dynamic DNAT pool and application probing in connector based solution for private application access

Publication Date: 2026.01.29 PALO ALTO NETWORKS INC

AI summary

The present application discloses a method, system, and computer system for providing intelligent DNS load balancing using a combination of a dynamic DNAT pool and application providing in a connector-based solution for private application access. The method includes: (a) performing a DNS re-resolution for resolving an application Fully Qualified Domain Name (FQDN) to obtain a plurality of IP addresses for a plurality of application servers, (b) performing periodic application server probing, and (c) dynamically updating a destination network address translation (DNAT) to provide DNS load balancing for application traffic. The DNAT is updated based at least in part on one or more of the DNS re-resolution and the application server probing.