Non-LDH Domain Name Resolution via LDH Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current domain name authorities limit domain names to ASCII letters, numeric digits, and hyphens, preventing the use of non-standard characters, which restricts branding and marketing flexibility for website owners.
Innovation Solution
A system and method that allows domain name resolution and registration of names with non-LDH characters by associating a first computer server with a second server having a non-LDH domain name, using a registration server to maintain this association and configure client computers to establish communication sessions with the second server while displaying the non-LDH domain name.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If domain names are limited to LDH characters (ASCII letters, digits, hyphens), then domain name server compatibility and standardization are maintained, but branding and marketing flexibility are restricted
Solution Approach 1:
The patent introduces an intermediary mapping system that translates between LDH domain names (compatible with existing DNS) and non-LDH domain names (desired for branding). This intermediary layer allows the DNS to continue using standard LDH characters while users can register and access domains with special characters, emojis, or other non-standard characters through the mapping mechanism.
Solution Approach 2:
The patent creates a copy or representation of the non-LDH domain name in LDH format. Instead of modifying the DNS to handle special characters directly, the system generates an LDH equivalent (such as a hash or encoded version) that points to the original non-LDH domain, allowing standard DNS infrastructure to resolve the domain without direct exposure to special characters.
2Adaptability or versatility
If non-LDH characters are allowed in domain names, then branding options are expanded, but compatibility with existing domain name servers is compromised
Solution Approach 1:
The mapping system acts as an intermediary between the user's desired non-LDH domain name and the DNS server's requirement for LDH characters. The system accepts non-LDH input from users, translates it to LDH format for DNS resolution, and maintains the association between the two formats, ensuring DNS servers continue to operate with standard characters while users gain access to extended character options.
Solution Approach 2:
The patent segments the domain name resolution process into distinct stages: user input (non-LDH), mapping/translation layer, and DNS resolution (LDH). This segmentation allows each component to operate in its optimal format - users can input desired branding names with special characters while the DNS infrastructure continues to use standard LDH characters it is designed to handle.
3Adaptability or versatility
If a mapping system is introduced between LDH and non-LDH domain names, then non-standard characters can be used, but system complexity increases
Solution Approach 1:
The mapping system is designed to be self-populating and self-maintaining. When a new non-LDH domain is registered, the system automatically generates the corresponding LDH mapping and stores it in the mapping database. The system self-updates as new domains are added, reducing the need for manual configuration and minimizing operational complexity despite the added functionality.
Data Source
AI summary
A method of resolving a domain name that includes a non-LDH character, involves a client computer receiving a domain name update notification for a first computer server that has a LDH domain name comprising at least one character but excluding non-LDH characters. In response, the client computer downloads a configuration payload from a registration server that maintains an association between the first computer server and a second computer server. The configuration payload links the first computer server to a non-LDH domain name associated with the second computer server and configures the client computer to determine an identification of the second computer server from the first LDH domain name. The non-LDH domain name has at least one non-LDH character. The client computer uses the identification of the second computer server to establish a communication session therewith while displaying the associated non-LDH domain name.