Name resolution for hosts outside AD domain

  • Thread starter Thread starter Clementius
  • Start date Start date
C

Clementius

Hi,
We use active directory and DNS on a Windows server. Our local domain is
corp.OurCompanyName.com. Users also access other hosts that are not part of
the local domain but still on the local network. All desktops point to the
DNS server for name resolution. How can we have our DNS server resolve names
for these other local hosts? We would rather not update desktops' Hosts
files. Thanks for your help. C
 
In
Clementius said:
Hi,
We use active directory and DNS on a Windows server. Our local domain
is corp.OurCompanyName.com. Users also access other hosts that are
not part of the local domain but still on the local network. All
desktops point to the DNS server for name resolution. How can we have
our DNS server resolve names for these other local hosts? We would
rather not update desktops' Hosts files. Thanks for your help. C
Click to expand...

Are these other hosts resolvable in another domain name?
If they are, Windows Server 2003 can resolve that domain by using a
conditional forwarder.

If they aren't you can add host records to your current domain's Forward
Lookup Zone either manually or dynamically. You lose some security by
allowing a non-member to dynamically register in DNS.
 
Thank you Lanwench for your response. These hosts are local to our network
and unknown to the ISP. C

"Lanwench [MVP - Exchange]"
 
Thank you Kevin for your response. The host we need to add is
Exchange.ISPName.com. We are connecting to an Exchange server hosted by our
provider. The address of the Exchange server is not public. We connect to
the Exchange through a dedicated line with the ISP. The ISP requested we
update the Hosts file on each desktop with the Exchange private IP @. I
assume I cannot add Exchange.ISPName.com to the corp.OurCompanyName.com
Forward Lookup Zone. Where else may I add it on the server? Thank you. C
 
In
Clementius said:
Thank you Kevin for your response. The host we need to add is
Exchange.ISPName.com. We are connecting to an Exchange server hosted
by our provider. The address of the Exchange server is not public. We
connect to the Exchange through a dedicated line with the ISP. The
ISP requested we update the Hosts file on each desktop with the
Exchange private IP @. I assume I cannot add Exchange.ISPName.com to
the corp.OurCompanyName.com Forward Lookup Zone. Where else may I add
it on the server? Thank you. C
Click to expand...
So, you access the Exchange server hosted at the ISP by a private IP?
And you access the Exchange server by "exchange.ispname.com"?

Simple, and you can do it in DNS so you don't have to mess with the hosts
file on each workstation. If the hosts file has the name in it now you can
delete that line after you do this.

Add a Forward Lookup zone named with the Fully Qualified Domain Name you
access the Exchange server by. For instance "exchange.ispname.com" in that
zone create one new host, leave the name field blank and give it the IP
address needed to access the Exchange server, Click OK to create the record
anyway when it barks at you saying "(same as parent folder) is not a valid
host name"
 
Ah - gotcha. Just out of curiosity, which hosted exch. co did you go with,
and have you been happy with it? I've looked into this for a couple of small
clients, and most of the hosting companies I looked into didn't seem to care
much about security - didn't force VPN or RCP/HTTPS for all clients - left
it as an option, and allowed insecure connections through their firewalls -
made me nervous.
Thank you Lanwench for your response. These hosts are local to our
network and unknown to the ISP. C

"Lanwench [MVP - Exchange]"
Set up forwarders on your local DNS server that point to your ISP's
DNS servers. See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
Click to expand...
Click to expand...
 
We use XO Communications (www.xo.com). They are OK. We connect to the server
through a T1 to XO. They also provide Internet access for us. They do not
force VPN but traffic to Exchange does not go over public networks. I am not
sure the service is cost effective (compare to hosting Exchange in-house)
unless you enforce strict quotas on mailboxes which brings up other issues
with users. C


"Lanwench [MVP - Exchange]"
Ah - gotcha. Just out of curiosity, which hosted exch. co did you go with,
and have you been happy with it? I've looked into this for a couple of small
clients, and most of the hosting companies I looked into didn't seem to care
much about security - didn't force VPN or RCP/HTTPS for all clients - left
it as an option, and allowed insecure connections through their firewalls -
made me nervous.
Thank you Lanwench for your response. These hosts are local to our
network and unknown to the ISP. C

"Lanwench [MVP - Exchange]"
Set up forwarders on your local DNS server that point to your ISP's
DNS servers. See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Clementius wrote:
Hi,
We use active directory and DNS on a Windows server. Our local
domain is corp.OurCompanyName.com. Users also access other hosts
that are not part of the local domain but still on the local
network. All desktops point to the DNS server for name resolution.
How can we have our DNS server resolve names for these other local
hosts? We would rather not update desktops' Hosts files. Thanks for
your help. C
Click to expand...
Click to expand...
Click to expand...
 
Thanks Kevin. Works well! C

Kevin D. Goodknecht said:
In
So, you access the Exchange server hosted at the ISP by a private IP?
And you access the Exchange server by "exchange.ispname.com"?

Simple, and you can do it in DNS so you don't have to mess with the hosts
file on each workstation. If the hosts file has the name in it now you can
delete that line after you do this.

Add a Forward Lookup zone named with the Fully Qualified Domain Name you
access the Exchange server by. For instance "exchange.ispname.com" in that
zone create one new host, leave the name field blank and give it the IP
address needed to access the Exchange server, Click OK to create the record
anyway when it barks at you saying "(same as parent folder) is not a valid
host name"
Click to expand...
 
Back
Top