BIND 4.9.4P1 / FreeBSD 2.1.0 weirdness

BIND 4.9.4P1 / FreeBSD 2.1.0 weirdness

Post by Miguel A.L. Par » Fri, 06 Sep 1996 04:00:00



Hello,

I've just installed BIND 4.9.4P1 on a FreeBSD 2.1.0 server.  This was
in response to a problem with the Squid proxy caching server continuously
complaining about not finding DNS names.  This happens -- 'masipag' is
the FreeBSD server.  Note that the authority records are the root name
servers, and not the actual servers for the domain.


; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 1, Auth: 9, Addit: 9
;; QUESTIONS:
;;      counter.digits.com, type = A, class = IN

;; ANSWERS:
counter.digits.com.     10716   A       206.101.96.152

;; AUTHORITY RECORDS:
.       93991   NS      E.ROOT-SERVERS.NET.
.       93991   NS      I.ROOT-SERVERS.NET.
.       93991   NS      F.ROOT-SERVERS.NET.
.       93991   NS      G.ROOT-SERVERS.NET.
.       93991   NS      A.ROOT-SERVERS.NET.
.       93991   NS      H.ROOT-SERVERS.NET.
.       93991   NS      B.ROOT-SERVERS.NET.
.       93991   NS      C.ROOT-SERVERS.NET.
.       93991   NS      D.ROOT-SERVERS.NET.

;; ADDITIONAL RECORDS:
E.ROOT-SERVERS.NET.     180391  A       192.203.230.10
I.ROOT-SERVERS.NET.     180391  A       192.36.148.17
F.ROOT-SERVERS.NET.     180391  A       192.5.5.241
G.ROOT-SERVERS.NET.     180391  A       192.112.36.4
A.ROOT-SERVERS.NET.     180391  A       198.41.0.4
H.ROOT-SERVERS.NET.     180391  A       128.63.2.53
B.ROOT-SERVERS.NET.     180391  A       128.9.0.107
C.ROOT-SERVERS.NET.     180391  A       192.33.4.12
D.ROOT-SERVERS.NET.     180391  A       128.8.10.90

;; Total query time: 169 msec
;; FROM: marikit to SERVER: masipag  203.176.0.6
;; WHEN: Thu Sep  5 12:02:46 1996
;; MSG SIZE  sent: 36  rcvd: 347

Compare it to a good one:


; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 1, Auth: 4, Addit: 4
;; QUESTIONS:
;;      counter.digits.com, type = A, class = IN

;; ANSWERS:
counter.digits.com.     85830   A       206.101.96.152

;; AUTHORITY RECORDS:
DIGITS.com.     172229  NS      DNS1.SRV.LYCOS.com.
DIGITS.com.     172229  NS      DNS2.SRV.LYCOS.com.
DIGITS.com.     172229  NS      NS.IBP.com.
DIGITS.com.     85830   NS      ns.galanter.com.

;; ADDITIONAL RECORDS:
DNS1.SRV.LYCOS.com.     172369  A       206.101.97.113
DNS2.SRV.LYCOS.com.     172369  A       206.101.96.113
NS.IBP.com.     172229  A       206.181.94.33
ns.galanter.com.        165226  A       206.42.166.47

;; Total query time: 98 msec
;; FROM: marikit to SERVER: makisig  203.176.0.3
;; WHEN: Thu Sep  5 12:06:17 1996
;; MSG SIZE  sent: 36  rcvd: 221

Thanks in advance for any feedback!

--

iphil communications, makati city, philippines           http://www.iphil.net

 
 
 

1. BIND 4.9 on linux?

I am wondering if anybody has successfully compiled and run BIND 4.9 on a
linux box...  Also, does the ninit program in the contrib directory of
the bind source work under linux?

                                        Tom Dylewski
                                        ErieNet

2. Ensoniq Soundscape - /dev/audio: No such device or address

3. Compiling BIND 4.9.3pl1

4. help: > 1GB discs => Kernel Panic

5. bind 4.9.? on Linux 1.0.9

6. Problem in running apache

7. bind 4.9 named setup

8. solaris 10 build 63 and lofiadm

9. Bind 4.9 for Solaris anyone?

10. bind 4.9.3B26 and Solaris2.4

11. BIND 4.9 with solaris patch

12. Has anyone ported Bind 4.9 for Solaris 2.x?

13. DNS - Solaris7 (BIND Migrationproblem 4.9-8.1)