bind - 9.5.0-P1

Chris Buxton cbuxton at menandmice.com
Tue Aug 12 15:13:03 UTC 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> In my host PC 2.6.21.5 linux kernel is running and in my target  
> board linux 2.6.24.7 kernel..
>
> In minicom i tried named -v
> it gave the version of the bind i.e 9.5.0.p1 and after this i tried  
> "named -c /dev/null -g ",
>
> 01-Jan-1970 05:31:07.363 starting BIND 9.5.0-P1 -c /dev/null -g
> 01-Jan-1970 05:31:08.283 loading configuration from '/dev/null'
> 01-Jan-1970 05:31:08.300 no IPv6 interfaces found
> 01-Jan-1970 05:31:08.304 listening on IPv4 interface lo, 127.0.0.1#53
> 01-Jan-1970 05:31:08.312 listening on IPv4 interface eth0,  
> 172.16.5.51#53
> 01-Jan-1970 05:31:08.344 default max-cache-size (33554432) applies
> 01-Jan-1970 05:31:08.357 automatic empty zone: 0.IN-ADDR.ARPA
> 01-Jan-1970 05:31:08.361 automatic empty zone: 127.IN-ADDR.ARPA
> 01-Jan-1970 05:31:08.363 automatic empty zone: 254.169.IN-ADDR.ARPA
> 01-Jan-1970 05:31:08.366 automatic empty zone: 2.0.192.IN-ADDR.ARPA
> 01-Jan-1970 05:31:08.368 automatic empty zone: 255.255.255.255.IN- 
> ADDR.ARPA
> 01-Jan-1970 05:31:08.371 automatic empty zone:  
> 0.0.0.0.0.0.0.0.0.0.0.0.0.0.A
> 01-Jan-1970 05:31:08.374 automatic empty zone:  
> 1.0.0.0.0.0.0.0.0.0.0.0.0.0.A
> 01-Jan-1970 05:31:08.377 automatic empty zone: D.F.IP6.ARPA
> 01-Jan-1970 05:31:08.379 automatic empty zone: 8.E.F.IP6.ARPA
> 01-Jan-1970 05:31:08.382 automatic empty zone: 9.E.F.IP6.ARPA
> 01-Jan-1970 05:31:08.384 automatic empty zone: A.E.F.IP6.ARPA
> 01-Jan-1970 05:31:08.387 automatic empty zone: B.E.F.IP6.ARPA
> 01-Jan-1970 05:31:08.469 default max-cache-size (33554432) applies:  
> view _bd
> 01-Jan-1970 05:31:08.563 none:0: open: /opt/TRIAL1/etc/rndc.key:  
> file not fd
> 01-Jan-1970 05:31:08.564 couldn't add command channel 127.0.0.1#953:  
> file nd
> 01-Jan-1970 05:31:08.566 no source of entropy found
> 01-Jan-1970 05:31:08.567 ignoring config file logging statement due  
> to -g on
> 01-Jan-1970 05:31:08.732 running
>
> Following things were displayed in the minicom,
>
> so is the binary is working properly????
>
> when i tried dig command
>
> dig google.com
>
> # dig google.com
>
> ; <<>> DiG 9.5.0-P1 <<>> google.com
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> it showed the following error,i have connected my board to LAN,so wt  
> might be the problem,should i need to modify .conf files(named.conf  
> or resolve.conf)


The binary is working fine. You should now add the following:

- - a source of entropy in the form of /dev/random
- - a file named rndc.key, at the path indicated in the error message

Your resolv.conf should list the server itself as a name server, like  
this:

nameserver 127.0.0.1

That's probably all you need in resolv.conf. You can also set up an  
explicit named.conf if you want something other than the default  
behaviors.

To make it run as a daemon but otherwise the same as above, simply  
remove the "-g" argument from the command line:

/path/to/named -c /dev/null

It will log messages to syslogd if syslogd is running.

Chris Buxton
Professional Services
Men & Mice

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkihqH8ACgkQ0p/8Jp6Boi066wCcD7VLWcHaMnfVYn9JPZQ9oKM4
XmIAn1wiciE3pldimg5k2f+dwUhgnbeJ
=EzJj
-----END PGP SIGNATURE-----


More information about the bind-users mailing list