Thank you Bill for clearing up that mess in my head, if we can mop up here
>I assume if this is the case and I copy the cdb file to a slave machine, I >would need to add another NS record to and a domain name pointing to the IP >of tiny on the slave machine? > > > I don't quite follow this... can you restate it? Just keep in mind that you should have 2 NS records for a domain, the primary and secondary, and make sure there are corresponding A records (they can resolve to the same IP if you don't want to use a second IP). Then point your external cache to this IP for the internal domain. You have almost answered it at the end, what I was getting at was setting up a secondary name server on a second machine for fault tolerance. So if I add a second ns record on the primary sever to my domain this time containing the domain name for the secondary name server (tiny_dns IP on the secondary nameserver, not the ext_dnscache IP) this will complete internal domain name ns record setup. Now, copy (rsync or a suggested method?) the all tiny_dns data and vegadns data to the secondary name server. If the client machines on my network have the 2 name servers ext_dnscache IPs in there network settings, the primary is queried first, if this had been powered off or unable to answer queries for some reason, the client machine the queries the secondary name server, this has the 2 ns records, the first NS record is dead so I then assume it moves to the second NS record which contains the hostname (IP) for the secondary name server resulting in the query being answered? I'm sorry this is long winded but I need to understand each stage of admin and mechanics. You may have a easier way of explaining this for which I would be eternally grateful Again, many thanks Regards Paul Ps, am I mistaken or have I seen you posting on the qmailrocks mailing list at some point? -----Original Message----- From: Bill Shupp [mailto:[EMAIL PROTECTED] Sent: 21 December 2004 18:41 To: [email protected] Subject: Re: [users] Setting up domain & name servers Paul Swainson wrote: >Hi to all list users, > >This is my first time here and I'm quite a newbie to djbdns & vegadns. My >questions are to do with name servers setup when using vegadns, I have built >this server for a school to use in there internal network (dns server will >not be queried from the internet). > >My djbdns setup is tiny is on my eth0 10.0.0.1, ext_dnscache is on 10.0.0.2. >I will set all the PC's on the network to query ext_dnscache 10.0.0.2 to >resolve internal domain names. > >This is working, when I create a new domain you must enter a primary >nameserver which can be a domain name or an IP, as I understand this I would >enter tinydns IP in there (10.0.0.1), is this correct? > > > Actually, NS records should not be an IP. They should be a hostname that resolves to an A record. >Now when I now create the rest of the zone stuff mail.mydomain.tst etc I >must create a NS record here, you can not enter the IP of the NS (tinydns IP >same as the one in the primary names server). > > > I think the error checking is only in one place, that's why you are seeing this. I will look into that. >Should I create a domain name for tinydns IP 10.0.0.1 so I can enter that >domain name into the NS record im mydomain.tst? > > > Yes. >I assume if this is the case and I copy the cdb file to a slave machine, I >would need to add another NS record to and a domain name pointing to the IP >of tiny on the slave machine? > > > I don't quite follow this... can you restate it? Just keep in mind that you should have 2 NS records for a domain, the primary and secondary, and make sure there are corresponding A records (they can resolve to the same IP if you don't want to use a second IP). Then point your external cache to this IP for the internal domain. >As you can see I'm a bit of a novice and any help would be greatly >appreciated. > > Not a problem. It's always good to see open source used in schools. Regards, Bill
