If I have a domain www.exemple.com how can I create second level domain ?
For exemple how can I create :
Www.client1.exemple.com
Www.client2.exemple.com
...
Thank you!
This will largely depend on who your domain name provider is. but basically the client1 part of www.client1.example.com is a subdomain.
'Most' DNS providers will allow for the creation of subdomains but not all do.
Once you have created a subdomain then the www part of that is just another host
If you are aiming to have a system where you substitute anything for client1 you might be able to use a www..example.com record. Again if your provider supports that (though they should do, it is standard DNS syntax) You would add the record www. and it should match www.$anything.example.com This is useful if you have clients with subdomains instead of profiles and you just want to point them all to the same server.
Related
I have a concern with our CDN as we are planning to apply custom domain. I understand the part that it is not possible to map a CNAME record to a root domain, such as contoso.com. I want to ask for a workaround, let us say yes we already assigned it to www.contoso.com. But people now adays do not use the www subdomain anymore and will just type constoso.com in the URL address bar and therefore it will just return a 404 because it is not mapped making as lose potential customers. What is your suggested solution or workaround for this?
Some DNS hosts allow creating CNAMES for root domains (ANAMES).
If your DNS host doesn't allow that then you can try to use subdomain redirection (like simple node.js app hosted on azure). Not the best solution but I'm not sure if other exists.
The work around is to use the cdnverify CNAME feature with A record.
CNAME : cdnverify.constoso.com -> cdnverify.constoso.azureedge.net
A record: constoso.com -> x.x.x.x
After all verification is complete, the CNAME can be removed. It worked for my domain.
(source: https://arlanblogs.alvarnet.com/adding-a-root-domain-to-azure-cdn-endpoint/)
There is currently no solution for this, except the described workaround when your domain-provider supports this.
There is a feature request on Azure for this problem:
https://feedback.azure.com/forums/217313-networking/suggestions/31221439-cdn-allow-root-domain-for-custom-domains
so basically I'm trying to make a secondary domain that is about.wyrnz.com and I was wondering if I have to buy another domain or if it is possible to do that without buying a new domain?
Thanks everyone for replying! I've worked it out now so this is now closed!
As soon as you own a second level domain (wyrnz.com), you can create as many sub-levels as you want. That includes third level (xxx.wyrnz.com), but also fourth (yyy.xxx.wyrnz.com) and as many levels you want.
That also depends on you host. I know that some hosts restricts the number of sub-domains you're allowed to create.
If www.wyrnz.com is your domain you should not have to buy another domain. In fact, you can not even buy it, you already own it. about.wyrnz.com is a subdomain of wyrnz.com.
What I did is:
Create a subfolder on the webserver, create a subdomain and point the subdomain to that folder. Every time someone types in about.wyrnz.com, the index page in the subfolder will be served to the user
I've created a really simple databaseless php application that I want to offer as a hosted solution. I've enable wildcard subdomains so that users can sign up and create a subdomain (e.g. "user.myapp.com"). However, I would like to offer the ability for my users to use a custom domain as well if they prefer. I'm pretty sure this can be accomplished by asking the user to add an A Record to their custom domain pointing to my server's IP, but I'm not sure how to handle the domain on my end once they create an A Record pointing to my server's IP.
So, say a user signs up for my service under "user.myapp.com" and then they decide they want to use a custom domain "someuser.com" instead. My specific question is — once the user adds an A Record to their domain "someuser.com" pointing to my server's IP, how do I tell my server to point that domain to "user.myapp.com"? Or is there an easier way to do this?
You'd need to first setup your server to accept requests from someuser.com, which is entirely different than setting up a wildcard for your server alias (e.g. *.myapp.com). You can have a default vhost handle all the hostnames that no other vhost is setup to handle, but then you're still left with mapping someuser.com to user.myapp.com.
Depending on how you've setup your php application, the user's going to need to enter the custom domain they've registered that they had point to your app, then you'll need to know to do that mapping internally by checking the $_SERVER['HTTP_HOST'] server variable to see what host the request is for, and if it's for someuser.com, then map it to user.myapp.com.
I'm hosting a clients site at client.mysite.com, but my client want to have its own domain, like www.clientsite.com.
With a CNAME configuration, I'll be able to hook my client domain to the content, but... considering I'm still hosting my clients content, which domain will be finally listed on Google with contents of client.mysite.com contents?
a) mysite.com
b) clientsite.com
Thanks for helping.
In the DNS hierarchy, the CNAME resource record will be attached to the clientside.com. A CNAME is simply a reference to the location of that site's A record. With that in mind, I believe mysite.com will be listed as hosting the data.
Does your client want it to appear under his name?
If so, then this should not be solved using DNS (well, not only using DNS).
If your client wants to get the content listed under his domain name, the best way to do this, is to add their name to your server.
Then point client domain name to your server.
The best way to do the pointing (when also considering SEO)
is to make an webforward (301 permanent) from the root, to the www
and make the www subdomain point to the ressource.
(Or vice verca)
IF you are using the example above (webforward on root) you can use a cname instead of an A record to point the domain name. However do not add a cname to the root of a domain (effectively shutting down your domain name).
So-
Short Answer:
client.mysite.com will have the content (also according to google).
Any attempt to obfuscate this is black hat or grey hat ;)
a better way of doing it is to simply setup the clients domain name on your server.
Then point only one hostname to the server. Server host/headers will take care of the rest.
Setup in DNS
# webforward 301 www
www a or Cname to server
Quick rules:
NEVER put Cname on the root of a domain
Only allow 1 hostname to show content (can be done both as explained above via DNS/webforward or via server configurations)
Im running SAAS where customer signs up and a script installation takes place in a subdomain, i.e., subdomain.mydomain.com and starts using the site. Now I want to allow my customers to map their FULL domain eg. www.customerdomain.com to subdomain.mydomain.com, something like bloggers.com or wordpress does. How I can do this. I am using Linux dedicated server. Help would be greatly appreciated. I dont want URL masking or redirection.
I'm currently developing a project and have recently faced the exact same issue. Here's two ways you can go about solving it:
Super-easy
A little more tricky, but not impossible
The first would be to allow domain mapping of subdomains (e.g. http://subdomain.example.com). This is dead simple for your users to setup. They would head over to their registrar and create a new CNAME record as follows:
(name) subdomain.example.com -> (record) subdomain.yoursite.com
Unlike changing A Records, this change only takes about 120 mins to fully propagate (compared with up to 72 hrs).
If your users pay for the privilege of using the domain mapping feature (i.e. it's not made available to users on a free plan), then you could could store each user's custom subdomain in your database, then check against this (in .php) when they try to access your website via their custom subdomain. If they're allowed, do nothing, otherwise redirect them to an alternate url.
So that's the easy one over and done with. Now for trickier option. If you have a dedicated IP address, or in your case a dedicated server, you can use the cPanel API to dynamically create A Records, this way users would be able to map their domain (rather just their subdomain) to your website. You would need to make the following A Record for your customer, together with getting them to update their domain's A Record with your dedicated IP address:
Your server:
(name) customersdomain.com -> (record) subdomain.yoursite.com
Customer's registrar:
www -> (record) [YOUR IP ADDRESS]
I'm not going to detail the API process for you, but you can read through the documentation here:
http://docs.cpanel.net/twiki/bin/view/SoftwareDevelopmentKit/ApiAuthentication
Anyways, I hope this helps and that you have fun building your website!
J
The (name) represents the custom domain belonging to your customer (e.g. customerdomain.com). The (record) would point to their subdomain on your SAAS site. So if I signed up to your website with a username of 'nike', you would use 'nike.yoursite.com'.
J
Install the wordpress domain mapping plugin, obviously your wordpress installation is setup for Wordpress MU.
Now the way I understand it you want to give your bloggers the opportunity to host their blog on their own personal domain while still hosting on your sever. Under "Domain Mapping" in "Settings" of "Network Administrator"(Super User).
There is Domain Options:
You want to check the User domain mapping page that's Option 3.
This will allow your blog users to specify the domain of their personal site. One thing to remind them is that their DNS records should point to your web server.