I am launching the site with many subdomains. Currently when I'm tweaking it on my hosting using hosts file to point to the IP address all if fine. But when I made it live for the whole world, some parts are broken and do not want to load. for example the www and others.
I'm using a third party DNS for DNS. What should I use A NAME records or CNAME records to make it work.
Currently I have 2 records for A records:
localhost
and mydomain IP address
in CNAME I have:
two records for mail and ftp
What type of record you should use depends on what you are referencing to:
A records are used to reference an IPv4 address. (173.194.70.100)
CNAME records are used when referencing to another DNS name (google.com)
I don't understand why you want to make a DNS record that points to localhost. Since localhost like 127.0.0.1 always means the local machine anyone trying to connect to that address will connect to their local machine.
Some good examples of the use of common DNS record types: http://www.debianhelp.co.uk/dnsrecords.htm
Related
I need to access my Digitalocean server by typing sendy.ambee.app in the URL. If I type the IP address 157.230.9.219, it works.
But as long as I type sendy.ambee.app, it does NOT work.
When I ping sendy.ambee.app in terminal, it pings the correct IP address (157.230.9.219). Same thing when I try it here https://asm.saas.broadcom.com/en/ping.php
This is my Google domain's Name Space settings:
Shall I change Name servers? Just note here, on my ambee.app domain I use Google Workspace (so I do want to keep google servers for the main domain)
What else shall I have set up in there (in Google Domains DNS settings)? This is what I got so far:
I'm confused about many options there
shall I add A record in Custom resource records
or shall I forward sendy.ambee.app → 157.230.9.219 in Synthetic records
or shall I set sendy.ambee.app → 157.230.9.219 in Registered hosts
?
Is there anything specific I need to set in Digitalocean settings?
------------ ↓ UPDATE (Dec 15, 2020) ↓ --------------------
It seems that the problem is with Google Domains provider since I tried to test it out a different provider that I have and I created an A record for sendy.ambeeapp.com ->157.230.9.219 and it works without any issue (try http://sendy.tomasbaran.com to see for yourself).
Another thing is that I can't change the default Google NS servers, since I'm hosting Google Workspace on my main domain ambee.app.
To answer, succinctly, you want to add a custom Address mapping (A) record from the host name (sendy) to the IPv4 address (157.230.9.219) for your domain (ambee.app).
You should leave the name servers as they are; this configuration is necessary so that Google can manage your domain and resolve your records.
It's good to leave the defaults TTL but you can reduce these. Alternatively, once you've updated your DNS records through Google, you can check the resolver on Linux using either of the following:
nslookup sendy.ambee.app 8.8.8.8
nslookup sendy.ambee.app 8.8.4.4
NOTE 8.8.*.* are the IPs for Google's DNS service and will resolve quicky
It may (!) take some time (but usually not very long) for these updates to be shipped to other DNS resolves on the Internet.
It's unclear how you're able to resolve sendy.ambee.app to the IPv4 address (157.230.9.219) without changing your DNS records.
It's unlikely Google Domain's (i.e. Google's) DNS is at issue.
In the last month, my site no longer works on my computer or any computer connected to the same network that I use at home and I have tried other internet networks and the site doesn't work too, but strangely it works in some other networks!
The error message in the browser is : ERR_NAME_RESOLUTION_FAILED
I did not know the problem but when I looked at the site intoDNS I found 3 problems :
WARNING: One or more of your nameservers did not return any of your NS records.
------
You should already know that your NS records at your nameservers are missing, so here it is again:
ns77.domaincontrol.com.
ns78.domaincontrol.com.
-------
ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
208.109.255.49 216.69.185.49
Also, two months ago I moved my domain from Godaddy to Namecheap.
Please can you help me?
The domain's name servers are pointed to the servers of Godaddy, but there is no DNS zone for the domain there. You need to check what are the name servers of Namecheap (or another DNS hosting service) and point the name servers of the domain to these servers. Also you will have to create a DNS zone for the domain at the new DNS host (Namecheap or other of your choice) and create DNS records pointed to your web host's IP address.
If you only have a web site and no other services, like mail server you can only create two A records, like this:
Type: A
Host: # (or empty, it means the same)
Target (or Value, or Points to): ip.of.web.site
Type: A
Host: www
Target: ip.of.web.site
When troubleshooting DNS issues (specifically whether a domain is resolving), what is the proper way to check so that you get accurate results? DNS info is cached throughout the internet, and different machines (like local machine) or service (like pingdom) has different results.
How to check the DNS so that you know what you will get after it propagates?
Working with Heroku and CloudFlare.
In most common cases you can use tools such as: dig or host. Both tools are made for query name servers to retrieve info. You can also use a simple "ping something.domain.com" in order to see if IP has changed. But I suggest you to use different DNS's on the computer you're using to test. Actually Google DNS replicate so fast ( 8.8.8.8 ).
Not on purpose DNS poisoning: Keep in mind if you're pinging something that is recently configured/changed on your name server and still not propagated you'll "poison" the DNS's cache and this data is going to expire, but later...( Always depending on domain name TTL's of course ).
Using a new DNS wich never has known that domain you're sure the request is made for the first time and it's going to be made without asking any cache.
Example:
To get all the DNS servers for domain.com:
$ host -t ns domain.com
domain.com name server ns2.domain.com.
domain.com name server ns3.domain.com.
To ask a domain name for something.domain.com:
$ dig #nameserver something.domain.com
You can also ask for TXT, CNAME types and so on...
Examples:
AXFR retrieval test:
$ dig #domainname domain.com AXFR
Or get all Mail Exchange (MX) server for a domain:
$ host -t MX domain.com
domain.com mail is handled by 10 smtp.godo.com.
domain.com mail is handled by 20 smtp2.godo.com.
Hope it helps.
Cheers! :)
http://en.wikipedia.org/wiki/Nslookup
To get a "Non-authoritative" answer from your local name server that would be e.g.:
nslookup test.com
To check the name server where the domain is listed that would be e.g.:
nslookup test.com nameServerOfTest.com
My host has changed my IP address in my VPS hosting. This was a planned change they asked me when will it be good for me.
When they've changed my IP I managed to change the 2 nameserver's IP at my domain host so they will point to the new ip now.
I'm using kloxo and I have changed the DNS records for my main domain. It is working correctly with the new IP address now.
However I'm hoiting other domains there aswell but they just can't seem to be loading those sites...
Can anyone please tell me what could be the problem? Maybe change their DNS to the new ip aswell? (But if I do that, won't all my domain point to the main domain?)
The DNS records for those other domains will also need to be updated. Provided that you've correctly set up your VirtualHosts (or equivalent), then changing the A-records of the other domains to match the new IP of your server shouldn't cause any issues.
I need to get a reverse DNS entry into my zones file for one of my domains hosted under Plesk 9.2.2. Does anybody have ANY idea how this done? If all else fails I will have to update the zones file myself, but I am not sure how that will affect the front end working.
The reverse DNS entries are actually held by the people who manage the IP address space for the server, so typically they will need to make this change.
Lets say your IP address is 1.2.3.4, and you want to set up a reverse DNS record, what will actually be queried is 4.3.2.1.in-addr.arpa, which will return a PTR record, which would be a domain, or sub-domain with an A record that matches 1.2.3.4.
If you talk to the people who manage your IP addresses, they should have this configured to respond to PTR records.