Michael, Thanks for your time and patience. I have a bit more inline...
On Wed, Feb 25, 2004 at 07:38:30PM -0600, Michael D Schleif wrote: > First of all, adreamcreation.org is *NOT* delegated to you, no matter > what whois says: > > # dnsqr any adreamcreation.org > 255 adreamcreation.org: > 36 bytes, 1+0+0+0 records, response, authoritative, nxdomain > query: 255 adreamcreation.org > > # dnsqr ns adreamcreation.org > 2 adreamcreation.org: > 36 bytes, 1+0+0+0 records, response, authoritative, nxdomain > query: 2 adreamcreation.org > > Domain 102010.org appears to be setup properly. You must understand the > concept of `nxdomain'. I'll have to get with the registrar on this. This particular registrar doesn't have any method to register a DNS host on their website. > Second, your original examples: <snip> > show the `One (1) name and two (2) addresses' malady: > > / .2.168.192.in-addr.arpa > ns1.102010.org > \ .38.231.216.in-addr.arpa > > / 192.168.2.2 > demian.102010.org > \ 216.231.38.127 > > This is not readily accomplished. I see what you mean now. Lesson learned. If I changed the tinydns-private data to look something like this... .loc.102010.org::ns1.loc.102010.org .1.168.192.in-addr.arpa::ns1.loc.102010.org =gw.loc.102010.org:192.168.1.254 +ns1.loc.102010.org:127.0.0.1 =pictor.loc.102010.org:192.168.1.6 =miru.loc.102010.org:192.168.1.5 =axp.loc.102010.org:192.168.1.4 =siddhartha.loc.102010.org:192.168.1.3 .dmz.102010.org::ns1.dmz.102010.org .2.168.192.in-addr.arpa::ns1.dmz.102010.org =demian.dmz.102010.org:192.168.2.2 +www.102010.org:192.168.2.2 +www.adreamcreation.org:192.168.2.2 Or have I just destroyed things even more? The part I'm still not sure I understand is the DMZ... > > > Do these DMZ hosts have two (2) interfaces? > > > > The DMZ host has a single interface. > > Your DNS host probably has two interfaces. tinydns-private *MUST* > associated with the private interface, and tinydns-public *MUST* be > associated with the public interface. Actually, the DNS host, is a three interface configuration. eth0 => net eth1 => loc eth2 => dmz > Your DMZ host has one (1) interface; therefore, you will have better > success if you limit that interface to one (1) address. I'm not sure I understand you here. The host on the DMZ has a single interface, and a single IP already. > > > If so, what is the domain of your private LAN? > > > > > > =demian.private.network:192.168.2.2 > > > > The contents of my /etc/tinydns-private/env/DOMAINS file is... > > > > 1.168.192.in-addr.arpa > > 102010.org > <snip /> > > This is going to be a major problem. > > First, look closely at the above, and you will see that you are > specifying two (2) private networks: > > 1.168.192.in-addr.arpa > 192.168.2.2 This is true, so in this case, do I need to also specify the 2.168.192.in-addr.arpa domain in the DOMAINS file? It would look like this with the new tinydns-private data file above... 1.168.192.in-addr.arpa loc.102010.org 2.168.192.in-addr.arpa dmz.102010.org -- Thanks, Sak. ----- ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
