Is www a subdomain? [closed] - dns

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I recently purchased something.com.
When I visit something.com from my browser, I get the index page I uploaded on server.
However, if I visit www.something.com, it shows Error 404.
So I create a sub-domain named 'www' and upload another index file there.
Now, www.something.com and something.com shows two different websites.
My question is, is 'www' a normal sub-domain? Or some special kind of sub-domain? If yes, how is it different from other sub-domains?

is 'www' a normal sub-domain? Yes, it is. From the point of view of DNSs it is a totally normal subdomain.
is some special kind of sub-domain? Yes, it is, indeed. It is so commonly used that most Registrars and Hosting providers do automatically create it for you and permanently redirect it to the web server hosted with them.
in your case, it seems that this is not what happens. So, create it and permanently redirect it, instead of creating a new index page for it.

Related

How to make it so that when I type test.com it will open the files from b.test.com? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
We have two servers (with different IPs) which are hosting two different websites on them. We have the first site as the apex domain (example.com) and the second is a subdomain (b.example.com).
Right now example.com and b.example.com are completely different websites. How can I change this so that when I got to example.com it shows the same contents as b.example.com current shows?
So I guess this depends on what you're trying to achieve. I am assuming that because you have b.example.com that is supposed to be the new "beta" site that you are now wanting to go live with.
If you want to swap to the new site then you should update the DNS A record for example.com to point at the same IP that b.example.com is pointing at.
This is one approach but I would recommend adding more detail to your question so that we can be more clear about what you're trying to achieve 👍

What DNS requirements do I need to map one domain to another? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I have my first site at http://www.example.com/members/quiz.php?qid=My-quiz which queries a database.
I would like to display the exact content for each quiz under my second site: http://www.mysecondsite.example/quiz.php?qid=My-quiz
I am new to DNS so I know this is probably a simple question. What do I need to do on both domains to make this work?
You cannot solve this issue solely with DNS. With DNS all you can say that the IP address for www.example.com is the same as that for www.mysecondsite.example.
Your webserver has to understand that any requests for www.mysecondsite.example are actually the same as that for www.example.com and has to fulfil or redirect those requests appropriately. Depending on your webserver, search the manual for the topic on redirecting/forwarding requests.

godaddy webhosting root directory [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
im using go-daddy to learn web hosting ...
so i had problem and i reset my account because i thought something change some settings in the server..
after i reset the account i still have the same problem that my web root DIR is in (ht-docs owned by root) which i cant edit ...
this is the effective root directory .. i dont know why its not (public_html)
i ve allready asked in godaddy before about this and figured out my self the root directory by searching html code in all files in my server
(grep -isr "html code" /*)
https://uk.godaddy.com/community/Managing-Web-Hosting/public-html/td-p/51705
note: im newbie in linux .. i've just purchased godaddy account to learn web hosting ..
Why do you want to edit stuf in the default htdocs dir while the document root is set to /public_html/www in your user dir, according to the control panel screenshot you provided?
Look for public_html/www in your user dir, it should be ~/public_html/www, which is a shortcut to /home/YOUR_USER/public_html/www
PS: be careful asyour last screenshot shows /home/YOUR_USER/public_html as the document root, while the control panel one as www on top of it (but it might just be to handle subdomains)

URL Forwarding or CNAME for github pages [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I've set up a github page with a custom subdomain like sub.abc.com, and I also want the domain abc.com redirects to the subdomain(show subdomain in the browser's address bar). So, which method should I take, 302 URL Forwarding or CNAME? Thanks.
I have got an answer form github's technical support staff via email, and he said that I should use URL Forwarding rather than CNAME. Hope this can be helpful for others who meet the same problem.

Subdomain linked to a subdirectory? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I'm trying to set up my own cloud network and just got it to work the way I want it to, but I was hoping to linking it to a domain I own over at Godaddy. I want to use a subdomain for the cloud-thingy, but I don't want to link it to the ip alone. I'd rather link it to i.e "11.222.333.44/storage", instead of just "11.222.333.44" so I can still host a website at my domain's root
It seems like you need a Name-based Virtual Host, read the Apache docs.

Resources