[mrkelly]

I'm currently running BIND to provide name service for my internal network (not a very large one at all - just 3 machines). Recently one of my friends recommended using djbdns rather than bind. He said that it's easier to configure than bind. I'm still having some trouble with my setup and I'm not enjoying the dns configuration. Perhaps he didn't understand my "problem" with the configuration, but I honestly don't know enough about bind and djbdns to tell if there's any good reason to switch.

Or arguably, how should I have setup bind? My router (the openbsd box, also running a dhcp server) is properly identified to the network, but the other while two computers can use the dns server to retrieve names for the internet, I can't get intranet names to work. I can post the named DB files, if that's what I would need to change.

[elmore]

I use H2N for my local net at home, Basically just a fancy perl script which converts your hosts file to a DNS format, running plain old named.


Super easy setup, nothing else needs to be loaded and it works in a chrooted environment. Should take you all of 15 minutes to setup. You probably wouldn;t want to run this at an enterprise level company but for a home net with a few computers it completely rocks, or even a small to medium sized business. :D

[|MiNi0n|]

Bind/named is a tad confusing at first but it really is quite easy, especially when used in conjunction with h2n that elmore spoke of. Why don't you describe your problem a bit more and I'll see if I can help you out. I assume your using the stock bind/named for OpenBSD? So that would bind 4? Bind 4 is quite simple to setup.

Give me some details and I'll lend a hand.

[mrkelly]

Give me some details and I'll lend a hand.

I'm using the stock install w/ OBSD 3.1. Most of the "directions" I got came from NoMoa's OpenBSD Page (http://www.nomoa.com/bsd).

I'm including my named.boot, and my network's zone and rev files (I hope they come out right). Let me know if you want to see anything else.

bash-2.05a$ less named.boot
; @(#)named.boot 5.1 (Berkeley) 6/30/90

; boot file for secondary name server
; Note that there should be one primary entry for each SOA record.

; NOTE: if you are not chroot'ing named, change directory to /var/named/namedb
; OpenBSD chroot's named by default
;directory /var/named/namedb
directory /namedb

; type domain source host/file backup file

cache . root.cache
primary 0.0.127.IN-ADDR.ARPA localhost.rev
primary 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.0.ip6.int
localhost.v6.rev
primary 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.0.ip6.arp
a localhost.v6.rev
primary localhost localhost.zone
primary thoughts.net db.thoughts.zone
primary 0.168.192.IN-ADDR.ARPA db.thoughts.rev

; example secondary server config:
; secondary Berkeley.EDU 128.32.130.11 128.32.133.1 ucbhosts.bak
; secondary 32.128.IN-ADDR.ARPA 128.32.130.11 128.32.133.1 ucbhosts.rev.bak

; example primary server config:
; primary Berkeley.EDU ucbhosts
; primary 32.128.IN-ADDR.ARPA ucbhosts.rev

bash-2.05a$ less db.thoughts.zone
; thoughts domain database
@ IN SOA dream.thoughts.net. your_id.dream.thoughts.net. (
14 ; Serial
3600 ; Refresh
900 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS dream.thoughts.net.

; Addresses
localhost.thoughts.net. IN A 127.0.0.1
dream.thoughts.net. IN A 192.168.0.1

bash-2.05a$ less db.thoughts.rev
; thoughts domain reverse lookup database
@ IN SOA dream.thoughts.net. your_id.dream.thoughts.net (
14 ; Serial
3600 ; Refresh
900 ; Retry
3600000 ; Expire
3600 ) ; Minimum
0.168.192.in-addr.arpa. IN NS dream.thoughts.net.

; Addresses
1.0.168.192.in-addr.arpa. IN PTR dream.thoughts.net

[|MiNi0n|]

If you're lucky, it could be as simple as a case sensitive issue. Look here in your named.boot:


primary 0.168.192.IN-ADDR.ARPA db.thoughts.rev

And then these lines from you db.thoughts.rev:

0.168.192.in-addr.arpa. IN NS dream.thoughts.net.

; Addresses
1.0.168.192.in-addr.arpa. IN PTR dream.thoughts.net


These should be respectively:
0.168.192.IN-ADDR.ARPA
1.0.168.192.IN-ADDR.ARPA

Also, are you actually using IPv6? That may obfuscate things for you if you're not, just remove those entries.

Lastly, as both elmore and I stated, h2n is really the way to go. It'll parse your /etc/hosts file and create all your db's automatically. Very simple and quick stuff.

Oh... if the above doesn't work, plese post your nslookup errors, they are *very* informative for troubleshooting.