Jeff, Actually it does store TTL and MX priority information, here's what my "domain template" looks like:
Zdomain.tld:ns1-auth.terraworld.net.:root.terraworld.net. &domain.tld::ns1-auth.terraworld.net.:172800 &domain.tld::ns2-auth.terraworld.net.:172800 @domain.tld::mail.domain.tld.:10:172800 +domain.tld:10.0.0.1:172800 +ftp.domain.tld:10.0.0.1:172800 +mail.domain.tld:10.0.0.1:172800 +localhost.domain.tld:127.0.0.1:172800 +www.domain.tld:10.0.0.1:172800 djbdns has the capability to automatically create the cache times (172800 on all these) as well as a default MX weight of 10 if you don't specify it. This page http://cr.yp.to/djbdns/tinydns-data.html which you may have already read, goes through the full specifications of the data file. When I run the dnsloaddata program, it does not send any of the extended information to stdout. For example, the data lines pertaining to my personal domain: Zthewatch.org:ns1-auth.terraworld.net.:root.terraworld.net.:200202012:43200:7200:1209600:172800:172800 &thewatch.org::ns1-auth.terraworld.net.:172800 &thewatch.org::ns2-auth.terraworld.net.:172800 @thewatch.org::mail.thewatch.org.:20:172800 +thewatch.org:64.254.34.12:172800 +boberz.thewatch.org:64.254.49.226:172800 +multia.thewatch.org:64.254.49.225:172800 +ghostie.thewatch.org:12.231.82.42:172800 +localhost.thewatch.org:127.0.0.1:172800 +mail.thewatch.org:64.254.32.52:172800 +www.thewatch.org:64.254.34.12:172800 +cs.thewatch.org:64.254.50.50:172800 +ftp.thewatch.org:64.254.34.12:172800 +virtego.thewatch.org:64.254.63.226:600 and what dnsloaddata presents: Zthewatch.org &thewatch.org &thewatch.org @thewatch.org +thewatch.org +boberz.thewatch.org +multia.thewatch.org +ghostie.thewatch.org +localhost.thewatch.org +mail.thewatch.org +www.thewatch.org +cs.thewatch.org +ftp.thewatch.org +virtego.thewatch.org So, it's either got to be parseing the information, or alternatively (this may be the case) dropping everything after the first delimiter. What I'm curious about is if the dnsloaddata program is properly reading the file such that it /can/ populate the database. If it's not reading the file properly (truncating after delimiters) then it's not possible for the program to populate the database at all. - Nick Bright 888-332-1616 http://home.terraworld.net -----Original Message----- From: Jeff Hedlund [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 21, 2003 10:04 AM To: Nick Bright Subject: Re: [dnsadmin] dnsloaddata program Nick Bright wrote: > If there is a patched version of dnsloaddata.c I would be *highly* interested in > obtaining it, as our DNS system is getting large > enough that I can't make all the entries by hand anymore. I tried writing my own > system in PHP, but I'm a poor database designer and > it didn't work well at all - I abandoned the project. My data file is small enough that I may be able to just re-enter things by hand... otherwise I'd patch it myself, if I had the time. > At least it appears everything it's spewing to standard out is correct information, > though. All your seeing is your data file. It's the same as doing a 'cat /path/to/djbdns/root/data'. (well, it does create the database and tables if not already created, but that's all). [unless you have a different version of dnsloaddata than me] > I didn't see in the stdout output any > cache times or mx weights and such. I hope that it's correctly parseing that > information as well? dnsloaddata isn't parsing anything. And as far as I can tell, dnsadmin does not store information about TTL and mx priority. That's something I'll have to add in as well before I start to use dnsadmin... Jeff -- /\ /\ .. .. .. [EMAIL PROTECTED] / \/ \ a t r i x . . . . . . . (770) 794-7233 s o f t w a r e i n c .. .. .. http://www.matrixsi.com
