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.
Related
I changed DNS provider recently and I am trying to add DNS records to my new provider. However, I am unsure about how many records I should add.
My old nameserver had a whole bunch of auto-created records like "ftp.example.com", "cpanel.example.com", "_carddavs._tcp.example.com", "webdisk.example.com", "autodiscover.example.com", etc etc.
So my question is, can I just add the below TWO A records?
# ---> A Record pointing to my host IP address
www ---> A Record pointing to my host IP address
Any replies would be greatly appreciated!!
This question is akin to asking 'how many contacts do I need in my address book'
If you only have one friend, then a single record is all you need. (I'm ignoring the required SOA and NS records)
If you are going to have something talking to ftp.example.com then go ahead and add that record.
If you want to recieve mail on that domain, then you will need at least one MX record.
If you want to host a website at www.example.com then you will need to add a www A record. (or if you want to host a website at notwww.example.com, then add that A record)
Fill your DNS up with whatever you need it to have.
The reason for all of the already included options is that they lead off to revenue generating pages for whoever hosts your domain.
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 have a GoDaddy domain www.exmaple.com which points to 255.255.255.255 (fake IP of course). My web server is behind a router that forwards port 80 to the appropriate port. All fine and dandy. However, like 99% of people out there, I have a dynamic IP. So I set up a hostname with noip.com called helloworld.ddns.net, set up their update client on my server (so it can update them whenever the IP changes (hasn't happened yet but i'm hoping it works as advertised), and then went to godaddy.com to change my records. Which is where stuff gets as hairy as harambe.
I started off by removing my A record, and changing my CNAME to point to helloworld.ddns.net.
Didn't work.
Googled around, and found that I need/should use the noip NSs. So I went back to godaddy, and changed my nameservers from theirs to the noip ones... ns[1,2,3,4,5].no-ip.com.
Still doesn't work. Should also point out, that after I made this change I lost the ability to set any records on my domain name. Which I guess makes sense since there's no point in godaddy having a record if I'm not using their NSs.
Tl;dr: How do I point godaddy domain, www.example.com, to a noip hostname, helloworld.ddns.net, which in turn points to my dynamic home ip, x.x.x.x.
Finally managed to solve my own issue, and I feel very silly for not realizing what the issue was before. The problem was that the CNAME was pointing to a subdomain (www) and therefore one couldn't access the site without including this in the URL. Summarised solution:
GoDaddy now has CNAME with a specific host name (ex www) and the noip domain as the value
No A record
Kept the default GoDaddy NSs
Configured forwarding w/o masking, to www.example.com... therefore, when someone tries to access example.com, they are automatically forwarded to the www subdomain.
A little bit of patience for propagation and everything was up and running.
We are running BIND 9.9.7 on Centos 6.5 and for a long time I have been creating "hostless" DNS entries so that sites work with or without the www.
Eg:
www IN A 192.168.1.1
domain.com. IN A 192.168.1.1
However, our client wants to use a CNAME record to a cloudfront host and the "hostless" entry doesn't work as a CNAME record.
In fact, it more than doesn't work, BIND won't even load the zone file. The error is
"failed: CNAME and other data"
domain.com. IN CNAME host.cloudfront.net.
www IN CNAME host.cloudfront.net.
It will load and resolve fine without the domain.com entry. I have tried a few variations, but nothing seems to work. including "", "."
Can anyone tell me the correct syntax for this entry?
There is no correct syntax for this (and it is not BIND specific, it is a side effect of RFC1912 which states that A CNAME record is not allowed to coexist with any other data.
Detailed explanation: Why can't a CNAME record be used at the apex (aka root) of a domain?
Some DNS providers might offer workaround hacks.
I'm hosting a clients site at client.mysite.com, but my client want to have its own domain, like www.clientsite.com.
With a CNAME configuration, I'll be able to hook my client domain to the content, but... considering I'm still hosting my clients content, which domain will be finally listed on Google with contents of client.mysite.com contents?
a) mysite.com
b) clientsite.com
Thanks for helping.
In the DNS hierarchy, the CNAME resource record will be attached to the clientside.com. A CNAME is simply a reference to the location of that site's A record. With that in mind, I believe mysite.com will be listed as hosting the data.
Does your client want it to appear under his name?
If so, then this should not be solved using DNS (well, not only using DNS).
If your client wants to get the content listed under his domain name, the best way to do this, is to add their name to your server.
Then point client domain name to your server.
The best way to do the pointing (when also considering SEO)
is to make an webforward (301 permanent) from the root, to the www
and make the www subdomain point to the ressource.
(Or vice verca)
IF you are using the example above (webforward on root) you can use a cname instead of an A record to point the domain name. However do not add a cname to the root of a domain (effectively shutting down your domain name).
So-
Short Answer:
client.mysite.com will have the content (also according to google).
Any attempt to obfuscate this is black hat or grey hat ;)
a better way of doing it is to simply setup the clients domain name on your server.
Then point only one hostname to the server. Server host/headers will take care of the rest.
Setup in DNS
# webforward 301 www
www a or Cname to server
Quick rules:
NEVER put Cname on the root of a domain
Only allow 1 hostname to show content (can be done both as explained above via DNS/webforward or via server configurations)