DNS Provisioning Gateway for Validated Record Change Deployment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing DNS update processes are prone to errors and outages, which can disrupt voice, video, and data services in networks like IMS-based 4G/5G, leading to reliability issues and customer dissatisfaction.

Innovation Solution

A DNS provisioning gateway (DPG) system that checks for errors in DNS record changes, schedules error-free updates, translates changes into protocol-specific formats, and provisions them to DNS servers, ensuring seamless and reliable DNS service delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If DNS record changes are applied directly without validation, then update speed is improved, but error rate increases causing service outages

Engineering Contradiction:

ImproveDNS update speedVSAvoidDNS service reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by validating DNS record changes before they are applied to production. The system performs syntax validation, semantic validation, and continuity checks on DNS record changes in a validation environment before approving them for deployment. This prevents erroneous changes from causing service outages while maintaining update capability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation system between DNS record change submission and deployment. The validation system acts as a mediator that checks changes for errors, validates syntax and semantics, and ensures continuity of name services before allowing changes to be applied. This intermediary layer filters out problematic changes while permitting valid updates.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If DNS record changes are validated thoroughly, then reliability is improved, but processing time increases

Engineering Contradiction:

ImproveDNS update reliabilityVSAvoidDNS update processing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the validation process into distinct phases: syntax validation, semantic validation, and continuity validation. Each phase focuses on specific aspects of DNS record changes, allowing parallel processing and optimized validation paths. This segmentation reduces overall processing time while maintaining comprehensive validation coverage.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes validation parameters dynamically based on the type of DNS record change being validated. Different validation rules and thresholds are applied depending on the record type, change magnitude, and service criticality. This parameter adaptation optimizes validation speed while maintaining reliability for each specific case.

Inventive Principle:

Principle #35Parameter changes

3Stability of the object's composition

If error checking is performed on all DNS changes, then service continuity is improved, but system complexity increases

Engineering Contradiction:

ImproveName service continuityVSAvoidValidation system complexity

Core Design Contradiction:

Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling the validation system to automatically detect, classify, and resolve certain types of DNS record errors without manual intervention. The system performs self-validation of syntax and semantics, and can automatically reject changes that would cause continuity issues. This automation reduces the need for complex manual validation processes.

Inventive Principle:

Principle #25Self-service

4Reliability

If DNS updates are scheduled and validated, then outage reduction is achieved, but update scheduling complexity increases

Engineering Contradiction:

ImproveService availabilityVSAvoidUpdate scheduling system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where validation results, error patterns, and service performance data are fed back into the scheduling system. This feedback enables intelligent scheduling decisions that avoid updating DNS records during peak service periods or when validation indicates potential risks. The scheduling system adapts based on historical data and current service conditions.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12554698B2System and method for managing domain name system records

Publication Date: 2026.02.17 AT&T INTELLECTUAL PROPERTY I L P

AI summary

Aspects of the subject disclosure may include, for example, a device including a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations of: receiving domain name system (DNS) record changes; identifying errors from the DNS record changes; discarding the DNS record changes responsive to the errors identified; scheduling the DNS record changes responsive to a lack of errors identified; translating the DNS record changes into protocol specific formats; and provisioning the protocol specific formats of the translated DNS record changes. Other embodiments are disclosed.