Windows 10: NSLOOKUP PROBLEM

Hi everyone, I have an F5 DNS, I have configured his listeners ..... he resolves all URL asked with NSLOOKUP except the client URL he returns the IP of F5 listener when I do a nslookup -debug URL or nslookup -type=soa URL, it shows the right canonical name, to be sure that it's windows problem I had login with SSH to F5 and do dig it shows canonical name in ubuntu same thing. So if anyone can help to solve this problem I will be very thankful.

:)

 

Windows 10 1709 System Restore problems...


That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.

 

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.

 

DNS_PROBE_FINISHED_NXDOMAIN on all browsers… but I can NSLOOKUP fine


For a few days, I've been occasionally getting DNS_PROBE_FINISHED_NXDOMAIN in Chrome. The most recent issue is with accessing a Web page on fs.cibc.com.

• My DNS server is 192.168.1.1, my router, whose DNS servers are 8.8.8.8 (and 169.53.182.124; the secondary is irrelevant, since the router can reach 8.8.8.8)
• On my router UI's network tools, I can both ping 8.8.8.8 and do an nslookup on cibc.com.
• Same on my PC: opening up a command window, I can successfully ping 8.8.8.8 and do an nslookup on cibc.com.
• However, the issue occurs in all browsers.

Here's what I've done:

• I've reset Chrome's experimental flags.
• I've disabled/enabled my network connection. I rebooted afterwards.
• I've rebooted my router (but not my cable modem).
• I restarted the DNS Client service (from the command line—"Restart" is greyed in the Services window.)
• I've checked my hosts file.

Since I can lookup the domain's IP manually, and on the router, I'm at my wit's end. What else should I do?