[ale] nslookup vs dig

[Gary Maltzen]

# nslookup www.clayton.edu dns.libertybay.com
Server:  dns.libertybay.com
Address:  209.247.83.140

Non-authoritative answer:
Name:    www.clayton.edu
Address:  168.28.243.100

# dig www.clayton.edu @dns.libertybay.com

; <<>> DiG 8.2 <<>> www.clayton.edu @dns.libertybay.com
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;;      www.clayton.edu, type = A, class = IN

;; ANSWER SECTION:
www.clayton.edu.        3h15m29s IN A   168.28.243.100

;; Total query time: 143 msec
;; FROM: ****** to SERVER: dns.libertybay.com  209.247.83.140
;; WHEN: Wed Sep  6 14:29:52 2000
;; MSG SIZE  sent: 33  rcvd: 49


----- Original Message -----
From: Dan Newcombe <Newcombe at mordor.clayton.edu>
To: ale at ale.org
To: ALE <ale at ale.org>
Sent: Wednesday, September 06, 2000 11:52 AM
Subject: [ale] nslookup vs dig


> Okay...to me it seems that
> nslookup
> > server ns.somewhere.com
> > www.something.com
>
> should return the same thing as
> dig @ns.somewhere.com www.something.com
>
> Yes?/No?
>
> My quandry is thus:
> nslookup against dns.libertybay.com for www.clayton.edu returns
> 168.28.243.100.   dig @dns.libertybay.com www.clayton.edu give me
> connection timed out.
>
> Do these go at it different ways?  I'm just trying to convince myself it's
> the ISP at fault, and not my DNS server.
>
> -Dan
>
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
body.
>

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.