Date: Wed, 8 Aug 2001 20:01:27 -0700 From: Tony Saign <tony@saignon.net> To: "'Hassan Halta'" <hassan@cs.earlham.edu> Cc: <freebsd-net@freebsd.org> Subject: RE: DNS and nslookup problem Message-ID: <000001c1207f$9594fff0$0600a8c0@tsaignmobl> In-Reply-To: <20010808214918.R14553-100000@quark.cs.earlham.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Use DIG! Much better than nslookup! unstable# dig ibm.com (p.s. You really should cross-post, it's not polite!) -Tony ; <<>> DiG 8.3 <<>> ibm.com ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 5, ADDITIONAL: 5 ;; QUERY SECTION: ;; ibm.com, type = A, class = IN ;; ANSWER SECTION: ibm.com. 6H IN A 129.42.18.99 ibm.com. 6H IN A 129.42.19.99 ibm.com. 6H IN A 129.42.16.99 ibm.com. 6H IN A 129.42.17.99 ;; AUTHORITY SECTION: ibm.com. 3H IN NS ns.watson.ibm.com. ibm.com. 3H IN NS ns.austin.ibm.com. ibm.com. 3H IN NS ns.almaden.ibm.com. ibm.com. 3H IN NS ns.ers.ibm.com. ibm.com. 3H IN NS internet-server.zurich.ibm.com. ;; ADDITIONAL SECTION: ns.watson.ibm.com. 3H IN A 198.81.209.2 ns.austin.ibm.com. 1D IN A 192.35.232.34 ns.almaden.ibm.com. 1D IN A 198.4.83.35 ns.ers.ibm.com. 3D IN A 204.146.173.35 internet-server.zurich.ibm.com. 30M IN A 195.212.119.252 ;; Total query time: 69 msec ;; FROM: <snipped> ;; WHEN: Wed Aug 8 19:58:06 2001 ;; MSG SIZE sent: 25 rcvd: 300 * -----Original Message----- * From: owner-freebsd-net@freebsd.org * [mailto:owner-freebsd-net@freebsd.org]On Behalf Of Hassan Halta * Sent: Wednesday, August 08, 2001 7:54 PM * To: freebsd-questions@freebsd.org * Cc: freebsd-net@freebsd.org * Subject: DNS and nslookup problem * * * * Hi, * * Here's a problem, say I am using nslookup to look for * ibm.net, but when I * do that, I will get ibm.net.cs.earlham.edu instead on ibm.net * by itself, * or non existence domain...etc. At the beginning it seems to * be a missing * period problem, but I assure you it's not. A friend of mine fixed it * temporarly if she adds nslookup -nosea , and everything goes * fine, but if * someone is using us as a nameserver, that will not help. I * was wondering * if there are some ways to solve or debug this problem. * * Thanks, * Hassan * * * * * To Unsubscribe: send mail to majordomo@FreeBSD.org * with "unsubscribe freebsd-net" in the body of the message * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000001c1207f$9594fff0$0600a8c0>