Paul Swainson wrote:
Actually, NS records should not be an IP. They should be a hostname that resolves to an A record.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?
I think the error checking is only in one place, that's why you are seeing this. I will look into that.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).
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
