On 7/19/06, tnelson at fudnet dot info <tnelson at fudnet dot info> wrote:
>
> Are you using the m0n0wall to forward DNS requests to the AD server? In an
> AD environment, the DNS provided on the domain controller must be used for
> most services to work properly.


yes, i used that setup before setting up AD, and since AD requires its own
dns to work properly i installed it too. the clients are now using the local
dns in AD to resolve instead of the dns forwarding offered by monowall, i
encountered some resolving issue regarding my https based webmail client
even though i already made mx, ptr records, i have no problems with regards
to other webservers we're hosting, i can see them just fine, but just like
what andrew said in his reply, AD dns service is a little flaky, my configs
are now working even though i didn't do any more tweaking. i guess it's just
that my AD is behaving strangely.



> > i am using m0n0wall dns forwarding service enabled in my 3 nics
> monowall,
> > one for the lan, one for the dmz and one for the public ip and i have no
> > problems with the setup clients can see the sites if they typed the fqdn
> > at
> > the browser, but when i configured an active directory that requires a
> > local
> > dns and have the windows clients use the local dns instead of the
> monowall
> > dns forwarding service, problem arise, i can't browse the
> > https://mailsample.org, the only way i can access it is by typing the
> > https://ip.add.ress, i can see the other webserver just fine, it's the
> > webmail client i'm concerned. is this a monowall issue? do i need to
> tweak
> > something? where?
> >
> > TIA
> >
>
>
>