Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / DNS / January 2004

Tip: Looking for answers? Try searching our database.

Anyone *really* understand DNS?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bigus - 23 Jan 2004 11:42 GMT
Hi

I've always fumbled my way through DNS (perhaps more specifically concerning
DNS configuration in the Windows NT family), and got things to work without
fully understanding it! I've been getting annoying messages on one of my
machines at work and so have reluctantly been revisiting the network
configuration.

Rather than detailing the specific problem, it would be useful if someone
could clarify DNS configuration on a general setup scenario. So, here's the
scenario:

Server machine name: WEBSRV1
Windows 2000 domain: EXTERNAL
DNS entry for server: www.mywebserver.ac.uk

It's much easier to show you an image of what I'm referring to, so please
see the Advanced TCP/IP and System Network Identification configs for that
machine here:

http://www.creationfactor.net/image1.jpg

The things I don't understand in this scenario are:

SYSTEM PROPERTIES | IDENTIFICATION

1) What exactly is the primary DNS suffix for this computer? The only DNS
entry is www.mywebserver.ac.uk but if I entered "mywebserver.ac.uk" as the
primary suffix then the Identification panel would show
"websrv1.mywebserver.ac.uk" which doesn't exist.

2) If mywebserver.ac.uk isn't the primary DNS suffix, then shoudl there be
one or is it perfectly normal to leave that field blank?

ADVANCED TCP/IP SETTINGS

1) There are only 2 options, "append primary and connection specific DNS
suffixes" and "append these DNS suffixes", but neither apply in this case as
there are no DNS suffixes for websrv1, so again is it normal to have ought
there?

2) I know the definition of FQDN. It mentions "For resolution of unqualified
names". What is the difference between qualified and unqualified domain
names? Is it something to do with names that are registered on the WWW as a
whole and "internal" DNS names where say "rl.ac.uk" might be the top level
domain available to the world, but "mybastardpc.rl.ac.uk" only works
internally within the organisation?

3) What's "DNS suffix for this connection" all about?

4) The setting "register this connection's addresses in DNS" says about
using the full computer name as defined in system network identification
(which is "websrv1." at present), so presumably if the primary DNS suffix is
left blank this option better be unticked otherwise it'll generate errors?

That's about it.. who know's their stuff then? ;-)

Thanks
Bigus
Marc Reynolds [MSFT] - 23 Jan 2004 13:25 GMT
Hi,

The following link contains the Windows 2000 DNS White Paper. It would be
the best place for you to start. If it doesn't answer all of your questions,
please post again.

http://www.microsoft.com/windows2000/techinfo/howitworks/communications/nameadrm
gmt/w2kdns.asp


Signature

Thanks,
Marc Reynolds
Microsoft Technical Support

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

> Hi
>
[quoted text clipped - 55 lines]
> Thanks
> Bigus
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.