A little clarification on some points you asked about: /etc/named.conf This file controls the behavior of your bind server. The redhat rpm places it in /etc, but it can reside anywhere. The startup file on a redhat 8 system built with rpms is /etc/init.d/named. This file starts BIND with /etc/named.conf as the config file.
/var/named/db.* This is where you should place zone files for all domains you are authoritative for. For example, when you buy wikked.us, you'll need to make a file named db.wikked (or any name you want) and put it here. This file is where you update IP addresses for www.mystyka.com or add additionsl hosts. After you create your /var/named/db.mystyka zone file (Steve provided a very good example), you'll need to edit /etc/named.conf and tell it that your /var/named/db.mystyka or /var/named/db.mystyka.com.zone file exists, where to find it, and is a "master" zone file. Eliminate the parts in /etc/named.conf that refer to mystyka.com as a secondary zone (I'm assuming your box will be the master and you'll eventually use one of the free dns servers as a slave for mystyka.com) After you edit named.conf, you have to execute: $ sudo /usr/sbin/rndc reload This will tell BIND to check for updates to the zone files in /var/named and changes to the /etc/named.conf configuration file. This is also why you need to update your rndc key file (you want yours to be different than mine so I can't restart your bind). Also, *every* time you edit /var/named/db.mystka, you need to ensure that you increase the serial number in the format 2003033001 (by date with another number at the end). Don't ever forget this (we all have at one time or another, but we hope you'll learn from our mistakes). After every edit you'll want to: $ sudo /usr/sbin/rndc reload $ sudo tail /var/log/messages This restarts bind and checks the log for errors. On Sun, 2003-03-30 at 13:39, Wikked Skye wrote: > Okay, I really appreciate everyone's help here, but I am starting to > feel really dumb...LOL Some of this is starting to make more sense, and > I can find things, but other things are not anywhere to be found... > > I looked for the file db.mystyka, and it does not exist...My db folder > is empty, it said I needed to run updatedb in root mode, so I did this, > but it looks like nothing happened. Is this a file I am supposed to > make myself? or does it generate on its own? I also checked my > named.conf file, so that it now has just the localhost info in it as > master, the reverse for 127.0.0.1 as 0.0.127-inaddr, and master as > mystyka.com > > I do not understand what you mean by using a different key then the one > generated by redhat...what difference does this make? Also, I cannot > seem to find a file anywhere that lists the address info, and has all of > that IN and then says A and gives the information. I completely redid > my system and started over from the beginning to make sure that I would > have everything looking more like everyone has suggested to me. I have > looked through all the documentation I can find on Redhat, and every > time it looks like I am doing things exactly as it shows, nothing still > seems to work. I am starting to get really frustrated. I would prefer > just to use the BIND configuration tool, as I am not too clear on > modifying the documents in edit, and worry about really messing things > up...LOL > > If I have things set the way the documentation I have found says to do > it, why dont I have that A (address) stuff in anywhere, and no > db.mysytka file exists anywhere? ARGH! LOL > > Thanks to all who are sticking with me so far to help me get this > figured out! I really appreciate all the time all of you are spending > with me helping me to get this straightened out. <SMILE> > > Kelly -- Mark Johnson-Barbier
signature.asc
Description: This is a digitally signed message part
