How to configure domain to open like www.domainname.com
Currently it is opening as domainname.com
Host -- Points To -- TTL Actions
# 45.40.137.206 1/2 Hour
CName (Alias)
Host -- Points To -- TTL Actions
email email.secureserver.net 1 Hour
ftp # 1 Hour
www # 1/2 Hour
You need to adjust DNS settings for your domain. You don't need CNAME record, instead you should add two A records for both domains (with www and without it), pointing to the same IP.
Related
I created a domain at freenom.com
https://imgur.com/a/ClaXVLX
which points to my app at Digital ocean droplet.
and next day I created this domain I tested and it works.
that domain is 1) at printscreen above.
Now I want to create several subdomains, as I know that is possible to make:
site.com - domain
dev1.site.com, dev2.site.com - subdomains
But I do not know what must be entered in fields 2) and 3) ?
When I tried as at printscreen above I got error :
Error occured: Invalid value in dnsrecord
Which are valid values ?
Thanks!
A domain name (for use as websites etc.) should point at an IP address. There are several kinds of DNS records. Records for pointing at IP addresses are A records, as you have in 1). Other kinds are MX records for mail servers, for example.
If you want to create a subdomain, you want to create another A record, so simply choose A for the "type" field.
Alternatively, if the IP is the same as an existing record, use a CNAME record which points to another record, e.g.
Name Type TTL Target
dev1.site.com CNAME 14440 site.com
This says that dev1.site.com should use the same record(s) as site.com, so if you ever update the A record of site.com, it will automatically apply to all subdomains too.
I found the way to
add two A record
A www.dev2 IP (same ip of your original website)
A dev2 IP (same ip of your original website)
Setup 2 subdomains on the Freenom DNS:
The CNAME record type does not accept a IP number.
For the subdomains, use a CNAME, but make the target the # sign, which represents the root domain.
To be clear, this will make both subdomains point to the IP address of the A record you specified for the root domain.
If you want the subdomains to point to a different IP, then use an A record instead of a CNAME record.
I recently updated my DNS to point to a new IP. When I ping the domain with and without www. I get different results (with the www I receive the old IP, without it I receive the new one). Is this just a DNS propagation issue in terms of timing? I have a catchall (*) set on the nameserver that the domain is pointing to.
In DNS, there are two records you need to update. It sounds like you updated the root or # record but there is also a www A record you need to update with the new IP.
I have a PHP application that must differentiate between different subdomains, and trying to better understand domains and subdomains. When I look at my GoDaddy Zone File, I see the following. This makes me think that my main domain mydomain.com points to 123.45.678, and several other subdomains such as ftp and www point to # which in turn points to my main domain 123.45.678, yet include their respective subdomain. Am I mistaken? I read http://www.webhostingtalk.com/showthread.php?t=470669 which is rather entertaining, however, never concluded the correct interpretation. Thank you
A (Host)
Host Points To
# 123.45.678
CName (Alias)
Host Points To
ftp #
www #
The '#' refers to the origin (your domain name, for example: mydomain.com) in the zone file. All the other records are hosts in that domain. For example 'www.mydomain.com' doesn't refer to a sub-domain, but rather a host in the 'mydomain.com' domain. By stating that they point to # (origin), this means all these 'hosts' are actually the same server. In essence your zone file says that you are running your FTP and web servers on the same physical host. If they were running on different machines, the # in those lines would be replaced by the actual IP addresses of those machines.
TL;DR: the 'www' and 'ftp' entries are hosts in your domain, not sub-domains.
I am using the Alternc control panel for shared hosting.
I am setting up a subdomain to point to github pages, as described here.
I need to point the CNAME record for my subdomain to .github.io, which I did with the alternc interface as seen in this image.
After waiting more than 24 hours, I got this message from github:
CNAME record should point to `your-username.github.io`, but it does not.
In effect, when visiting http://mxtoolbox.com/SuperTool.aspx?action=cname%3asommet.terredesjeunes.org&run=toolpage#, the CNAME record seems to be set to:
alberto56.github.io.terredesjeunes.org
not
alberto56.github.io
Same thing when running dig:
$ dig sommet.terredesjeunes.org +nostats +nocomments +nocmd
...
;sommet.terredesjeunes.org. IN A
sommet.terredesjeunes.org. 86400 IN CNAME alberto56.github.io.terredesjeunes.org.
I would be expecting to see the CNAME being alberto56.github.io, not alberto56.github.io.terredesjeunes.org. Is this a glitch with alternc, or am I not understanding something?
Thanks!
Albert.
Full DNS names need to end in a ., the root zone, otherwise the current zone is appended to the name. So, you want to set your CNAME to alberto56.github.io. with the terminal period to indicate that resolution should start from the root zone.
The glue record provider redirects "platform.domain.com to my DNS server. Now that I have dynamic control over this domain, I'm trying to forward all requests for this domain to to eu.loadbalancer.domain.com (a health check and server monitor) - so the user is redirected to a healthy and available server.
Because I can't resolve eu.loadbalancer.domain.com to a IP address, I have to use a CNAME (please correct me if I'm wrong on the latter statement).
My problem is that the zone file requires "# IN A"-record to be valid, and if I add a additional record for the #-alias, the zone file becomes: invalid.
So please help me out if you got any ideas. Thanks
$TTL 10
# IN SOA # platform.domain.com. (
1278075871 ; serial
10 ; refresh
180 ; retry
120 ; expiry
120 ) ; minimum
# IN NS platform.domain.com.
# 10 IN CNAME eu.loadbalancer.domain.com.
(this question probably belongs to serverfault.com)
This is a very common question. You can't have a CNAME at the same point as other DNS records. Section 3.6.2 of RFC 1034:
If a CNAME RR is present at a node, no
other data should be present; this
ensures that the data for a canonical
name and its aliases cannot be
different.
Try this instead:
# IN A w.x.y.z. ; IP address of an HTTP-level redirector
www IN CNAME eu.loadbalancer.example.com.
in other words, use the www prefix for the canonical URL, and push that off to your scalable web farm. Have the bare domain name go to a very simple web server which does nothing but HTTP redirects to the correct address.