* Sak <[EMAIL PROTECTED]> [2004:02:24:23:48:22-0800] scribed: > Hey everyone, > > I'm having a little trouble with accessing virtual hosts in my DMZ. > I've setup tinydns and it handles the primary DNS stuff (requests for > 102010.org) just fine. But when I try to access the other domain > either inside, or outside the network, I get a "...could not be > found." response. > > In my tinydns-private file, I've got the following for the DMZ, and > the sites that I'm hosting... > > .2.168.192.in-addr.arpa::ns1.102010.org > =demian.102010.org:192.168.2.2 > +www.102010.org:192.168.2.2 > +www.adreamcreation.org:192.168.2.2 > > My tinydns-public file looks like this... > > .102010.org::ns1.102010.org > .38.231.216.in-addr.arpa::ns1.102010.org > > @102010.org::demian.102010.org > =gw.102010.org:216.231.38.127 > +ns1.102010.org:216.231.38.127 > +ns2.102010.org:216.231.38.127 > > =demian.102010.org:216.231.38.127 > +www.102010.org:216.231.38.127 > +www.adreamcreation.org:216.231.38.127 <snip />
What does dnscache tell you? tail -f /var/log/dnscache/current | tai64nlocal One (1) name and two (2) addresses -- that is probably not what you want. Do these DMZ hosts have two (2) interfaces? If so, what is the domain of your private LAN? =demian.private.network:192.168.2.2 If not, then ditch the /etc/tinydns-private/root/data stuff, and access your DMZ hosts the same way I would: ssh -X demian.102010.org hth -- Best Regards, mds mds resource 877.596.8237 - 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 . . . --
signature.asc
Description: Digital signature
