Yes, definitely, if I understand your question. Don't know what you mean by
> I'm trying to figure a way to internalize domain without
> changing domain to an internal name.
Can you explain that? Do you mean you don't want to host your domain's
public DNS? If so, that's just fine, and is normal in small networks.
In an optimal AD setup, you're using your AD-integrated DNS server as the
only DNS server for all clients and servers, and set up forwarders to your
ISP's DNS servers/and/or use root hints to resolve Internet names. Don't put
external DNS server IPs in your server/client IP configs or you'll have
problems.
See
http://support.microsoft.com/default...b;en-us;300202 for more
info.
KJ wrote:
> Can you set up a DNS server to forward lookup to another
> DNS server that is not aware that you are doing so that
> you might be able to be forwarded from their DNS to the
> internet from inside a internal network? Would you be able
> to see objects that are on internal network? Would you be
> able to get to applications without the need for a zone
> transfer as long as the other DNS server is pulling the
> transfers and has a trust incorporated without the need
> for you to do so?
>
> I'm trying to figure a way to internalize domain without
> changing domain to an internal name. Just move all inside
> and point to the main DNS as forwarder and let my DNS grab
> what it needs to see or is this possible?
Similar Threads
