Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, April 20, 2009 2:06 AM | 2 votes
I have never fully understood the implications of "DNS Suffix for this connection". Can someone explain it to me?
We have 2 DNS zones - the equivalent of fullcompanyname.com.au and company.com.au and our single 2003 domain is called fullcompanyname - we do not have any WINS, and each site has a DC which also has DNS installed.
Most of our internal sites are accessible either with hostname.fullcompanyname.com.au or with just hostname
We use the DNS zone company.com.au mostly for Internet facing services
Our DNS servers have both zones, as the external DNS for company.com.au obviously contains the external IP addresses and our internal DNS for that zone contains the internal IPs.
How should I configure the IP properties in the network connection for our XP workstations and 2003/2008 servers?
Do I leave the "DNS suffix for this connection" to be blank (as currently) and depend upon the machine's knowledge of what domain it's in? Or, should I put fullcompanyname.com.au in here and check the box for "Register this connection's address in DNS" and check the box for "Use this connection's DNS suffix in DNS registration".
Please advise!
All replies (6)
Friday, April 24, 2009 10:34 AM âś…Answered | 1 vote
HI Christian,
Generally most computers no need to support or use more than one name in DNS. Connection specific DNS name is some time useful, for example you can use multiple names to find which network connection to use when client computers connect to multihomed computer.
By default your FQDN must be same as a Active directory domain name where the computer is located.
For more information refer below article.
http://technet.microsoft.com/en-us/library/cc816716.aspx
If you use one domain name internally and all client computers where located in that internal Active directory,no need to use dns suffix.
According to Microsoft best practices not recommended to assign ip address by DHCP server for the servers.
Regards & Thanks
Chinthaka -If you think my thread is helpful, Please vote.
Thursday, April 23, 2009 7:29 AM | 1 vote
Hi Christian,
If that network connection managed by DHCP server,DNS suffix assigned by the DHCP server,If you specify DNS suffix in that filed,DNS suffix assigned by DHCP will be ignore .
Use below MS Support Article.
http://support.microsoft.com/default.aspx/kb/305553
Regards
Chinthaka -If you think my thread is helpful, Please vote.
Friday, April 24, 2009 12:44 AM
Thanks for your reply.
It's not helped, as I know HOW to enter details into the properties box, but I still do not know what best practice should be.
The Microsoft support article 305553 is not very helpful, for example it just states that if you want the address registered, the tick the box to register - it does not explain what should be done in a normal domain.
Let me spell it out in case I was not being clear;
Should I assign a DNS suffix?
Should I assign this through DHCP? What about our servers which do not get their IP address from DHCP?
Or, should I leave it blank because the machine is a member of the domain and assumes a suffix of the local domain?
Thanks
Monday, April 27, 2009 2:51 AM
That's it! Thanks.
Although... I did understand that Microsoft best practice encouraged the use of DHCP for allocating IP configuration to servers. I understood this to be because Microsoft wanted servers' other IP address configuration to be set by DHCP (DNS servers, WINS servers etc) - and I heard that best practice was to set reservations for servers so that they always get the same IP address. I have disregarded this advice and manually set all configuration options for servers. This makes it very hard work when 260 servers in 36 sites have to be reconfigured to add a new DNS server or remove all WINS server configuration!
Monday, April 27, 2009 5:14 AM
That's it! Thanks.
Although... I did understand that Microsoft best practice encouraged the use of DHCP for allocating IP configuration to servers. I understood this to be because Microsoft wanted servers' other IP address configuration to be set by DHCP (DNS servers, WINS servers etc) - and I heard that best practice was to set reservations for servers so that they always get the same IP address. I have disregarded this advice and manually set all configuration options for servers. This makes it very hard work when 260 servers in 36 sites have to be reconfigured to add a new DNS server or remove all WINS server configuration!
You are Welcome :)
Chinthaka | If you think my thread is helpful, Please vote.
Monday, April 27, 2009 5:14 AM
That's it! Thanks.
Although... I did understand that Microsoft best practice encouraged the use of DHCP for allocating IP configuration to servers. I understood this to be because Microsoft wanted servers' other IP address configuration to be set by DHCP (DNS servers, WINS servers etc) - and I heard that best practice was to set reservations for servers so that they always get the same IP address. I have disregarded this advice and manually set all configuration options for servers. This makes it very hard work when 260 servers in 36 sites have to be reconfigured to add a new DNS server or remove all WINS server configuration!
You are Welcome :)
Chinthaka | If you think my thread is helpful, Please vote.