On Tuesday, 28 May 2019 12:35:12 ACST Mark Misulich wrote: [...]
My laptop etc/resolve.conf file reads nameserver 192.168.1.1 It reads the same as the resolve.conf file on my desktop, nameserver 192.168.1.1.
[...]
OK, all good so far. [...]
~> dig @192.168.1.1 www.google.com
; <<>> DiG 9.11.2 <<>> @192.168.1.1 www.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45760 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 258 IN A 172.217.9.68
;; Query time: 29 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Mon May 27 22:50:23 EDT 2019 ;; MSG SIZE rcvd: 59
Good, so that proves that name resolution via your router is working when the machine actually tries to use it.
~> nslookup
nslookup never did provide any readout, after 15 minutes of waiting. [...]
That's because when you run nslookup with no parameters it starts an interactive nslookup shell. You then need to tell it which server to use (using 'server xxx.xxx.xxx.xxx' without the quotes), and then type the hostname to lookup Otherwise, if you simply run "nslookup <hostname>" it will use the default nameservers that your system is configured to use. Try it both ways. Nslookup <hostname> should tell you which nameserver it is trying to use to resolve the name. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================