nslookup fails on windows 7
-
I tried switching off IPV6 but it didnt work it shows "DNS request timed out timeout was 2 seconds" almost every time these is the DNS communication as captured by wireshark when I type 'nslookup' and open the program
5 4.080346 192.168.1.6 192.168.1.1 DNS 84 Standard query 0x0001 PTR 1.1.168.192.in-addr.arpa
6 4.336621 192.168.1.1 192.168.1.6 DNS 113 Standard query response 0x0001 PTR 1.1.168.192.in-addr.arpa PTR D-Link.DSL2740Band when I type 'facebook.com'
21 12.931466 192.168.1.6 192.168.1.1 DNS 81 Standard query 0x0002 A facebook.com.DSL2740B
22 12.965884 192.168.1.1 192.168.1.6 DNS 156 Standard query response 0x0002 No such name A facebook.com.DSL2740B SOA a.root-servers.net
23 12.966017 192.168.1.6 192.168.1.1 DNS 81 Standard query 0x0003 AAAA facebook.com.DSL2740B
29 14.976087 192.168.1.6 192.168.1.1 DNS 72 Standard query 0x0004 A facebook.com
30 14.980174 192.168.1.1 192.168.1.6 DNS 88 Standard query response 0x0004 A facebook.com A 173.252.89.132(first field is the packet number,second:time,third:source IP fourth:dest IP fifth:protocol sixth:length seventh:description) why is my gateway's name appended on facebook.com (facebook.com.DSL2740B) when I type set type=mx or set type=all the MX and ANY queries are sent and there is no reply any help ??
-
I tried switching off IPV6 but it didnt work it shows "DNS request timed out timeout was 2 seconds" almost every time these is the DNS communication as captured by wireshark when I type 'nslookup' and open the program
5 4.080346 192.168.1.6 192.168.1.1 DNS 84 Standard query 0x0001 PTR 1.1.168.192.in-addr.arpa
6 4.336621 192.168.1.1 192.168.1.6 DNS 113 Standard query response 0x0001 PTR 1.1.168.192.in-addr.arpa PTR D-Link.DSL2740Band when I type 'facebook.com'
21 12.931466 192.168.1.6 192.168.1.1 DNS 81 Standard query 0x0002 A facebook.com.DSL2740B
22 12.965884 192.168.1.1 192.168.1.6 DNS 156 Standard query response 0x0002 No such name A facebook.com.DSL2740B SOA a.root-servers.net
23 12.966017 192.168.1.6 192.168.1.1 DNS 81 Standard query 0x0003 AAAA facebook.com.DSL2740B
29 14.976087 192.168.1.6 192.168.1.1 DNS 72 Standard query 0x0004 A facebook.com
30 14.980174 192.168.1.1 192.168.1.6 DNS 88 Standard query response 0x0004 A facebook.com A 173.252.89.132(first field is the packet number,second:time,third:source IP fourth:dest IP fifth:protocol sixth:length seventh:description) why is my gateway's name appended on facebook.com (facebook.com.DSL2740B) when I type set type=mx or set type=all the MX and ANY queries are sent and there is no reply any help ??
Sounds like your DNS server isn't working properly. Try querying Google's DNS servers:
nslookup
server 8.8.8.8
set type=a
facebook.com
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I tried switching off IPV6 but it didnt work it shows "DNS request timed out timeout was 2 seconds" almost every time these is the DNS communication as captured by wireshark when I type 'nslookup' and open the program
5 4.080346 192.168.1.6 192.168.1.1 DNS 84 Standard query 0x0001 PTR 1.1.168.192.in-addr.arpa
6 4.336621 192.168.1.1 192.168.1.6 DNS 113 Standard query response 0x0001 PTR 1.1.168.192.in-addr.arpa PTR D-Link.DSL2740Band when I type 'facebook.com'
21 12.931466 192.168.1.6 192.168.1.1 DNS 81 Standard query 0x0002 A facebook.com.DSL2740B
22 12.965884 192.168.1.1 192.168.1.6 DNS 156 Standard query response 0x0002 No such name A facebook.com.DSL2740B SOA a.root-servers.net
23 12.966017 192.168.1.6 192.168.1.1 DNS 81 Standard query 0x0003 AAAA facebook.com.DSL2740B
29 14.976087 192.168.1.6 192.168.1.1 DNS 72 Standard query 0x0004 A facebook.com
30 14.980174 192.168.1.1 192.168.1.6 DNS 88 Standard query response 0x0004 A facebook.com A 173.252.89.132(first field is the packet number,second:time,third:source IP fourth:dest IP fifth:protocol sixth:length seventh:description) why is my gateway's name appended on facebook.com (facebook.com.DSL2740B) when I type set type=mx or set type=all the MX and ANY queries are sent and there is no reply any help ??
Member 10964099 wrote:
why is my gateway's name appended on facebook.com (facebook.com.DSL2740B)
This is because it is defined in the DNS Suffix Search List (type 'ipconfig /all' to see what is set). This list is mainly for resolving hosts in your local domain (no need to specify full qualified domains). To avoid this you can use the nosearch option or append a period (but I'm not sure if using a period is supported by Windows nslookup):
nslookup -nosearch facebook.com
nslookup facebook.com.Regarding the timeouts there may be multiple reasons. There may be for example firewalls blocking requests (on your system, on the gateway, or even by your ISP). It may be also a DNS server that responds with delays due to high system or network load. Did you never got an answer or is it working sometimes (especially after sending the same query again)? When sending the same query again, the DNS server on your gateway should have stored the result in his local cache meanwhile so that he can answer without forwarding the query. You should also try to use a known DNS server as suggested by Richard:
nslookup facebook.com. 8.8.8.8
This avoids forwarding the query through the DNS server of your gateway / DSL router to the DNS server of your ISP and should be therefore much faster.
-
Member 10964099 wrote:
why is my gateway's name appended on facebook.com (facebook.com.DSL2740B)
This is because it is defined in the DNS Suffix Search List (type 'ipconfig /all' to see what is set). This list is mainly for resolving hosts in your local domain (no need to specify full qualified domains). To avoid this you can use the nosearch option or append a period (but I'm not sure if using a period is supported by Windows nslookup):
nslookup -nosearch facebook.com
nslookup facebook.com.Regarding the timeouts there may be multiple reasons. There may be for example firewalls blocking requests (on your system, on the gateway, or even by your ISP). It may be also a DNS server that responds with delays due to high system or network load. Did you never got an answer or is it working sometimes (especially after sending the same query again)? When sending the same query again, the DNS server on your gateway should have stored the result in his local cache meanwhile so that he can answer without forwarding the query. You should also try to use a known DNS server as suggested by Richard:
nslookup facebook.com. 8.8.8.8
This avoids forwarding the query through the DNS server of your gateway / DSL router to the DNS server of your ISP and should be therefore much faster.
well the DNS server address default is my routers address I changed it to my ISP's DNS server's address and everything works well any idea why this happened only on nslookup while the rest of DNS worked fine ? also : it happened only on one router I moved to another house and it is working with any setting
-
well the DNS server address default is my routers address I changed it to my ISP's DNS server's address and everything works well any idea why this happened only on nslookup while the rest of DNS worked fine ? also : it happened only on one router I moved to another house and it is working with any setting
Other programs will work because they usually have a longer timeout than the Windows nslookup. It seems that your router is rather slow in forwarding DNS requests and answers. If it is an old model (slow CPU, little memory, old firmware) you should get a new one.
-
well the DNS server address default is my routers address I changed it to my ISP's DNS server's address and everything works well any idea why this happened only on nslookup while the rest of DNS worked fine ? also : it happened only on one router I moved to another house and it is working with any setting
Member 10964099 wrote:
I moved to another house
That's a bit of a drastic step, just to solve a DNS lookup issue! :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
