DOMAIN NAME COLLABORATION SERVICE USING DOMAIN NAME DEPENDENCY SERVER

• US 20160080262A1
• Filed: 09/15/2014
• Published: 03/17/2016
• Est. Priority Date: 09/15/2014
• Status: Active Grant

• Current Assignee: NXP USA, Inc. (NXP Semiconductors NV)
• Original Assignee: Freescale Semiconductor, Inc. (NXP Semiconductors NV)
• Inventors: CRASTA, DENIS A., Addepalli, Srinivasa R.
• Granted Patent: US 9,954,815 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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);

in response to providing the first DNS query to the network, receiving from the DDS a first set of domain names related to the first domain name and storing the first set of domain names at a cache of the local DNS server; and

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

2. The method of claim 1, further comprising:

determining at the local DNS server a second set of domain names related to the first domain name;

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; and

wherein generating the set of DNS queries comprises generating the set of DNS queries to identify addresses for the third set of domain names.

3. The method of claim 2, wherein determining the second set of domain names comprises identifying the second set of domain names based on DNS queries received from local devices via a local network coupled to the local DNS server.

4. The method of claim 3, wherein determining the second set of domain names comprises determining the second set of domain names based on client identifiers included in the DNS queries.

5. The method of claim 4, further comprising:

identifying a time sequence of DNS queries for one of the local devices based on the client identifiers; and

wherein determining the second set of domain names comprises determining the second set of domain names based on the time sequence of DNS queries.

6. 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.

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

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

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

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

11. A method, comprising:

receiving, at a domain name dependency server (DDS), a DNS query for a first domain name;

identifying, based on a database of domain names at the DDS, a plurality of domain names that are related to the first domain name, the database of the DDS based on DNS queries issued from a plurality of devices over a wide area network; and

providing, by the DDS, the plurality of domain names to the wide area network for provision to a requesting device.

12. The method of claim 11, further comprising:

receiving at the DDS an indication of a change to a web service associated with the first domain name; and

updating the database of domain names based on the change to the web service.

13. The method of claim 11, further comprising:

receiving at the DDS an analysis of DNS logs based on the DNS queries issued from the plurality of devices; and

updating the database of domain names based on the analysis.

14. 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);

a cache to store a first set of domain names related to the first domain name and received in response to the first DNS query, the first set of domain names based on DNS queries from multiple devices over a wide area network; and

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.

15. The local DNS server of claim 14, 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; and

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

16. The local DNS server of claim 15, wherein the processor is to determine the second set of domain names comprises based on DNS queries received from local devices via a local network.

17. The local DNS server of claim 16, wherein the processor is to the second set of domain names based on client identifiers included in the DNS queries.

18. The local DNS server of claim 17, wherein the processor is to:

identify a time sequence of DNS queries for one of the local devices based on the client identifiers; and

determine the second set of domain names based on the time sequence of DNS queries.

19. The local DNS server of claim 14, 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.

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