Tag Info

New answers tagged


When you create the zone, create the subdomain and not the root domain. So create 2 zones, sub1.domain2.com. Delete domain2.com zone so your server stops answering nxdomain for www.domain2.com I use this method to split-dns my premise exchange servers.


Cause i have not 50 Reputation i'm not able to add an normal Comment. So had to do a normal comment, really strange the permission system here. http://blogs.technet.com/b/networking/archive/2015/05/12/split-brain-dns-deployment-using-windows-dns-server-policies.aspx Split Brain DNS, should be a good hint.


I was a little confused about the question at first, since certificates are generally thought of as providing for only one subject in the typical case. Isn't securing a single dns record(/subdomain, see section 3) with an SSL domain validated certificate that is NOT a wildcard the standard case for a website? Put simply, you can and should secure the ...


Yes you can have a certificate that just covers a particular subdomain. You can also have a certificate that covers more than one subdomain without being a wildcard. Be aware that SSL/TLS traditionally only allowed one certificate per IP/port combination. There is an extension called SNI that fixes that but there are still some older clients out there that ...


If you own "domain.com" you can also request a certificate for "mail.domain.com". You will just need to prove your ownership of the root domain.


You can use SSL cert issued just for mail.domain.com without any problem. The biggest advantage of wildcard certs is there is only "one cert to rule them all" - you don't need to manage dozens of certs.


What you probably want to do is create an NS record. Not a CNAME. NS subdomain.domain.com. ns1.nameserver.com. Then on your subdomains nameserver (could be the same nameserver): create a zonefile for subdomain.domain.com with the necessary and appropriate bindings. NS subdomain.domain.com. ns1.nameserver.com. A subdomain.domain.com. MX ...


server { set $docroot "/var/www/domain.com/public_html/"; listen 80 default_server; server_name www.domain.com domain.com; root $docroot; try_files $uri $uri/ /index.php?$args; index index.php index.html index.htm; } server { set $docroot "/var/www/sub1domain.com/public_html/"; listen 80; ...


It sounds like your application or some component of your server is actually redirecting to the IP address. In either chrome or firefox, pop open the debug/developer panel (ctrl + shift + k for firefox, ctrl + shift + j for chrome). Click on the 'network' tab. Make a request to the desired address (sub2.mydomain.com). What I'm theorizing you'll see is a ...


I'm assuming you're meaning you have something of the form example.com and mobile.example.com ? There is nothing inherently wrong with these being served from different IPs for load balancing or other purposes. It's not going to be an intelligent distribution of traffic based on actual load - but if it meets your needs : then as a cheap and easy solution I ...


As mentioned in the comments, the best way (most readable and fastest) is to manually configure each domain. This is because NGINX will create static entities in memory to avoid the runtime processing of each request. However, if you really want to do this (proxy_pass to different places for different subdomains) then you can do this: E.g. map $http_host ...


Ah!!! In the end it was a rails configuration problem! In --config ----settings ------production.yaml subdomain: tld_length: 1 domain: 'webweka.com' tld_length was set to 2, to handle the subdomained elastic beanstalk address xxx.elasticbeanstalk.com setting it back to 1 has handed the subdomain correctly! Whoops...

Top 50 recent answers are included