Wildcard DNS Forwarding for Multi-Data-Center Application Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack a user-friendly solution for tenants to identify and manage resources with wildcard domain names deployed across multiple data centers, leading to complex DNS forwarding configurations and inefficient resource discovery and onboarding.

Innovation Solution

A network controller and forwarding service manage wildcard domain name configurations, allocating anycast IP addresses to application connectors, and orchestrating DNS requests and load balancing across data centers to automate resource discovery and onboarding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual DNS forwarding configuration is used for wildcard domain names across multiple data centers, then resource discovery and onboarding can be achieved, but the configuration complexity and time consumption increase significantly

Engineering Contradiction:
Improveautomated resource discovery and onboardingVSAvoidDNS forwarding configuration complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system enables automated resource discovery and onboarding where the DNS forwarding service automatically detects, discovers, and onboards applications across data centers without manual configuration. The service self-manages the entire process from receiving wildcard domain name configurations to automatically discovering applications and setting up DNS forwarding rules, eliminating the need for manual intervention while reducing configuration complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The network controller pre-configures wildcard domain name mappings to data center IP addresses before actual application deployment. This preliminary configuration enables the DNS forwarding service to automatically route DNS requests for any matching domain names to the appropriate data centers, establishing the automated discovery and onboarding framework in advance without requiring complex per-application configurations

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If wildcard domain name configurations are deployed across multiple data centers, then resource availability and scalability improve, but the difficulty of managing and discovering resources increases

Engineering Contradiction:
Improvemulti-data center resource deployment flexibilityVSAvoidresource discovery difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The DNS forwarding service acts as an intermediary between DNS resolvers and multiple data centers. It receives DNS requests for wildcard domain names, automatically determines which data centers should receive these requests based on pre-configured mappings, and forwards them accordingly. This intermediary approach simplifies resource discovery by abstracting the complexity of multi-data center management from the DNS resolution process while maintaining flexible deployment across data centers

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the DNS forwarding process into distinct components: wildcard domain name configuration management, DNS request routing logic, and data center-specific application discovery. Each data center operates independently with its own application connectors, allowing resources to be discovered and managed in isolated units while maintaining overall system flexibility and reducing the difficulty of detecting and measuring individual resources

Inventive Principle:
Principle #1Segmentation

3Productivity

If manual configuration methods are used for DNS forwarding, then system simplicity is maintained, but productivity and efficiency of resource management decrease

Engineering Contradiction:
Improveresource management efficiencyVSAvoidconfiguration simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The DNS forwarding service automatically performs resource discovery, DNS request routing, and application onboarding without requiring manual configuration for each application. The service self-manages the entire workflow from receiving wildcard domain name configurations to automatically discovering applications across data centers and setting up appropriate DNS forwarding rules, significantly improving resource management efficiency while maintaining operational simplicity through automation

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The DNS forwarding service provides universal functionality that handles multiple tasks simultaneously: it manages wildcard domain name configurations, routes DNS requests to appropriate data centers, discovers applications automatically, and onboards new resources. This multi-functional approach improves productivity by consolidating multiple manual processes into a single automated service while maintaining ease of operation through a unified configuration interface

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250323892A1Multiple data center compatible deployment of applications matching a wildcard domain name
Publication Date: 2025.10.16 PALO ALTO NETWORKS INC
  • US20250323892A1 patent drawing
  • US20250323892A1 patent drawing
  • US20250323892A1 patent drawing

AI summary

A network controller communicates a wildcard domain name defined by a tenant and IP addresses of data centers for which a tenant has configured that wildcard to network elements of a network fabric through which the data centers are accessible. Each network element creates a rule to forward DNS requests with FQDNs that match the wildcard to each data center IP address. When a network element receives a DNS request indicating a FQDN that matches the wildcard, the network element forwards the DNS request to each data center IP address. Each data center element associated with one of the IP addresses receives the DNS request and determines if the FQDN can be resolved to an IP address in that data center. Data center elements for which domain name resolution is successful notify the network controller, which onboards the resource corresponding to the FQDN in that data center.