Windows 10: network lookup not working properly can find server via nslookup put not ping it

network lookup not working properly can find server via nslookup put not ping it


I can ping a server via ip but not via FQDN


but nslookup is providing the right IP for FQDN



can not map a network share via FQDN


fluhsed DNS already


any ieas?


Thanks

:)

 

ping doesn't resolve hostname, but nslookup does

That involves a different server. However, since you have an IP address that way try using it in a tracert. That way, you will be testing both ICMP (the protocol involved with a PING) and DNS because eventually tracert may decide to start showing you
some address names when it does a reverse lookup for the other addresses which would be involved in the PING. If you are blocked from using ICMP that might be enough to explain why you don't see the lookup which a PING would have to do.

HTH

Robert

---

 

NSLOOKUP and PING do not match

I read many articles about the different results between nslookup and ping, but I somehow feel I do not fit in any of the explanations.

Scenario: Windows 10 (latest updates) connected to a corporate VPN via SSTP. The VPN connection is configured to suffix the corporate domain on the DNS queries (but on my tests I experimented removing and adding this). My hosts file is empty,
except the comments that comes by default. I did a flushdns just before the commands.

On the server side there is a corporate webserver with specific rules when the connection originates from the internal LAN (or VPN) or from the WAN. The correct behavior was already observed in the past, so this "works". Next steps is experimenting other
machines.

Use Case:

• With the VPN connected, nslookup will use the LAN's Default Server and not my ISP DNS -> OK
• NSLOOKUP a certain fully qualified host name will give me it's internal LAN address -> OK
• PING the same fully qualified host name will give me the public WAN address of the corporate domain -> Not OK, unless the VPN is disconnected, in that case de results would be OK.

Opening a browser with the same fully qualified host name goes into the WAN access limited page (load balancer rules detecting the origin remote address), although the client host (my PC) is in the LAN via VPN. Using chrome's "net-internal" page I see the
browser is resolving the WAN address instead of the LAN address (item 2 above).

Again, I know ping and nslookup do not resolve names exactly in the same manner, but there is no DNS cache and the hosts file is clean, I would still expect ping to resolve the internal LAN address in this case.

Any ideas on further troubleshoot why the browsers seems to be resolving the names incorrectly?

Note; It may be me, but this latest windows 10 upgrade/update seems to have broken the network. Just a gut feeling from some glitches in the last weeks.

 

ping and nslookup shows different result

See below... Following commands run on my laptop..

C:\Users\han>nslookup sip.mycompany.com

Server: wsdc49.active.local

Address: 10.110.100.223

Non-authoritative answer:

Name: sip.mycompany.com.mycompany.int

Address: 220.250.64.26

C:\Users\han>ping sip.mycompany.com

Pinging sipdir.online.lync.com [52.113.64.147]

But there is a CNAME record on wsdc49 for sip.mycompany.com pointing to sipdir.online.lync.com. On wsdc49 I tried nslookup it showing fine.

PS C:\Users\han> nslookup sip.mycompany.com 127.0.0.1

Server: localhost

Address: 127.0.0.1

Name: sipdir.online.lync.com

Addresses: 2603:1047:0:2::b

52.113.64.147

Aliases: sip.mycompany.com