% cat /etc/resolv.conf ; generated by /sbin/dhclient-script nameserver 192.168.0.1
That looks like the typical address supplied by a consumer router, so it must be your Netgear. If dig works but nslookup doesn't, it's usually because the DNS server isn't supplying answers for your reverse zone. That's not uncommon in a consumer router, but check if Netgear has newer firmware to address that. nslookup, unlike dig, will try to resolve a name for the name server, and lack of reverse lookups makes that fail. Yet another reason that nslookup is deprecated. The Netgear should provide a reverse zone for 192.168.0.0/24, possibly with synthesized names.
