Internal DNS to resolve Client Resources

[Mike]

I have recently established a Site-Site (B2B) connection
thru my firewall to a client. My users access multiple
resources on their network (Exchange, File Server, Web
Servers). I have appropriate IP address and Host names but
I'm not sure what sort of record to create in my DNS. When
I try to create a few different records that I think may
work but it wants to use my domains name after the record
I create. For Example: The record I am trying to create is
called "RECORD" which is a file server on their network
but when I resolve it, it comes back with RECORD.XYZ.COM
(XYZ being my domain name).

How can I create a record with the IP address I need and
so that it does not add my parent domain name after the
record?

Is it possible?

Thanks
Mike

 

[Kevin D. Goodknecht [MVP]]

In

I have recently established a Site-Site (B2B) connection
thru my firewall to a client. My users access multiple
resources on their network (Exchange, File Server, Web
Servers). I have appropriate IP address and Host names but
I'm not sure what sort of record to create in my DNS. When
I try to create a few different records that I think may
work but it wants to use my domains name after the record
I create. For Example: The record I am trying to create is
called "RECORD" which is a file server on their network
but when I resolve it, it comes back with RECORD.XYZ.COM
(XYZ being my domain name).

That is the way the DNS hierarcy works.

How can I create a record with the IP address I need and
so that it does not add my parent domain name after the
record?

You could use a hosts file, but you would have to add it to every machine.
You should be able to resolve the record using DNS if you have your domain
name in the domain search list.

 

[Tim Rains [MSFT]]

Hi Mike. Thank-you for your post.

The issue is how the name is being entered on the client. You can create a
DNS record called "RECORD" in zone called abc.com. But if someone simply
types "RECORD" as the name that they want to resolve (this is called a
single label name i.e. no dots in the name), a Windows 2000 client will
automatically append its own domain name to the end of this host name and
send that query to DNS. In your case the queried name would be
record.xyz.com. If that name can be resolved, you will end up connecting
to a system that you did not intend to. If the name can't be resolved the
client will obviously fail to connect to any system.

One way to customize this behavior is to use a DNS search suffix.
Essentially you tell the client what DNS suffixes to append to single label
names when they are entered. You are overriding the client's default
behavior by doing this, so you need to add all the suffixes to the list
that are necessary in both environments. This article should help:

275553 How to Configure a Domain Suffix Search List on the Domain Name
System
http://support.microsoft.com/?id=275553

I hope that helps.

Tim Rains
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.