OK now the rubber hits the road. I have registered a domain name through eNameCo.com. What is the next step here? Prior to this I was playing around on a protected network just trying to get tinydns working, now I would really like it to work but so far it hasn't.
Are you (James) using tinydns? If so...there seems to be problems. I built and installed it fine, followed the slightly broken instructions on the djbdns website but tinydns just isn't doing its job. For instance, it explains how to install it and then link its /etc/tinydns directory to /service. Fine, did it. Then it calls for running svscan on /service. Fine, did it. Problem arises here...syslog fills with a bunch of: supervise: fatal: unable to start env/run: file does not exist supervise: fatal: unable to start env/run: file does not exist supervise: fatal: unable to start env/run: file does not exist supervise: fatal: unable to start root/run: file does not exist supervise: fatal: unable to start root/run: file does not exist supervise: fatal: unable to start root/run: file does not exist This is inspite of following the directions and building and installing tinydns without problem. I have tried adding: search <my domainname> nameserver 127.0.0.1 nameserver 155.101.152.159 In combination, alone, in different orders, followed by my dhcp-supplied nameservers. Am I missing something? I have tried creating a local dnscache to no avail, tried changing my hostname to no avail (as usual it wrecks connectivity, breaking all X connections, etc), tried adding aliases to my dns cdb. Between the errors above and everything else, my system and tinydns is simply not acting as a dns of any kind, local or no. I've gone over the tinydns/djbdns instructions and I have not varied from them except where they are broken (like if you do as the instructions say and create a symlink from /etc/tinydns to /services you will NOT get a /services/tinydns/root, you will get a /services/root). This bastard just ain't workin. I'd appreciate some more pointers for a novice here. On Wednesday 30 January 2002 02:23 pm, James wrote: > Praedor ont eh postfix side I don't know. But on the dns side what I > do is add the REAL ip number of my box to etc/resolv.conf as one of > the nameservers (keeping the secondary as one I don't control keeps > me alive if dns changes) Then try pinging your box by domain name > from your box. If you can, dns is resolving locally. > > James > > On Wed, 30 Jan 2002 11:33:29 -0700 > > Praedor Tempus <[EMAIL PROTECTED]> wrote: > > Thanks...I have postfix running, I have tinydns built and > > installed, and I downloaded dhcp-dns from freshmeat. I've edited > > resolve.conf to place 127.0.0.1 at the top and I've followed the > > instructions that came from the djbdns site (tinydns) but I see no > > indication at all that tinydns is actually doing anything. > > The instructions: > > > > 1. Use tinydns-conf to configure tinydns on 1.2.3.4: > > "tinydns-conf tinydns dnslog /etc/tinydns 1.2.3.4" (of course, > > substituting my real ip) > > > > 2. Tell svscan about the service: > > "ln -s /etc/tinydns /service" > > > > 3. Now tell tinydns to answer questions about <my domain name> and > > 3.2.1.in-addr.arpa domains and to advertise 1.2.3.5 as the DNS > > server (I tried 127.0.0.1 and then my ip address here without > > result): "cd /service/root" > > "./add-ns <my domain> 1.2.3.5" > > "./add-ns 3.2.1.in-addr.arpa 1.2.3.5" > > "make" > > > > 4. I then told it about my mailserver: > > "cd /service/root" > > "./add-mx <my domain> 1.2.3.4" > > "make" > > > > Now when I svscan runs, it produces a lot of errors on one > > directory in /service: > > > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start root/run: file does not exist > > supervise: fatal: unable to start root/run: file does not exist > > supervise: fatal: unable to start root/run: file does not exist > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start env/run: file does not exist > > supervise: fatal: unable to start root/run: file does not exist > > supervise: fatal: unable to start root/run: file does not exist > > supervise: fatal: unable to start root/run: file does not exist > > supervise: fatal: unable to start root/run: file does not exist... > > > > and queries do not go through my tinydns at all. I see no error > > messages in my logs anywhere. > > > > Any pointers or corrections? To publish my dns so my mailserver > > will really work, do I use 127.0.0.1 or my actual IP address, or do > > I produce an alias/virtual IP (or something)? > > > > On Tuesday 29 January 2002 07:02 pm, J. Craig Woods wrote: > > > Praedor Tempus wrote: > > > > I installed postfix last night and have since switched my smtp > > > > server to local via postfix. > > > > [...] > > > > > I think you are on the right path with postfix. There are a few > > > short cuts out there for mail servers with dhcp assigned ip > > > addresses, i.e. dydns.com but setting up the real thing is the > > > way to go. I have a similar situation, and here is my solution > > > (of course, there are many methods for doing what you want). Run > > > your own name server, and make a MX resource record for your mail > > > server. Change localhost to your FQDN, and enter that in the > > > postfix config file (main.cf). After you get your dhcp pump, > > > giving ip, nameservers, and mask info, you will need to edit > > > "/etc/resolv.conf" and add your dns server as a primary > > > nameserver (127.0.0.1 is the best entry). Also add "search > > > your.domain.com" as the first domain to search. You can keep the > > > > [...] > > > > -------------------------------------------------------
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
