Subject: Re: dig not working?
To: Danny Thomas <>
From: Michael L. VanLoon -- <>
List: current-users
Date: 03/30/1996 21:58:00
>matthew green <> writes
>>just a note:  i had the same problem when i compiled the bind
>>4.9.3-beta17 dig (which is 2.1, too, i think) a while ago.

>my copy seems to be working fine - that's dig 2.1 from bind-4.9.3 brought
>into NetBSD 1.1/i386 and built using the shres script. Apart from my own

Here's an illustration of the broken NetBSD-current dig.  Others have
acknowledged its brokenness, so I'm sure it's just a matter of time
until someone who knows what they're doing decides to figure out
what's wrong and fix it.  This is what it, and my old static one do:

[michaelv@MindBender]~> dir `which dig`
-r-xr-xr-x  1 bin  bin  45056 Mar 27 16:08 /usr/sbin/dig*
[michaelv@MindBender]~> dir /usr/local/bin/dig
-rwxrwxr-x  1 bin  bin  161538 Sep  9  1993 /usr/local/bin/dig*
[michaelv@MindBender]~> dig mx

; <<>> DiG 2.1 <<>> mx 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; Total query time: 408 msec
;; WHEN: Sat Mar 30 21:50:04 1996
;; MSG SIZE  sent: 31  rcvd: 225

[michaelv@MindBender]~> /usr/local/bin/dig mx

; <<>> DiG 2.0 <<>> mx 
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 10
;; flags: qr aa rd ra ; Ques: 1, Ans: 2, Auth: 3, Addit: 5
;;, type = MX, class = IN

;; ANSWERS:  360000  MX      5  360000  MX      10

;; AUTHORITY RECORDS:  360000  NS  360000  NS  360000  NS

;; ADDITIONAL RECORDS:       360000  A       360000  A       360000  A       360000  A       360000  A

;; Sent 1 pkts, answer found in time: 378 msec 
;; WHEN: Sat Mar 30 21:50:08 1996
;; MSG SIZE  sent: 31  rcvd: 225

>usage, DOC (Domain Obscenity Checker) from bind/contrib seems to find it
>OK. It's a pity DOC wasn't brought in to current because we should be
>encouraging people to *check* their dns zone delegation for mistakes.
>There's too much rubbish in the dns precisely because there is no culture
>of verifying dns setup.

That sounds useful.

>On the other hand the NetBSD 1.1 ping only works for me with IP addresses,
>so there's some problem for it to access the resolver. I'd probably have to
>rebuild it.

I have had no problems with general name resolution -- everything
there is working perfectly normal as far as I can see.  I do run my
own local named, which is authoritative for my own domain, and
otherwise is simply caching.

  Michael L. VanLoon                       
       --<  Free your mind and your machine -- NetBSD free un*x  >--
     NetBSD working ports: 386+PC, Mac 68k, Amiga, HP300, Sun3, Sun4,
                           DEC PMAX (MIPS), DEC Alpha, PC532
     NetBSD ports in progress: VAX, Atari 68k, others...