Domain name collaboration service using domain name dependency server

• US 9,954,815 B2
• Filed: 09/15/2014
• Issued: 04/24/2018
• Est. Priority Date: 09/15/2014
• Status: Expired due to Fees

• Current Assignee: NXP USA, Inc. (NXP Semiconductors NV)
• Original Assignee: NXP USA, Inc. (NXP Semiconductors NV)
• Inventors: Crasta, Denis A., Addepalli, Srinivasa R.
• Primary Examiner(s): Tran, Jimmy H
• Application Number:
  US14/486,584
• Publication Number:
  US 20160080262A1
• Time in Patent Office: 1,317 Days
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 61/58 Caching of addresses or names

Abstract

A domain name dependency server (DDS) stores known relationships between domain names. In response to a domain relationship query from a local DNS server for a given domain name, the DDS supplies the domain names that are related to the given domain name. This reduces or eliminates serial requests for the related domain names from the local DNS server, reducing overall DNS lookup latency for the requested service. The DDS can be shared among multiple local DNS servers, and can be updated dynamically or manually to enhance the accuracy of its stored domain name relationships.

Claims

1. A method comprising:

at a local Domain Name Service (DNS) server, providing a first DNS query for a first domain name to a network for provision to a domain-name dependency server (DDS), wherein the first domain name identifies a webpage;

in response to providing the first DNS query to the network, receiving from the DDES a first set of domain names used to access content included in the web page and storing the first set of domain names at a cache of the local DNS server, wherein the first set of domain names indicate content in other domains that are different than a domain indicated by the first domain name;

generating a set of DNS queries at the local DNS server to identify addresses for the first set of domain names;

determining at the local DNS server a second set of domain names used to access content included in the webpage, wherein

the second set of domain names indicate content in other domains that are different than the domain indicated by the first domain name, and

based on DNS queries received from local devices via a local network coupled to the local DNS server, and

the second set of domain names are determined based on DNS queries received from local devices via a local network coupled to the local DNS server and further based on client identifiers included in the DNS queries;

merging the second set of domain names with the first set of domain names at the local DNS server to form a third set of domain names wherein generating the set of DNS queries comprises generating the set of DNS queries to identify addresses for the third set of domain names; and

identifying a time sequence of DNS queries for one of the local devices based on the client identifiers, wherein determining the second set of domain names comprises determining the second set of domain names based on the time sequence of DNS queries.

2. The method of claim 1, further comprising:

providing from the local DNS server a response to a second DNS query including an address for a domain name of the second DNS query, the second DNS query received from a client device; and

including with the response an indication that the address is not to be cached at the client device.

3. The method of claim 2, wherein the indication comprises a time-to-live field of the response to the second DNS query.

4. The method of claim 1, wherein the first DNS query comprises a DNS query for a web page.

5. The method of claim 1, wherein the first DNS query comprises a DNS query for streaming media.

6. The method of claim 1, wherein the first DNS query comprises a DNS query for a network messaging service.

7. A local domain name service (DNS) server, comprising:

a network interface to provide a first DNS query for a first domain name to a network for provision to a domain-name dependency server (DDS), wherein the first domain name identifies a webpage;

a cache to store a first set of domain names used to indicate content included in the webpage and received in response to the first DNS query, wherein

the first set of domain names indicate other domains that are different than a domain indicated by the first domain name, and

the first set of domain names is determined based on DNS queries from multiple devices over a wide area network;

a processor configured to generate a set of DNS queries at the local DNS server to identify addresses for the first set of domain names, wherein

the cache is to store a second set of domain names related to the first domain name,

the processor is to merge the second set of domain names with the first set of domain names at the local DNS server to determine a third set of domain names,

the processor is to generate the set of DNS queries based on the third set of domain names,

the processor is to identify a time sequence of DNS queries for one of the local devices based on the client identifiers, and

the processor is to determine the second set of domain names comprises based on DNS queries received from local devices via a local network, based on client identifiers included in the DNS queries, and based on the time sequence of DNS queries.

8. The local DNS server of claim 7, wherein the processor is to:

provide a response to a second DNS query including an address for a domain name of the second DNS query, the second DNS query to be received from a client device; and

include with the response an indication that the address is not to be cached at the client device.

9. The local DNS server of claim 8, wherein the indication comprises a time-to-live field of the response to the second DNS query.