Yup, I gather it's a Mac issue to do with Rendezvous - sorry to
disturb the list!  Just have to ask the Windows guy to remove the
.local from the end of his domains.

On 2/21/07, Tim Vaughan <talltim at gmail dot com> wrote:
> Sorry, after poking around a bit I've found that it actually seems to
> be working - for example, a:
>
> dig @192.168.123.1 host.fluid.local
>
> actually gives NOERROR and the correct IP (this is on a mac, by the
> way).  However, a:
>
> ping host.fluid.local
>
> gives "Unknown host".  Is this more likely a problem with my Mac?
>
> Tim
>
> On 2/20/07, Chris Buechler <cbuechler at gmail dot com> wrote:
> > On 2/20/07, Tim Vaughan <talltim at gmail dot com> wrote:
> > > Hi,
> > >
> > > I work in an office that has two networks behind a m0n0wall.  One is
> > > run by my colleague who only tolerates Windows servers - the other is
> > > mine.
> > >
> > > I'm using m0n0wall as a DNS forwarder on the LAN interface
> > > (192.168.123.xxx) and has a .tim domain.
> > > The other network is on OPT1 (192.168.2.xxx) and has a Windows SBS
> > > machine running Active Directory, DHCP etc - m0n0wall is just a
> > > gateway.  It has a .fluid.local domain
> > >
> > > I want m0n0wall to forward DNS requests for xxx.fluid.local to the SBS
> > > machine which is at 192.168.2.111.  I've set it up as I thought was
> > > right, in a way which worked when I had a VPN between two m0n0walls
> > > but it's not working.  dig@192.168.2.111 commands work ok on a machine
> > > on my network so I don't understand why the m0n0 doesn't forward the
> > > DNS requests.
> > >
> >
> > I'm guessing the authoritative DNS server for the domain you've setup
> > are across an IPsec connection. If that's the case, the fix is the
> > same as the SNMP over VPN fix (see FAQ).
> >
> > -Chris
> >
>