RESOLVING ACCESS TO CONTENT ASSOCIATED WITH SHARED DOMAIN NAME USING ROUTING WEBSITE
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 forward the Requesters to their Websites. A Routing Website may determine the network address or the geographical location of the Requester and serve the Requester with a forwarding command that forwards the Requester to a Website associated with Requester's network address or geographical location. Each Website is maintained by its own Content Provider.
1 . A shared domain name system, comprising:
a) a Plurality of Websites storing a content accessible via a computer network, wherein each Website stores content corresponding to one or more network addresses, and
b) a Routing Website having an ability to determine a Requester's network address and forward a Requester to a Website corresponding to said Requester's network address.
2 . The system of claim 1 , further comprising:
c) a Plurality of Requesters having an ability to access said Routing Website.
3 . The system of claim 1 , further comprising:
c) a Database storing associations between network addresses or blocks of network addresses and said Websites.
4 . The system of claim 1 , further comprising:
c) a Plurality of Content Providers providing content for said Plurality of Websites.
5 . The system of claim 4 , further comprising:
d) a Database storing associations between network addresses or blocks of network addresses and said Content Providers.
6 . The system of claim 1 , wherein said Routing Website has an ability to determine a geographical location of said Requester using said Requester's network address and forward said Requester to a Website corresponding to said geographical location.
7 . The system of claim 6 , wherein said geographical location comprises latitude and longitude coordinates.
8 . The system of claim 6 , further comprising:
c) a Database storing associations between geographical locations and network addresses.
9 . The system of claim 6 , further comprising:
c) a Database storing associations between geographical locations and said Websites.
10 . The system of claim 6 , further comprising:
c) a Plurality of Content Providers providing content for said Plurality of Websites.
11 . The system of claim 10 , further comprising:
d) a Database storing associations between geographical locations and said Content Providers.
12 . The system of claim 1 , wherein forwarding of said Requester to said Website corresponding with said Requester's network address is achieved by serving said Requester with a webpage containing redirecting meta tag.
13 . The system of claim 1 , wherein forwarding of said Requester to said Website corresponding with said Requester's network address is achieved by serving said Requester with a webpage containing redirecting programming script.
14 . A shared domain name method, comprising the steps of:
a) determining a Requester's network address, and
b) forwarding a Requester to a Website corresponding to said Requester's network address.
15 . The method of claim 14 , wherein Steps a) and b) are performed by a Routing Website.
16 . The method of claim 14 , further comprising the steps of:
c) requesting content from a Routing Website, and
d) receiving a forwarding command from said Routing Website.
17 . The method of claim 14 , wherein Step b) comprises a step of:
c) serving a webpage containing redirecting meta tag to said Requester.
18 . The method of claim 14 , wherein Step b) comprises a step of:
c) serving a webpage containing redirecting programming script to said Requester.
19 . A shared domain name method, comprising the steps of:
a) determining a geographical location of a Requester, and
b) forwarding said Requester to a Website corresponding to said geographical location of said Requester.
20 . The method of claim 19 , wherein Steps a) and b) are performed by a Routing Website.
21 . The method of claim 19 , further comprising the steps of:
c) requesting content from a Routing Website, and
d) receiving forwarding command from said Routing Website.
22 . The method of claim 19 , wherein Step b) comprises a step of:
c) serving a webpage containing redirecting meta tag to said Requester.
23 . The method of claim 19 , wherein Step b) comprises a step of:
c) serving a webpage containing redirecting programming script to said Requester.
24 . The method of claim 19 , wherein said geographical location comprises latitude and longitude coordinates.