I have setup o DNS service on Window Server 2019.
I have an A record (A) that is:
web.metroman.gr -> 192.168.99.213
The nslookup answer
nslookup web.motorman.gr
Server:winsrv2019dc.int.motorman.gr
Address: 192.168.99.200
Name: web.motorman.gr
Address: 192.168.99.213
But when I try the "web.motorman.gr" from a network pc, they go to google like I search for that. I have try Edge, Firefox, Opera, they do the same.
If I write "http://web.motorman.gr" they work fine.
How can I solve that?
Thanks in advance
Related
I have create a very simple site in IIS Server version 8.5 using port 85. The site only have one index.html that shows the word "test" the page. When I access the site inside the server I can access it successfully: "http://localhost:85" is working.
Trial 1:
I try accessing it from my computer that is connected to the same network with the server using url "http://servername.test.com:85", the browser goes loading for long time and finally ends in with error "Connection Reset".
Trial 2: I try updating the Site Binding's Host name with our "Vanity Name" and "IP Address", but after this I still get a "Connection Reset" error.
Trial 3: Now I also check for opened ports using netstat, and I can see that port 85 is open. So I don't know why I'm getting Connection Reset error
Trial 4: I added Connection timeout value on the settings. But still I'm getting Connection Reset error.
Please kindly help with advise how to fix this Connection Reset issue. I can't find what is the reason behind this issue. Thank you in advance.
According to your description, I guess you may not bind the right IP address for the servername.test.com domain or use the wrong ip address bind with servername.test.com domain.
I suggest you could firstly try to use the server's ip address to access your web application to make sure you firewall setting and IP setting is right.
If your client server and the IIS server are in the same domain and you have installed an DNS server, then you could access the web site by domain. Details about how to set the DNS server, you could refer to this article.
If you just want to test, you could try to modify the hosts file in the C:\Windows\System32\drivers\etc path in your client server.
For example:
127.0.0.1 www.example.com
I've found the solution. I issue was caused by Firewall enabled on the server and the ports are not opened by the Network Administrators. So I just opened the Ports that I will be using and it works now. Installing IIS Failure Tracing help me catch the error also. Thank you for all those who answered.
I am trying to connect to a university server using a VPN client. I can connect to the client. Also, if I ping the server by name and by IP address, they both work:
ping servername
ping serveripaddress
However, I cannot access the server from the browser if I type:
\servername
\serveripaddress
and also I do not see anything in Network apart from my own computer. I changed my Workgroup to the correct Workgroup, and it still doesn't work.
Also, as my DNS suffix I use the domain name as well as the FQDN, but it doesn't work either.
I restarted after each of these changes, but it didn't help.
I read that when I have a VPN connection working and I am also able to ping the server to which I want to connect, it is most probably DNS resolution problem. But I do not know anymore what to do (I checked and tried the correct DNS suffixes).
Do you know what should I do more? I am using Windows 7.
Thank you.
It sounds like you're trying to use UNC pathing. Assuming that you're getting your network settings from DHCP, are you getting a WINS server?
I can connect to my wifi (another laptop is fine on this network), however the browser will not load web pages, and I cannot ping google.com
One strange thing I have noticed is that if I look in /etc/resolv.conf the following lines are present:
#Generated by Network Manager
nameserver 8.8.8.8
nameserver 4.4.4.4
Where I am sure the second line should be 8.8.4.4. So I change the second line to this and check again that the change has been implemented.........which it has.
However, I then reconnected to the wifi and my changes had been wiped and had changed back to:
#Generated by Network Manager
nameserver 8.8.8.8
nameserver 4.4.4.4
Is this behavior normal?
This problem is also intermittent. Sometimes my browser works fine and I can ping google.com, others times I get this problem.
What seems to be the issue?
update:
I can successfully ping google by IP (216.239.39.99)
browser still not able to load websites however.
Wether this is conincidence or not, in my chrome browser I went into advanced settings and turned off the "allow google to predict urls" option and voila I know have internet.
I am new to windows server. I just installed DNS on windows 2012 server. Here is how it appeared after installing
Then i went to DNS manager. I created a new Forward Primary zone and reverse zone. Here is the screen shot
Then i created the record (A, MX, CNAME). Here are the screen shots of each
SOA:
Name Server:
A Record:
MX Record:
CNAME:
Reverse lookup Zone:
After all that when i do nslookup, then i get Default Server: Unknown. Why ? Why i am getting unknown server
Why i am getting unknown ?
Thanks
You did all correct, but you dont mentioned are you restart DNS service after that? After restart its working fine for me.
From the quick google research it seems to be a reverse PTR record issue. Try recreating the PTR record. Here is a NSLookup Unknown troubleshooting for a bit older version. This might work for Server 2012 as well.
Having some issues running my code local.
I have host file setup like this:
127.0.0.1 ryan.local.myappname.com
if I ping that URL it kicks back from 127...
but if I browse there in firefox or IE it takes me to an old version of the site that is currently live instead of taking me to the local one...
I am running Windows 7
Any ideas?
copied: https://serverfault.com/questions/65903/host-file-set-ping-goes-127-0-0-1-but-in-browser-url-still-goes-out-to-web
A common reason for this problem is that you're using a proxy that does the DNS resolving for you. This way your browser never tries to resolve the host name, but simply passes it on to the proxy, which of course doesn't use your host file entry.
Answer per serverfault:
ipconfig /flushdns
Worked like a charm.