Tag Info

New answers tagged

0

You are somewhat confused about the different parts of the URL. Let me break them out for you: https://www.example.com/path https is the protocol www is the subdomain example.com is the domain name com is the top level domain /path is the URL path How can URLs have a dot . at the end, e.g. www.bla.de.? is about the domain name ending in a . ...


3

This is relatively easy to do. Using example.com, you have: An A record for the example.com A CNAME (as an alias) pointing www to example.com (www is a sub-domain) --where www = example.com -- or -- An A record for www.example.com To have sub-domain.example.com you would have: An A record for sub-domain.example.com --where the IP address is for the new ...


2

No. I run several sites like this. The binding determines which app takes the requests, and each app can only have one app pool. An app pool can use multiple processes (a web garden) but that is completely unrelated to wildcard domain names (even a single domain gets split across multiple processes in this scenario). An app domain (a security construct ...


0

If you use it at blog.example.com, it will be treated as another website. If you put it on a subfolder, it will be treated as part of website. This will impact the content of the website, inbound links, pages, backlinks, and everything else. Conclusion: it is better in a subfolder then on a subdomain. You have to remove the content on a subdomain because ...


1

If you move your blog to a subdomain, you shouldn't, by any means, keep it in the folder due to duplicate content problems. You can only move it, not copy it. About your question, for my experience it's not true and you should keep your blog where it is right now. This happens because the main domain has the main strength and power and dividing it to ...


0

You also need to configure your web server to (return a 301) redirect from blog.qmery.com to blog.borhancid.com. Simply pointing DNS correctly is not enough.


4

I would recommended either using the www or non-www and stick with it. Set a preferred URL in Webmaster Tools and then 301 to either your www or non-www. The reason for this would be Google would see both the non-www and www sites as two separate websites. If the content is exactly the same, then you could be penalized with duplicate content.


0

You don't want just an A record, you want an SRV record for minecraft. To connect with whatever.domain.tld to your minecraft server add _minecraft._tcp.whatever.domain.tld. IN SRV 0 5 minecrafts_port_number yourminecraftserver.domain.tld. and then yourminecraftserver.domain.tld. IN A servers.ip.address It looks like taking a detour but ...



Top 50 recent answers are included