nslookup seems to work fine but ping cannot reach my nameserver
Published 3 years ago • No plays • Length 1:50Download video MP4
Download video MP3
Similar videos
-
2:28
nslookup not working but ping and traceroute with icmp does work fine
-
2:28
nslookup can resolve but ping cannot
-
1:38
dns unable to resolve but can ping and use nslookup using fqdn?
-
9:14
ping command - troubleshooting networks
-
2:10
dns resolution issue nslookup works, but web/ping doesn't (3 solutions!!)
-
2:39
how to fix when i can nslookup and dig an internal hostname, but i cannot ping
-
3:04
fix dns_probe_finished_nxdomain in chrome | how to solve dns probe finished nxdomain on error chrome
-
1:24
windows 10 - can ping ip but cannot ping hostname on my lan
-
9:32
how to allow ping requests through windows firewall
-
3:51
how to fix nslookup error default server unknown in windows server 2022, 2019, and 2016
-
4:04
windows 7 dns not working (nslookup is working; ping -4 name.com not working) (5 solutions!!)
-
3:04
can ping ip address and nslookup hostname but cannot ping hostname temporarily in windows
-
1:18
ping, nslookup and tracert works, but i can't access server via browser - any ideas?
-
2:26
devops & sysadmins: can ping ip address and nslookup hostname but cannot ping hostname
-
10:39
why is 'ping' unable to resolve a name when 'nslookup' works fine? (22 solutions!!)
-
2:38
devops & sysadmins: nslookup works but ping doesn't
-
1:51
ping fails to find host but nslookup resolves okay on windows (2 solutions!!)
-
1:25
ping and nslookup work, browsing doesn't
-
1:19
ping/nslookup working but telnet/browser fails
-
2:06
what does it mean if nslookup and ping fail to resolve a host name but tracert does not?
-
2:22
devops & sysadmins: nslookup works but ping fails with dns error randomly
-
2:01
why can't my browser resolve host, but ping and nslookup can? (2 solutions!!)