website does't work in some network - dns

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

Related

Why cant i access websites via proxied Cloudflare?

I Live in Estonia.
The second day I observe some kind of problem with the opening of some of my sites.
Example:
https://cp.nasdaq.ee - sometimes it works, sometimes it doesn't
https://185.252.232.227:8888/ - this is the same site cp.nasdaq.ee, but via IP - always opens properly
If the site is down and i enable the VPN, then it starts working.
In all other countries, the site opens without problems https://www.host-tracker.com/ru/ic/4/697585f4-486b-4c8e-b530-e3f0b6c96972/
This problem have all of my friends (5 men) who live in Estonia.
Perhaps the problem is somehow related to the fact that cp.nasdaq.ee has NS servers in the Cloudflare.com zone, but not all sites connected to Cloudflare have the problem.
I observe the problem only for those sites that are connected to Cloudflare and their A-record leads to ip 185.252.232.227.
If IP 109.205.176.239, 62.171.151.28, 62.171.151.28 are specified, then sites open without problems.
For your information,
all IPs listed are for VPS owned by Contabo.com hosting, the server is located in Germany.
The problematic IP 185.252.232.227 is from one VPS on Contabo, and all the other IPs I listed are from another VPS on Contabo.
And if i turn of status Proxied at CLoduflare.com and set DNS ONLY - then website works well!
Here is such an incomprehensible problem ...

How to setup subdomain for digitalocean?

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.

Godaddy DNS Zone configuration

German Mail Providers like GMX or T-Online are blocking my emails. A support guy from GMX said the a-record for mail would be missing. I added it.
Now I checked this site and got 5 warnings http://mxtoolbox.com/domain/x-invest.net/ I also added a SPF record, but there are still problems with some providers. From some providers I even did not get any mailer daemons.
My IP adress or domain is not blacklisted by any of those providers.
I am worried about doing the DNS setup wrong on my apache server, but actually it should be a copy of my setup, I used with another server before.
Here is a screenshot of all I have at this time:
Maybe you could help me out, if I was missing something important or even have wrong dns record.
PS. Sorry, hope the screenshot is okay for the moderation. I was not able to copy the records - It was not my intention to spam my domain.
Clicking your link, the only ones I'd be real concerned are (in my order of priority):
Primary Name Server Not Listed At Parent
Name Servers are on the Same Subnet
The Certificate is invalid
First one indicates that your nameserver listed in the SOA record is not included at the level above you:
x-invest.net. 86400 IN SOA ns1.secureserver.net. info.s50-62-56-203.secureserver.net. 2015061806 86400 7200 3600000 86400
Which means that the server you listed as the authority for your domain does not match what the internet says is the authority.
Second one is more an issue if you have any sort of fault tolerance worries. If the ISP drops your subnet or circuit for some reason, your sites will not resolve.
Third one is only an issue if you have customers that are concerned about the security of their connection. The big red X in the browser address bar is very discouraging to customers and their credit cards.
EDIT (answer comment):
An authoritative DNS server is one that actually contains the information being requested: reference
DNS being a hierarchical structure, so it follows that the chain to get to your domain needs to be complete from the top down in most cases. You can bypass that structure in some circumstances, like private DNS domains being hosted by internal corporate servers. Internal machines point to the internal DNS servers, which host domains that may not be accessible to the outside, but will also do recursive queries out to the internet as an example.

DNS using BIND with Subdomains - Multiple Servers and Hosting Accounts

Hopefully someone can help clarify this.
I have a domain ie example.com registered with Go Daddy. I host the website with TSOHost so in my domain configuration, I have set the following NS records.
Nameserver 1: ns1.tsohost.co.uk
Nameserver 2: ns2.tsohost.co.uk
I am now able to serve the website both www and non www from this hosting package. I simply have an A record for example.com and a CNAME for www.example.com to point to example.com (this is being configured in the cpanel Advanced DNS Zone Editor). So now we have the website showing as expected and required.
I would also like to setup a kind of DDNS service using a different server entirely, (this will hold DNS records that I will create on the fly using a Radius database).
So I want to use the subdomain ddns.example.com for this DDNS service, ie bob.ddns.example.com for Bob (so that when I ping bob.ddn.example.com, I can alter the IP to 8.8.8. say). In Cpanel I have an A record for ddns.example.com and an A record for *.ddns.example.com to point to my server that will manage this, for example 85.214.214.214.
I have installed Bind on the server (currently using a digital ocean server for this, to which I have added ddns.exmaple.com as an A record to the droplet and *.ddns.example.com also), I have created a zone for ddns.example.com, within this I have set the ns record as the digital ocean details.
I have then added the following to my file /var/named/ddns.example.com.hosts
$ttl 38400
ddns.example.com. IN SOA ns1.digitalocean.com. jon#example.com. (
1414575123
10800
3600
604800
38400 )
ddns.example.com. IN NS ns1.digitalocean.com.
bob.ddns.example.com. IN A 8.8.8.8
When I ping bob.ddns.example.com on the server with bind installed I get 8.8.8.8, but when pinging for anywhere else I get the bind server IP.
Can I ask if what I am doing is possible ie, going from godaddy to tso, to another server and if so what NS records should I specify for bind? or is there something in the named config I need to change, I have set the following options in named.conf in an attempt to solve this issue.
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
allow-query { any; };
recursion yes;
I am aware that recursion may leave me open to DOS attacks and I intend to turn this to no eventually, but for the moment during testing I have left this to yes.
Any help or information would be greatly appreciated, I have been trying different variations of zone files etc without success, I am really though unsure as to if I am going in the right direction.
Hopefully I have made sense, but any further info I can provide, please let me know.
My first question would be - Are you sure you've updated the Registrar with this server as the DNS nameserver for this domain?
Use nslookup to find out:
# nslookup
> set querytype=NS
> server 4.2.2.1 (a DNS server on the Internet)
> ddns.example.com. (a closing dot helps avoid lookups using preferred search domains.)
and confirm that the Internet knows who to communicate with, and that your NS host is authoritative for the domain.
Next would be - Do you have any other nameservers up to "answer" for that subdomain, causing other problems?
BTW - glad to hear you fixed this issue!

DNS - Site with subdomains - A NAME, CNAME?

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

Resources