> I could not get timydns to answer for two internal networks. My > solution is: > > .private.network::localhost > .1.168.192.in-addr.arpa::localhost > =tworoute.private.network:192.168.1.254 > =localhost.private.network:192.168.1.1 > > .dmz.network::localhost > .2.168.192.in-addr.arpa::localhost > =dmzbox.private.network:192.168.2.1 > > notice that the DMZ has a address in another network but it's > name is in the private.network. This works for me. >
I made the changes similar to what you described above. Basically what I did was to add to the private file as follows: .dmz.dawnsign.com::ns.dawnsign.com .2.168.192.in-addr.arpa::ns.dawnsign.com # mail exchanger @dawnsign.com::mercury.dawnsign.com =mercury.dawnsign.com:216.xxx.xxx.xxx =myrouter.dawnsign.com:192.168.1.254 ns.dawnsign.com was already defined for the .dawnsign.com domain so there wasn't any need to define it within the .dmz.dawnsign.com domain. It seems to have worked. Am I correct in my assumption that when a name resolution request comes in from any machine in the 192.168.2.x network, the request will be checked against the entries defined for the .dmz.dawnsign.com domain and not the .dawnsign.com domain? ~Doug ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&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
