Re: Invalid Namespace
- From: "TJ" <noreply@xxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Feb 2008 08:59:51 -0000
Jorge thank you for your response. I have sorted this. The problem was
that the DHCP on Linux was configured to use Linux as the main DNS server.
I changed this to the Windows and we could not access our external website
internally. I have now added an (A) record on the Windows DNS for www to
point to our website. No one is screaming as of yet so I think it is
solved.
Thanks again
TJ
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:AC57D21A-EF6C-43BC-A330-82BF141D28BC@xxxxxxxxxxxxxxxx
Hi
The clients should use their INTERNAL DNS server, then you should
configure your Internal DNS server to handle the external requests. As you
said " the clients should initially send any (internal) DNS requests to
the Windows Server and if this cannot resolve the request is forwarded to
the Linux box for external ", but for this to happen you need to configure
the Windows DNS to forward all other requests to a valid DNS server that
knows the answer for non-internal domain requests.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
.
- Follow-Ups:
- Re: Invalid Namespace
- From: Jorge Silva
- Re: Invalid Namespace
- References:
- Invalid Namespace
- From: TJ
- Re: Invalid Namespace
- From: Jorge Silva
- Invalid Namespace
- Prev by Date: Re: An active directory Domain Controller for the domain could not be contacted in windows vista Business
- Next by Date: lock out a ad account when it is not in use
- Previous by thread: Re: Invalid Namespace
- Next by thread: Re: Invalid Namespace
- Index(es):
Relevant Pages
|
Loading
