How should tinydns deal with a dmz?
One of our Dachstein-CD firewalls was up for several days, functioning as we expected. mailonerr is configured to use our mail server that sits on the dmz -- and we were getting our periodic notices, until sometime after 2200 last night. tinydns/public is setup and functioning properly. Even while troubleshooting this issue, remote systems could do dnsmx properly. tinydns/private was setup for *only* private.network information, which did *not* apply to the mail server. dnscache appears to be functioning properly; but, shouldn't this resolve the dmz mail server properly for the firewall and everything inside the firewall? dnsmx from the local firewall hangs and does not return to a prompt for many minutes -- never waiting & Ctrl-C . . . One resolution -- is currently working successfully, now -- is to put our tinydns/public data into tinydns/private data. Is this the way it is supposed to work? What do you think? -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
