We need to have a different name server for multiple subdomains of a subdomain. For example,
john.users.example.com
jack.users.example.com
I tried adding NS for subdomains *.users.example.com but it doesn't work. I tried following combinations (the domain is hosted on name.com)
Following works, but only for users.example.com it uses the new name server
users.example.com NS new.nameserver.com
Following works too
*.example.com NS new.nameserver.com
But this does not work
*.users.example.com NS new.nameserver.com
Any idea what am I doing wrong?
Related
I am having difficulties getting my domain to point to my EC2 properly. I searched through a few third party guides online, and got slightly swamped in the official AWS documentation, but despite this I still cant get it to work.
Ive have Route 53 set up like this:
Type: A
Value: ??.??.??.?? (IP address)
Type: NS
Value: ns-1403.awsdns-47.org.
ns-1696.awsdns-20.co.uk.
ns-632.awsdns-15.net.
ns-431.awsdns-53.com.
Type: SOA
Value: ns-431.awsdns-53.com.
awsdns-hostmaster.amazon.com
And on my domain host I have the DNS Records set up like this:
Hostname: www
Type: NS
Value: ns-1403.awsdns-47.org
ns-1696.awsdns-20.co.uk
ns-632.awsdns-15.net
ns-431.awsdns-53.com
I think I am doing something fundamentally wrong. Firstly Im not sure if I got the Hostname part right on my DNS records. On the site it says .domain after the input box for the Hostname, which makes me think its a sub domain specifier. Am I right in thinking the # symbol works for no subdomain? (i.e. domain.com instead of www.domain.com)
Secondly should I remove the NS record set from Route 53, as its already specified in the DNS Records on the domain host?
Many thanks
There are two missing pieces here: telling your registrar to use Route53 instead of their own NS servers, and telling Route53 about your EC2 instance.
First, you need to set up your registrar. In this step you're telling the registrar to tell the global DNS system to look at Route53 for information about domain.com. Here's a quick tutorial for Namecheap and here's one for GoDaddy. Other registrars are similar, just google for YourRegistrarHere assign nameservers.
Second, to tell Route53 about your EC2 instance you should set an A record for domain.com within Route53 pointing at the elastic IP address that your EC2 instance is assigned. You should also create another A record for www.domain.com pointing at the same IP.
For your second question, as soon as you set up your registrar correctly the interface for creating records should just go away. You'll be managing all of your DNS records through Route53 instead.
I have a Ghost blog running where the domain is set to www.mysite.com on their end and two CNAME entries set to the following:
Host:www Points to: mysite.ghost.io
Host: # Points to: mysite.ghost.io.
I want to run the blog off of a subdomain, preferably blog.mysite.com and use www and the root of my domain to run a separate site hosted by my hosting service.
Would this involve simply changing the CNAME information on my host at iPage to the following.
Host: blog Points to: mysite.ghost.io and removing the original two entries listed above?
I think your assumption to just add a CNAME that points blog to mysite.ghost.iois correct. If you would like to only forward the blog subdomain the two entries for wwwand # are not needed. These entries should point to the separate hosted site.
You can find more information about how to use a custom domain with ghost.io here: https://ghost.org/blogs/domains/.
How do I redirect a dynamic subdomain to the same subdomain on a different domain?
*.example.com to *.example2.com
Can this be handled with Zerigo?
Depending on your exact requirements, you could achieve that with a DNAME record:
For example, you could have the following in your example.com zone file:
example.com. IN DNAME example2.com.
and a pretty standard example2.com zone, you can mostly achieve the effect.
Querying dig www.example.com, you'd get:
example.com. IN DNAME exmaple2.com.
www.example.com. IN CNAME www.exmaple2.com.
However, if you had DNS records that you need directly under either zones, e.g. an A, MX or TXT record, they don't "alias" so you need to store them in both zones.
In any case, DNAME is not supported in most DNS providers (Zerigo included) that only gives you a web interface, so you'd need to run your own DNS server.
In DNS you can not redirect, that is an HTTP function. But what you can do is use CNAMEs. A CNAME take a dns name and under the covers resolves it to another name. For example:
www.example.com resolves to www.example2.com. In the web browser the user will see www.example.com though.
What you will want to do is look into "wilcard CNAME". There is a limitation though. A wildcard CNAME will only point to a single address. This means that:
*.example.com will only ever point to a single address at example.com2 (let's say you pick bang.example2.com)
foo.example.com -> bang.example2.com
bar.example.com -> bang.example2.com
baz.example.com -> bang.example2.com
cux.example.com -> bang.example2.com
It is also important to note that not every DNS provider allows for wildcard CNAMEs. Also, not every DNS server allows wildcard CNAMEs. If you really want to have a wildcard CNAME point to the corresponding entry in example2.com, then you may want to look into powerDNS. It allows for 3rd party plugins written in various languages like lua. It also can be backed by a mysql, postgress, ldap, or a sqlite backed. This means that you can add that functionality yourself if it does not already exist.
Good luck
I'm trying to connect my Tumblr with my custom domain - currently I have no A records, just two CNAME records:
*.mydomain.com -- domains.tumblr.com
www.mydomain.com -- domains.tumblr.com
My Tumblr is set up to connect to www.mydomain.com and currently it works correctly when I access it via www.mydomain.com; however, I need to make the http://mydomain.com address also work. I have no idea how to do this.
the official tumblr document as of writing says do an A record for the mydomain.com to the Tumblr IP, OR use a CNAME if it is www.mydomain.com you want to use to domains.tumblr.com. http://www.tumblr.com/docs/en/custom_domains
I think you can do both also but not tried this yet. (Seen referenced in other posts on SO).
Add a CNAME record for the second-level domain as well:
mydomain.com -- domains.tumblr.com
The version *.mydomain.com would affect only domains like foo.mydomain.com and bar.mydomain.com, not the second-level domain itself.
I have a server that already has a domain, lets say mysite.com but i want to put another site on it with the domain mysite2.com.
So my questions are, how do i set up the nameserver settings.... My first domain i have listed
ns1.mysite.com
ns2.mysite.com
So would it work if i used:
ns1.mysite2.com
ns2.mysite2.com
for my new site?
Also, i have to set up "glue records". These are the ns1 and ns2 from the nameserver and provide the ip of my server. So for the mysite2.com would i use ns1.mysite2.com and then the ip would be for example 111.111.111.111/MYSITE2 ? Because the glue record for the first site is just 111.111.111.111.....?
Hope this isn't to confusing, i'm just new to this stuff and want to understand it a bit better and i don't want to mess my original site up in anyway.
thanks for the help.
Your DNS records don't have to be within the same domain as the one they host. If you are running your own DNS servers, they can live inside your primary domain. But if you're using another DNS provider like zoneedit.com or easydns.com, just use the hostnames they provide.
"Glue records" are the NS pointers that let the root servers find the DNS servers for a particular domain. For example, there might be:
mysite.com NS dns1.example.com
mysite.com NS dns2.example.com
mysite2.com NS dns1.example.com
mysite2.com NS dns2.example.com
Note that this is entirely different from where your domain's web site is served. For that, you just configure the DNS for each of these domains so that the IP address for the "www" host (and probably the domain itself) points to the same IP ... then you read your web server software's documentation on how to set up "named virtualhosts".
Are you clear on the distinction between DNS hosting and web hosting? If not, I can go into more detail.