Dynamic DNS Configuration for Local Network Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Devices in local area networks often rely on default DNS settings provided by DHCP servers, which point to remote DNS servers for Internet access, limiting local area network communication to IP addresses, making it cumbersome and error-prone for devices to connect within the network.

Innovation Solution

A client process that detects the presence of a local DNS server within the network adjusts DNS settings to use the local server, allowing for both Internet and local area network access, and reverts to the original DHCP settings if the local DNS server is absent.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If devices use default DHCP-supplied DNS settings pointing to remote DNS servers, then Internet access is enabled, but local area network communication becomes cumbersome and error-prone requiring IP address entry

Engineering Contradiction:

Improvelocal area network communication easeVSAvoidDNS server adaptability

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system dynamically switches between remote and local DNS servers based on the presence and status of a local DNS server. When a local DNS server is detected, the client process automatically updates DNS settings to use the local server; when absent, it reverts to the remote DHCP-supplied DNS server. This dynamic adaptation resolves the contradiction by making the system flexible enough to provide ease of operation for local communication when needed while maintaining Internet access capability when local services are unavailable.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The invention changes the DNS server parameter based on network conditions. The client process monitors for the presence of a local DNS server and adjusts the DNS configuration accordingly - switching from remote DNS server parameters to local DNS server parameters. This parameter change enables the system to optimize for local area network communication ease when a local DNS server is present, while maintaining the ability to access remote DNS servers for Internet connectivity when local services are absent.

Inventive Principle:

Principle #35Parameter changes

2Ease of operation

If devices switch to local DNS server for local network access, then local communication ease is improved, but Internet access may be lost if local DNS server is absent

Engineering Contradiction:

Improvelocal area network communication easeVSAvoidnetwork connectivity reliability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The client process implements continuous monitoring of the local DNS server's presence and operational status. This feedback mechanism detects when the local DNS server is absent or non-functional and automatically triggers a switch back to the remote DHCP-supplied DNS server. This feedback loop ensures reliability by preventing loss of Internet access while still enabling ease of local communication when the local DNS server is available and functioning properly.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system maintains the DHCP-supplied remote DNS server configuration as a backup before attempting to use a local DNS server. This prior cushioning ensures that if the local DNS server is absent or fails, the device can immediately revert to the remote DNS server without loss of Internet connectivity. This preparatory measure protects against reliability issues while allowing the system to optimize for local communication ease when conditions permit.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

3Ease of operation

If manual configuration of local DNS server is required, then local communication capability is achieved, but device complexity and user burden increase

Engineering Contradiction:

Improvelocal area network communication easeVSAvoidDNS configuration complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The client process automatically performs detection of the local DNS server, monitors its presence, and updates DNS settings without user intervention. The system self-manages the complexity of DNS configuration by implementing automatic detection and switching logic, eliminating the need for users to manually configure DNS settings. This self-service approach maintains ease of operation for local communication while hiding the complexity of DNS management from the user.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The client process acts as an intermediary between the network environment and the device's DNS configuration. It automatically detects the presence of a local DNS server, evaluates whether to switch to it, and manages the configuration changes. This intermediary function absorbs the complexity of DNS server selection and switching, presenting a simple experience to the user while handling the complex decisions about which DNS server to use and when to switch between local and remote options.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8924519B2Automated DNS configuration with local DNS server

Publication Date: 2014.12.30 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A client process may identify a local DNS server and may change a DHCP-supplied DNS setting to the local DNS server when the local DNS server is present. The client process may periodically monitor the local DNS server and, if the local DNS server is not present, the client process may revert the DNS setting to the originally supplied DHCP DNS setting. The client process may actively monitor the local DNS server by initiating communication with the local DNS server, or may passively monitor by listening for activity by the local DNS server.