StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO1 A-record for every subdomain (10000+); any potential issues? Any other solution?
primarykey
Id
474244
data
AcceptedAnswerId
475892
AnswerCount
4
ClosedDate
CommentCount
5
CommunityOwnedDate
2009-01-26T20:18:57.103
CreationDate
2009-01-23T19:51:35.063
FavoriteCount
2
LastActivityDate
2009-01-26T20:29:09.233
LastEditDate
2009-01-26T20:29:09.233
LastEditorUserId
35634
OwnerUserId
35634
ParentId
0
PostTypeId
1
Score
1
ViewCount
1071
LastEditorDisplayName
Henry
text
Body
Most solutions I've read here for supporting subdomain-per-user at the DNS level are to point everything to one IP using *.domain.com. It is an easy and simple solution, but what if I want to point first 1000 registered users to serverA, and next 1000 registered users to serverB? This is the preferred solution for us to keep our cost down in software and hardware for clustering. <a href="http://learn.iis.net/file.axd?i=1101" rel="nofollow noreferrer">alt text http://learn.iis.net/file.axd?i=1101</a> (diagram quoted from MS IIS site) The most logical solution seems to have 1 x A-record per subdomain in Zone Datafiles. BIND doesn't seem to have any size limit on the Zone Datafiles, only restricted to memory available. However, my team is worried about the latency of getting the new subdoamin up and ready, since creating a new subdomain consist of inserting a new A-record & restarting DNS server. Is performance of restarting DNS server something we should worry about? Thank you in advance. UPDATE: Seems like most of you suggest me to use a reverse proxy setup instead: <a href="http://learn.iis.net/file.axd?i=1102" rel="nofollow noreferrer">alt text http://learn.iis.net/file.axd?i=1102</a> (ARR is IIS7's reverse proxy solution) However, here are the CONS I can see: <ol> <li>single point of failure</li> <li>cannot strategically setup servers in different locations based on IP geolocation.</li> </ol>
Tags
<mod-rewrite><dns><subdomain><bind>
Title
1 A-record for every subdomain (10000+); any potential issues? Any other solution?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USHenry
UserOwnerUserId
1. USHenry
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO1 A-record for every subdomain (10000+); any potential issues? Any other solution?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO1 A-record for every subdomain (10000+); any potential issues? Any other solution?
 UserUserId
 USDan P
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 PO1 A-record for every subdomain (10000+); any potential issues? Any other solution?
 UserUserId
 USHenry
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.