Request routing processing

• US 8,626,950 B1
• Filed: 12/03/2010
• Issued: 01/07/2014
• Est. Priority Date: 12/03/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: MacCarthaigh, Colm, Richardson, David R., Redman, Benjamin W. S.
• Primary Examiner(s): Wang, Liangche A
• Assistant Examiner(s): Nguyen, Hao
• Application Number:
  US12/960,421
• Time in Patent Office: 1,131 Days
• Field of Search: None
• US Class Current: 709/245
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]

Abstract

Generally described, the present disclosure is directed to managing request routing functionality corresponding to resource requests for one or more resources associated with a content provider. A service provider can assign a set of DNS servers corresponding to a distributed set of network addresses, or portions of network addresses, for one or more identifiable domains. If the service provider receives requests to assign DNS server to conflicting domains, the set of DNS servers for each identifiable are assigned such that there are no matching network addresses between the sets of domains associated with the conflicting domains.

Claims

1. A method for managing DNS queries comprising:

obtaining, by a service provider, a request for hosting domain name service (DNS) query services for an identifiable domain;

determining, by the service provider, a number of assignable network address subdivisions, wherein each network address subdivision corresponds to a proportional division of available network addresses for service provider DNS server components;

assigning, by the service provider, a first set of network addresses in each of the determined network address subdivisions for the identifiable domain, wherein each of the network addresses in the first set of assigned network addresses from each subdivision for the identifiable domain are not matching;

transmitting, by the service provider, the first set of assigned network addresses, wherein DNS server components corresponding to the assigned network addresses from the first set of assigned network addresses are delegated to be authoritative to respond to DNS queries for the identifiable domain;

obtaining, by the service provider, a second request for hosting DNS query services, the second request corresponding to a second identifiable domain;

determining, by the service provider, a conflict associated with the identifiable domain and the second identifiable domain;

assigning, by the service provider, a second set of network addresses in each of the determined network address subdivisions for the second identifiable domain, wherein each of the network addresses in the second set of assigned network addresses from each subdivision for the second identifiable domain are not matching and wherein no matching network addresses between the first and second sets of assigned network addresses exist; and

transmitting, by the service provider, the second set of assigned network addresses, wherein DNS server components corresponding to the assigned network addresses from the first and second sets of assigned network addresses are delegated to be authoritative to respond to DNS queries for the second identified domain, and

wherein an identified destination network address in the DNS queries directed to the first or second set of assigned network addresses determines an authoritative DNS server component for the DNS queries.

2. The method as recited in claim 1, wherein each network address subdivision corresponds to one of four ranges of available network addresses for service provider DNS server components.

3. The method as recited in claim 2, wherein the four ranges of available network addresses are evenly distributed.

4. The method as recited in claim 1, wherein assigning the network address in each of the determined network address subdivisions includes selecting a network address from each determined network address subdivision such that the significant portion of the assigned networks addresses do not match.

5. The method as recited in claim 1, wherein assigning the network address in each of the determined network address subdivisions further includes preventing the assignment of network addresses that results in the matching of a threshold number of significant portions of the assigned network addresses between the identifiable domain and other domains.

6. The method as recited in claim 5, wherein the threshold number of network addresses is defined such that between the identifiable domain and the other domains, at least one significant portion of the assigned network addresses that does not match exists.

7. The method as recited in claim 1, wherein assigning the network address in each of the determined network address subdivisions includes assigning a uniquely named DNS server that has been previously associated with the identified network address.

8. The method as recited in claim 1, wherein assigning the network address in each of the determined network address subdivisions includes selecting a non-significant portion of each assigned network address such that a threshold number of the non-significant portions of the network addresses for the identifiable domain are not matching.

9. The method as recited in claim 8, wherein the threshold number of non-matching non-significant portions of network addresses includes all the assigned network addresses such that for the identifiable domain, none of the non-significant portions of all the assigned network addresses match.

10. The method as recited in claim 1, wherein the network addresses correspond to Internet protocol network addresses.

11. The method as recited in claim 1, wherein determining the conflict associated with the identifiable domain and the second identifiable domain includes determining that the identifiable domain and the second identifiable domain correspond to a same textual domain name.

12. The method as recited in claim 1, wherein determining the conflict associated with the identifiable domain and the second identifiable domain includes determining that the identifiable domain and the second identifiable domain correspond to subdomain conflicts.

13. A method for managing domain name service (DNS) queries comprising:

obtaining a request for hosting DNS query services for a first identifiable domain, the request including a request for assigning a set of DNS servers for the first identifiable domain;

assigning a first set of DNS servers for hosting the DNS query services directed toward the first identifiable domain, wherein each DNS server in the set of DNS servers is selected from defined network address zones, wherein the defined network address zones correspond to a division of assignable network addresses for service provider DNS servers;

causing the DNS servers corresponding to the assigned first set of DNS servers to be authoritative to respond to DNS queries for the first identifiable domain;

obtaining a request for hosting DNS query services for a second identifiable domain, the request including a request for assigning a set of DNS servers for the second identifiable domain, wherein the first and second identifiable domains conflict;

assigning a second set of DNS servers for hosting the DNS query services directed toward the second identifiable domain, wherein each DNS server in the set of DNS servers is selected from defined network address zones, wherein no matching network addresses between the first and second sets of DNS servers exist; and

causing the DNS servers corresponding to the second set of DNS servers to be authoritative to respond to DNS queries for the second identifiable domain.

14. The method as recited in claim 13 further comprising determining a number of network address zones.

15. The method as recited in claim 14, wherein the number of network address zones corresponds to a proportional distribution of available network addresses.

16. The method as recited in claim 13 further comprising selecting a non-significant portion of each assigned network address such that a threshold number of the non-significant portions of the network addresses for the first identifiable domain are not matching.

17. The method as recited in claim 16, wherein selecting the non-significant portion of each assigned network address corresponds to selecting the non-significant portions of the network addresses from unique values corresponding to a non-overlapping range of potential values.

18. The method as recited in claim 17, wherein the range of values corresponds to the number of zones.

19. The method as recited in claim 13, wherein causing the DNS server components corresponding to the assigned network addresses to be authoritative to respond to DNS queries for the first identifiable domain includes transmitting the assigned network address for each of the set of DNS servers.

20. The method as recited in claim 13, wherein causing the DNS server components corresponding to the assigned network addresses to be authoritative to respond to DNS queries for the second identifiable domain includes transmitting a name associated with the assigned network address for each of the set of DNS servers, the name associated with the assigned network address previously configured with the assigned network addresses.

21. The method as recited in claim 13 further comprising determining whether a conflict exists between the first and second identifiable domains.

22. The method as recited in claim 21, wherein determining whether a conflict exists between the first and second identifiable domains includes determining that the first identifiable domain and the second identifiable domain correspond to a same textual domain name.

23. The method as recited in claim 13, wherein at least a portion of the first set of DNS servers and at least a portion of the second set of DNS servers corresponds to a same physical computing device.

24. A system for domain name service (DNS) query processing comprising:

an interface component for obtaining registration information at a service provider for registering one or more content providers with the service provider, the registration corresponding to hosting at least of portion of request routing functionality associated with one or more resources provided by the content provider; and

a processing component operative to;

obtain requests for hosting DNS query services for first and second identifiable domains, wherein each request includes a request for assigning a set of DNS servers for the identifiable domain;

assign a first set of DNS servers for hosting DNS query services associated with the first identifiable domain, wherein each DNS server in the first set of DNS servers is selected from defined network address zones, wherein the defined network address zones correspond to a division of assignable network addresses for service provider DNS servers and wherein no matching network addresses in any of the first set of DNS servers exist;

cause the DNS server components corresponding to the assigned network addresses to be authoritative to respond to DNS queries for the first identifiable domain;

assign a second set of DNS servers for hosting DNS query services associated with the second identifiable domain, wherein each DNS server in the second set of DNS servers is selected from the defined network address zones, wherein there is no matching network addresses in any of the second set of DNS servers, and wherein no matching network addresses between the first and second set of DNS server based on a determined conflict between the first and second identifiable domain exist; and

cause the DNS server components corresponding to the assigned network addresses to be authoritative to respond to DNS queries for the second identifiable domain.

25. The system as recited in claim 24, wherein the processing component is further operative to determine a number of network address zones.

26. The system as recited in claim 24, wherein the processing component is operative to assign network addresses within each set of assigned DNS severs in a manner such that a threshold number of the non-significant portions of the network addresses for the first identifiable domain are not matching.

27. The system as recited in claim 26, wherein the processing component is operative to select the non-significant portions of the network addresses from unique values corresponding to a non-overlapping range of potential values.

28. The system as recited in claim 27, wherein the range of values corresponds to the number of zones.

29. The system as recited in claim 24, wherein the processing component is operative to transmit the assigned network address for each of the set of DNS servers.

30. The system as recited in claim 24, wherein the processing component is operative to transmit a name associated with the assigned network address for each of the set of DNS servers, the name associated with the assigned network address previously configured with the assigned network addresses.

31. The system as recited in claim 24, wherein the processing component is operative to determine whether a conflict exists between the first and second identifiable domains.

32. The system as recited in claim 31, wherein the processing component is operative to determine a conflict based on a determination that the first identifiable domain and the second identifiable domain correspond to a same textual domain name.

33. The system as recited in claim 24, wherein at least a portion of the first set of DNS servers and at least a portion of the second set of DNS servers corresponds to a same physical computing device.