Tag Info

New answers tagged

0

To answer your question - the hostname should be whatever is meaningful to you or your organisation. Hostname The hostname is used only by the host. It's used by the system and services as a default (human-readable?) identity when no context-specific identity has been specified. It might be used in a log file; it's probabaly used on your shell to give ...


2

The hostname is a convenience for uniquely identifying the host on your network. It's an entirely internal name that can be anything you want. The hostname doesn't have to be related to any of its DNS names. For example, your host named abc can have DNS records that point to it as www.example.com, mail.example.com, and so on. If you run local DNS within ...


0

At the end a friend of mine saw that I have a typo in the vhosts and he added some entries in /etc/hosts with the domain and the server IP thedomain.com XXX.XXX.XX.XX www.thedomain.com XXX.XXX.XX.XX orlybg.thedomain.com XXX.XXX.XX.XX calis.thedomain.com XXX.XXX.XX.XX


0

As mentioned in the comment of the question, I needed to edit some DNS records on DigitalOcean, not in the registar administration. Seems that I missed this link during my research, hope it helps other folks. https://www.digitalocean.com/community/tutorials/how-to-set-up-and-test-dns-subdomains-with-digitalocean-s-dns-panel


0

I have two suggestions apart from this issue Add ServerName with the FQDN of the host in which the Apache is serving the request. This will help you avoid lots of trouble. If all of the sub-domains have different IP address then use IP based virtualization instead of Name based. Your VirtualHost configuration looks perfect and it doesn't look creating ...


0

Well, the problem was very simple. My sites are hosted at Digital Ocean and I had only non-www domains in their DNS records. I still don't know how to dynamically add all subdomains (asterisk is not supported) but that's another story.


1

You have two virtualhost files for the same domain, at for the same port. You need just one file for this. Choose if you want to serve your Odoo using mod_proxy or mod_wsgi, but not both.


0

You'll have to trace the DNS query one at a time to see where it bombs out. On your PC, try this: nslookup > set type=ns > site.com That should return a list of name servers. Pick one by going: > server ip_address_of_one_of_the_NS_servers_returned_above Then that server should have the www record in it. Confirm this by running: > set type=a ...


2

The short answer to your specific case: apache will serve the FIRST overlapping virtual host. Since 000-default is before fc.localhost in the alphabet the first virtualhost is loaded and served. To answer what i assume is the follow up question: You can host many sites on the same IP:PORT using namedVirtualHosts This technology relies on the Host Header in ...


1

This is called "name based virtual hosting", described here: [http://httpd.apache.org/docs/2.4/en/vhosts/name-based.html]


12

Yes. This would all be controlled through DNS. You can set up, for example, www.example.com to 203.0.113.2 and home.example.com to 203.0.113.3. You could theoretically go turtles all the way down and make subdomains of your subdomains. The address www.chicago.illinois.us.example.com is perfectly valid, though cumbersome. (edited to conform to RFC 5737 ...


0

Does A record matters while creating subdomain Creating the A record is how you create the subdomain!* You don't create the subdomain in apache, you create it in your DNS, and then configure apache to serve content for it. You state that you don't have an option in your panel to create an A record... You NEED that option in order to accomplish that ...


1

When Wildcard SSL certificate is issued for *.domain.com, you can secure your unlimited number of sub domains over the main domain. For example: sub1.domain.com sub2.domain.com sub3.domain.com sub*.domain.com If the Wildcard SSL certificate is issued on *.sub1.domain.com, in that case you can secure all second level subdomains which are listed under the ...


4

You should get the UCC SAN certificate as GoDaddy suggests. You need AT LEAST two FQDNs - autodiscover.domain.com and mail.domain.com. Never had an issue with Godaddy certs.


2

URLs are relative to the server they are hosted on. So if someone goes to http://dashboard.example.com/admin, that request will go to the server dashboard.example.com. That server can then redirect the request to some other server (say http://dashboard.example.org/admin/createuser). So the short answer is that you need to configure your webservers ...



Top 50 recent answers are included