*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello all, I'm trying to build an OpenBSD 3.5 box as a DNS server using djbdns. Can anyone PLEASE tell me how to get djbdns installed? Everywhere I've looked has instructed me to fetch the src/ports tree but from what I can make out (I'm not totally confident with CVS) but from what I can tell I haven't got enough disk space to build the tree. After a few hours of "building" it ends by saying there's isn't enough disk space.
I'm familliar with keeping FreeBSD up to date but am not yet familliar with OpenBSD. As far as I can tell I was getting the CVS correct except for the small issue of diskspace.
I have a 2Gig hard drive (it's only a DNS server) perhaps what I should be doing is rebuilding it with different partition sizes. Can anyone suggest partition sizes respective to my hard drive size that should suit?
Any help would be great. As I've said I'm on shaky ground with OpenBSD so if someone can just help get out of trouble one way or another that would be great. I'd prefer to use djbdns if it still exists and is maintained. But if not, what do we suggest? Surely not BIND?
Distribution: Knoppix to play, Slack current, OpenBSD stables
Posts: 111
Rep:
Glad to see you are trying an OpenBSD / djbdns combo... I tend to think this is a deadly sharp way of doing DNS work myself. I would encourage you to head over to http://cr.yp.to and read the docs on how to go about the install. There are three packages you have to download and install for it to work: ucspi-tcp, daemontools, and finally djbdns. They are all ultra tiny packages, and compile real peppy like even on an old PI, I couldn't image you needing more than 2-3 megs disk space for the whole trio, not to mention no more than that in RAM for operation. Take some time and read through Dan Bernstein's (the author of the packages) excellent step by steps on the process, and you should be up and running. Post here if there are more concerns after following through on this.
using ports doesn't make much sense as this is a very specific and unique daemon system this fellows developed, I think you'll appreciate it once you've gone through once or twice and done it.
but it doesn't seem to be working. Each step seemed to proceed correctly and after changing the resolv.conf of my workstations to nameserver 192.168.1.12 (the IP address of my DNS) they can no longer resolve.
I should mention that since setting this up my DNS' hard drive is either being read from or written to on a regular one second interval - possibly writing errors to a log file?
Are there any other pages I should have followed in addition to the ones I've done?
Distribution: Knoppix to play, Slack current, OpenBSD stables
Posts: 111
Rep:
I think I've got an idea... you have your resolv.conf depending on just your djbdns box, so if your machine doesn't have the mapping, it fails... you need a second line I believe that has the nameserver of your router or of your upstream DNS server from your ISP
nameserver 192.168.1.12
nameserver 192.168.1.1
so it can resolve out to a fallback, and then cache the results for itself. The harddrive writing is probably all going to a file called, I believe /etc/dnscache/log/main/current or something in the log subdirectory there, which, when cat'd, will have a string of errors pertaining directly to the machines inability to resolve beyond itself.
Ok... to save confusion let's pretend I have two computers (I don't).
Computer one is called MyDNS -> IP 192.168.1.12
Computer two is my Gentoo workstation -> IP 192.168.1.2
Now... following your instructions above I changed the resolv.conf of my Gentoo box to
nameserver 192.168.1.12
nameserver 192.168.1.1
And when opening a browser to lookup a hostname it took a while before it fell through to finding it. But it DID find it. I thought that's probably because the Gentoo box failed with 192.168.1.12 and skipped to 192.168.1.1 for the DNS. So I editted resolv.conf on the Gentoo box to:
nameserver 192.168.1.12
and tried a different site and found it couldn't resolve
BUT the interesting thing is... if I then went to the same site as before I could browse to it without a problem.
still with Gentoo resolv.conf:
nameserver 192.168.1.12
firefox -> www.google.com
Instantly resolves to the site and THEN google search WORKED!!
My novice belief is that MyDNS is caching the DNS data but it's failing to lookup? PErhaps my Netcomm 1300NB (192.168.1.1) isn't forwarding the DNS requests?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.