/etc/hosts file has an entry in my development server 10.xx.xx.162 server-dev.xxx-intra.net. ping to server-dev.xxx-intra.net is successful.But when I am trying to access from the browser - https://server-dev.xxx-intra.net, it throws server-dev.xxx-intra.net's server IP address could not be found. I understand that it is not able to resolve that name to IP but shouldn't /etc/hosts entry have taken care of this? Please let me know if I am missing something.
Related
I set up our custom DNS server in AWS and looks like doing nslookup a dns works fine in forward but if I do nslookup it in reverse like using its IP, it gives me an error as below
** server can't find x.x.x.x.in-addr.arpa: NXDOMAIN
I can do nslookup any other public dns and IP back and forth but can't do nslookup a IP for some reason.
FYI, I used an internal IP to set this up.
Could you please give me any suggestions to resolve this?
Thanks,
My domain isn't resolving and I have pinged the IP address but it shows there is 0% packet loss. But when I go to the site in a browser, it can't connect to it.
I've tried for few hours to figure this out, and there is so much information out there but I feel like I've tried it all. I have checked my DNS settings, and I have checked my server logs for errors etc. What could be wrong?
I hope this isn't too much of a noob question, but I am kinda new to DNS stuff. I've done it before but find it hard to figure out the cause if something does go wrong.
In order to troubleshoot DNS issues, here is a list of common troubleshooting steps:
Double-check your DNS settings:
This means checking that your A record(s) is/are correct, and that they point to a valid (and the correct) IP address; checking that your CNAME record(s) is/are correct. Also check other records, if applicable;
Try visiting your website by entering its IP address into the Address Bar of your browser. If you still cannot connect to the site in a browser, it is likely that you are entering the IP address incorrectly, or that your provider is experiencing server or DNS problems, or that your DNS Server is not configured correctly (if you are running your own DNS Server). In this case, I would contact your provider, or go back to the documentation for the DNS Server you are using;
Flush your DNS cache. You can do this by entering the following command at a Command Prompt: ipconfig /flushdns, and then pressing Enter;
Ensure that your Hosts file contains valid entries. You can find out more about the Hosts file at the following address, which also contains a link to download a Hosts file with default configuration:
How can I reset the Hosts file back to the default?
I have 2 servers which are located in different networks. On each of them IIS is installed. When I try to connect to the first IIS server from the second, it gives me error: "Could not connect to the specified computer. The remote name could not be resolved". Fierwall is switched off. Maybe I should configure something in DNS or somwhere else?
Update:
Ping is ok, no packages are lost.
What happens when you "ping" the address from the command prompt?
If it comes up with host not found, then you either need to configure DNS on the server trying to get to the remote computer OR create a static hosts file entry pointing the name to the ip address...
i have few Centos 5.1 servers, recently they took very long time to communicate eachother, it looks like for every request it checks local server in public dns, is there is anyway to give option in /etc/resolve.conf to disable dns for some IP address ?
Add the server names and their IP addresses to the file /etc/hosts, e.g.
10.0.0.100 server1 server1-alias
10.0.0.101 server2
and then make sure that you list the keyword files before the keyword dns for the hosts entry in /etc/nsswitch.conf, i.e. that file should have a line that looks something like this:
hosts: files dns
After that, any attempts to resolve hostnames or IP addresses will first consult the /etc/hosts file, and only if that is unsuccessful go on to do a DNS lookup.
If I have a valid signed SSL cert, I can see the CN (common name) attribute does not have localhost or the LAN IP - but I do not see an SSL error "ssl_error_bad_cert_domain" when I connect to https://localhost. Surprisingly,I have seen this error (only in some cases) even if I connect to the public IP instead of hostname.
Can someone please help me with a reasoning ? I wonder if DNS (or say hosts files) would tell this resolution to the browser !