Solved

Advanced TCP/IP settings (DNS related)

Posted on 2013-02-05
3
446 Views
Last Modified: 2013-02-28
Hi

I was looking at the Advanced TCP/IP settings for a Windows 2008 Server and had some questions.

We have a multi-forest/multi-domain environment. The application server is based in a forest (one domain) named Production.mydomain.com

We also have other forests named UAT.uatdomain.com and Dev.devdomain.com

The application and its clients are all based in Production.mydomain.com, however test machines from the other domains may occasionally make connections to the server.

Under DNS, there is "Append Primary and connection specific DNS suffixes". What effect does entering domains in here have? I was going to add only production.mydomain.com and also have "DNS Suffix for this connection:" set to the same. Will this have an effect on clients connecting from other forests?

I can surely add them, but I just wanted to be sure of the logic behind this.

Thanks for any assistance
0
Comment
Question by:cpancamo
3 Comments
 
LVL 57

Accepted Solution

by:
Mike Kline earned 500 total points
Comment Utility
It means when your clients look for host names and use the various suffixes.

You look for the machine test

It will use test.domain.com  

test.suffix2.com
test.suffix3.com
etc....

It should not affect clients from other forests.

Thanks

Mike
0
 

Author Comment

by:cpancamo
Comment Utility
Thanks Mike.

So if the server has no need to initiate a connection to a device in another forest, there is no need to have the other forests listed?

How about web browsing? We may need to connect to https://download1.UAT.uatdomain.com for instance to download a package. Since we are specifying the full FQDN in the HTTP string, this shouldn't make a difference, right?

In fact, that setting only affects connections where the FQDN is not included?
0
 
LVL 35

Expert Comment

by:Nick Sui
Comment Utility
Hey Mike - how have you been? Please drop me a line at my email address [ nirmal_sharma @ mvps.org ]

HTTP traffic is again send to DNS Servers you have configured locally PLUS the logic as stated by Mike above.

>>>In fact, that setting only affects connections where the FQDN is not included?
True. DNS Resolver follows a logic in which it checks to see if name supplied for resolution is a flat name or FQDN.

Sys
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now