RESOLVING ACCESS TO CONTENT ASSOCIATED WITH SHARED DOMAIN NAME USING ROUTING DNS

• US 20050204064A1
• Filed: 06/23/2005
• Published: 09/15/2005
• Est. Priority Date: 06/23/2005
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Group Incorporated (GoDaddy, Inc.)
• Inventors: Ruiz, Tim
• Granted Patent: US 9,450,908 B2
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]

Abstract

Systems and methods of the present invention allow for sharing domain names based on a network address or a geographical location of a Requester. Multiple independent parties (Content Providers), which may be located in different geographical areas, may use the same domain name to host their websites. The Requester may access data (e.g. websites, FTP resources) associated with a shared domain name. A Routing DNS may determine the network address or the geographical location of the Requester and provide the Requester with a network address of a Server associated with Requester'"'"'s network address or geographical location. Each Server is maintained by its own Content Provider.

Claims

1. A shared domain name system, comprising:

a) a Plurality of Servers associated with a domain name, wherein each Server has a Server'"'"'s network address, and

b) a Routing DNS having an ability to determine a Requester'"'"'s network address and provide a Requester with said Server'"'"'s network address corresponding to said Requester'"'"'s network address.

2. The system of claim 1, further comprising:

c) a Plurality of Requesters having an ability to obtain DNS records for said domain name.

3. The system of claim 1, further comprising:

c) a Plurality of DNS providing DNS records to said Requester.

4. The system of claim 3, wherein said Plurality of DNS includes a Root DNS.

5. The system of claim 3, wherein said Plurality of DNS includes a Top Level DNS.

6. The system of claim 1, further comprising:

c) a Database storing associations between network addresses or blocks of network addresses and said Servers.

7. The system of claim 1, further comprising:

c) a Plurality of Content Providers providing content for said Plurality of Servers.

8. The system of claim 7, further comprising:

d) a Database storing associations between network addresses or blocks of network addresses and said Content Providers.

9. The system of claim 1, wherein said Routing DNS has an ability to determine a geographical location of said Requester using said Requester'"'"'s network address and provide said Requester with said Server'"'"'s network address corresponding to said geographical location.

10. The system of claim 9, wherein said geographical location comprises latitude and longitude coordinates.

11. The system of claim 9, further comprising:

c) a Database storing associations between geographical locations and network addresses.

12. The system of claim 9, further comprising:

c) a Database storing associations between geographical locations and said Servers.

13. The system of claim 9, further comprising:

c) a Plurality of Content Providers providing content for said Plurality of Servers.

14. The system of claim 13, further comprising:

d) a Database storing associations between geographical locations and said Content Providers.

15. A shared domain name method, comprising the steps of:

a) determining a Requester'"'"'s network address, and

b) providing a Requester with a Server'"'"'s network address, wherein a Server serves content to Requesters located at said Requester'"'"'s network address.

16. The method of claim 15, wherein Steps a) and b) are performed by a Routing DNS.

17. The method of claim 15, further comprising a step of:

c) prior to Step a), requesting DNS records of a shared domain name.

18. The method of claim 15, further comprising the steps of:

c) requesting content from said Server, and

d) receiving content from said Server.

19. A shared domain name method, comprising the steps of:

a) determining a geographical location of a Requester, and

b) providing said Requester with a Server'"'"'s network address, wherein a Server serves content to Requesters located in said geographical location.

20. The method of claim 19, wherein Steps a) and b) are performed by a Routing DNS.

21. The method of claim 19, further comprising a step of:

c) prior to Step a), requesting DNS records of a shared domain name.

22. The method of claim 19, further comprising the steps of:

c) requesting content from said Server, and

d) receiving content from said Server.

23. The method of claim 19, wherein said geographical location comprises latitude and longitude coordinates.