Inu Story's Room

윈도우 DNS
Windows 2000 DNS에서는 기존 버전보다 많은 성능향상이 이루어 졌다. 여기서는 그 특징들에 대해 간단히 알아본다. 자세한 정보는 DNS 도움말이나 관련서적을 참고하기 바란다. 참고로 Windows 2000 DNS 도움말은 기존 버전보다 매우 자세히 설명되어 있다.

1. 도메인 컨트롤러 로케이터(Locator) 서비스

액티브 디렉토리(이하 AD)는 DNS를 필요로 한다. 즉, AD에서 도메인 컨트롤러를 찾기 위해 DNS 서비스를 이용한다. 따라서 AD를 설치하려면 DNS 서비스를 같이 설치해야 한다.

2. 액티브 디렉토리와 통합

내결함성(Fault Tolerance), 보안등을 향상시키기 위해 DNS 영역을 AD에 통합할 수 있다. AD에 통합된 DNS 영역은 AD 복제를 통해 모든 도메인 컨트롤러에 복제된다. 복제된 도메인 컨트롤러에서 운영되는 모든 DNS 서버는 주 영역(Primary Zone) 서버로 작동한다.

3. 동적 업데이트 지원

클라이언트 컴퓨터들로 하여금 DNS 서버 내의 자신들의 리소스 레코드를 동적으로 업데이트 할 수 있도록 해준다. 이 기능은 수동으로 영역 정보를 수정해야 하는 작업과 시간을 줄일 수 있다. 기본적으로 Windows 2000 계열 컴퓨터만 지원되지만, DHCP 서버와의 통합을 통해 비-Windows 2000 계열 컴퓨터도 지원을 할 수 있다.

4. 레코드의 에이징(Aging) 및 청소(Scavenging) 지원

이 기능은 DNS 내의 무효한(사용되지 않는) 레코드가 남아 있는 것을 방지한다. 기본적으로 활성화되어 있지 않다.

5. AD 통합 영역에서 보안된 동적 업데이트(Secure Dynamic Update) 지원

영역을 AD에 통합하게 되면 오직 권한이 있는 클라이언트만이 동적 업데이트를 할 수 있도록 설정할 수 있다.

6. 향상된 관리상의 편이

향상된 GUI(Graphic User Interface)의 DNS 콘솔과 관리에 도움이 되는 여러가지 마법사 기능을 제공한다.

7. 명령 프롬프트상에서의 관리

DNS 콘솔에서 할 수 있는 작업들을 Dnscmd.exe 라는 툴을 이용해서 모두 할 수 있다. (Windows 2000 설치 CD의 \Support\Tools 폴더에서 Windows 2000 Support Tools를 설치해야 한다.)

8. 향상된 이름 해석

Windows 2000 Resolver는 기본적으로 이름해석을 위해 NetBIOS 보다 우선적으로 DNS를 이용한다. 즉, 기존의 Windows NT 4.0에서는 이름해석을 위해 NetBIOS를 기반으로 하지만 Windows 2000에서는 DNS를 기반으로 한다.

9. 향상된 캐싱 및 부정적(Negative) 캐싱

Ipconfig 명령을 통해 Resolver 캐시 내용을 보거나 지울 수 있다. 또한, 존재하지 않는 이름이나 레코드에 대한 정보를 저장하는 부정적(Negative) 캐싱을 지원한다. 이 기능은 사용자가 이미 존재하지 않다고 판단한 정보를 요청할 때 Lookup 시간을 줄일 수 있다.

10. 추가적인 클라이언트 향상

캐시는 Hosts 파일의 내용을 미리 로드할 수 있다. 또한, Resolver 서버 리스트는 사용 가능한 DNS 서버에 우선순위를 부여할 수 있도록 동적으로 재배열될 수 있다.

11. 순수한 DNS 환경 지원

만일 네트워크상의 모든 컴퓨터들이 Windows 2000 환경이라면 더 이상 WINS 서버를 운영할 필요가 없다. 비록 DNS, WINS 통합 환경이라해도 DNS에서 WINS Lookup을 설정하였다면 클라이언트에서 WINS 설정을 할 필요가 없다. 즉, WINS Lookup 기능을 통해 클라이언트의 요청을 DNS 서버가 WINS 서버에게 요청을 하게 된다.

12. 다른 DNS 서버와의 상호 호환성

Windows 2000 DNS는 RFC(Request for Comments) 호환이기 때문에 BIND와 같은 다른 DNS 서버와 상호 작동할 수 있다.

13. 다른 네트워크 서비스와의 통합

DHCP(Dynamic Host Configuration Protocol), WINS(Windows Internet Name Service)와 통합 운영이 가능하다.

14. 증분(Incremental) 영역 전송

전체 영역 정보를 전송하는 "전체 영역 전송" 뿐 아니라, 수정된 정보만을 전송하는 "증분 영역 전송" 기능을 지원한다. 이를 통해 영역 전송에 필요한 대역폭과 시간을 줄일 수 있다.

15. 새로운 리소스 레코드 유형 지원

도메인 컨트롤러를 찾기 위해 이용되는 SRV 리소스 레코드, ATMA 리소스 레코드와 같은 새로운 유형의 레코드 유형을 지원한다.

<출처 : Microsoft Technet>

Windows 2000 DNS : http://www.microsoft.com/technet/win2000/win2ksrv/reskit/tcpch06.asp?a=frame

위 사이트는 Windows 2000 DNS의 기술적인 부분에 대해 자세히 설명하고 있다.

 
$ SET DEF DKA0:[0,0]
$ 
$ 
$ 
$ DIR

Directory DKA0:[000,000]

000000.DIR;1        BACKUP.SYS;1        BADBLK.SYS;1        BADLOG.SYS;1       
BITMAP.SYS;1        CONTIN.SYS;1        CORIMG.SYS;1        INDEXF.SYS;1       
INU.DIR;1           SECURITY.SYS;1      SYS0.DIR;1          TCPIP$FTP.DIR;1    
TCPIP$TELNET.DIR;1  VMS$COMMON.DIR;1    VOLSET.SYS;1        

Total of 15 files.
$ CRE/DIR [PATCH]
$ DIR

Directory DKA0:[000,000]

000000.DIR;1        BACKUP.SYS;1        BADBLK.SYS;1        BADLOG.SYS;1       
BITMAP.SYS;1        CONTIN.SYS;1        CORIMG.SYS;1        INDEXF.SYS;1       
INU.DIR;1           PATCH.DIR;1         SECURITY.SYS;1      SYS0.DIR;1         
TCPIP$FTP.DIR;1     TCPIP$TELNET.DIR;1  VMS$COMMON.DIR;1    VOLSET.SYS;1       

Total of 16 files.
$ 
%%%%%%%%%%%  OPCOM  14-APR-2007 10:43:02.85  %%%%%%%%%%%
Message from user AUDIT$SERVER on DPROS1
Security alarm (SECURITY) and security audit (SECURITY) on DPROS1, system id: 10
25
Auditable event:          Network login failure
Event time:               14-APR-2007 10:43:02.85
PID:                      00000214        
Process name:             TCPIP$FTPC00001 
Username:                 TCPIP$FTP       
Remote node id:           3232236137 (0.617)
Remote node fullname:     192.168.2.105
Remote username:          FTP_C0A80269
Status:                   %LOGIN-F-NOSUCHUSER, no such user

$ 
$ 
$ 
$ CD    DIR

Directory DKA0:[000,000]

000000.DIR;1        BACKUP.SYS;1        BADBLK.SYS;1        BADLOG.SYS;1       
BITMAP.SYS;1        CONTIN.SYS;1        CORIMG.SYS;1        INDEXF.SYS;1       
INU.DIR;1           PATCH.DIR;1         SECURITY.SYS;1      SYS0.DIR;1         
TCPIP$FTP.DIR;1     TCPIP$TELNET.DIR;1  VMS$COMMON.DIR;1    VOLSET.SYS;1       

Total of 16 files.
$ WSE   SET DEF DKA0:[PATCH]
$ DIR

Directory DKA0:[PATCH]

DEC-AXPVMS-TCPIP_ECO-V0504-156-4.;2     DEC-AXPVMS-TCPIP_ECO-V0504-156-4.;1

Total of 2 files.
$ DIR/SIZE

Directory DKA0:[PATCH]

DEC-AXPVMS-TCPIP_ECO-V0504-156-4.;2
                       82142
DEC-AXPVMS-TCPIP_ECO-V0504-156-4.;1
                           0

Total of 2 files, 82142 blocks.
$ DEL DEC-AXPVMS-TCPIP_ECO-V0504-156-4.;1
$                            0 
$ DIR

Directory DKA0:[PATCH]

DEC-AXPVMS-TCPIP_ECO-V0504-156-4.;2     

Total of 1 file.
$ I
%DCL-W-ABVERB, ambiguous command verb - supply more characters
 \I\
$ 
$ DIR  /SIZE

Directory DKA0:[PATCH]

DEC-AXPVMS-TCPIP_ECO-V0504-156-4.;2
                       82142

Total of 1 file, 82142 blocks.
$ R DEC-AXPVMS-TCPIP_ECO-V0504-156-4
%DCL-W-ACTIMAGE, error activating image DEC-AXPVMS-TCPIP_ECO-V0504-156-4
-CLI-E-IMAGEFNF, image file not found DKA0:[PATCH]DEC-AXPVMS-TCPIP_ECO-V0504-156
-4.EXE;
$ REN DEC-AXPVMS-TCPIP_ECO-V0504-156-4. DEC-AXPVMS-TCPIP_ECO-V0504-156-4.EXE
$ R DEC-AXPVMS-TCPIP_ECO-V0504-156-4.EXE

		FTSV DCX auto-extractible compressed file for OpenVMS (AXP)
		FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT
		Copyright (c) Digital Equipment Corp. 1993

Options: [output_file_specification [input_file_specification]]

The decompressor  needs to know  the filename to use for the 
decompressed file. If you don't specify any, it will use the
original name  of the  file before it  was  compressed,  and
create  it in  the  current  directory.  If  you  specify  a
directory name, the file will be created in that directory.

Decompress into (file specification):
	Opening and checking compressed file...
Decompressing (press Ctrl-T to watch the evolution)...
	Creating decompressed file...
	Original file specification: TCPIPT54BL15$:[A72.KIT]DEC-AXPVMS-TCPIP_ECO
-V0504-156-4.PCSI;1
	Decompressed file specification: DKA0:[PATCH]DEC-AXPVMS-TCPIP_ECO-V0504-
156-4.PCSI;1
Successful decompression, decompression report follows:
	File Size: 82141.24 Blocks, 41070.62 Kbytes, 42056317 bytes
	Decompression ratio is 1 to 1.77 ( 77.08 % expansion )
	Elapsed CPU time:    0 00:00:16.00
	Elapsed time    :    0 00:00:24.83
	Speed : 351387.59 Blocks/min, 175693.80 Kbytes/min, 2998507.50 bytes/sec
$ 
$ 
$ DIR

Directory DKA0:[PATCH]

DEC-AXPVMS-TCPIP_ECO-V0504-156-4.EXE;1  DEC-AXPVMS-TCPIP_ECO-V0504-156-4.PCSI;1

Total of 2 files.
$ 
$ 
$ 
$ PROD INST *
 
The following product has been selected:
    DEC AXPVMS TCPIP_ECO V5.4-156          Patch (maintenance update)
 
Do you want to continue? [YES] YES
 
Configuration phase starting ...
 
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
 
DEC AXPVMS TCPIP_ECO V5.4-156: Compaq TCP/IP Services for OpenVMS.
 
    (c) Compaq Computer Corporation 2006. All Rights Reserved.
 
    Compaq Computer Corporation
 
    COMPAQ TCP/IP Services for OpenVMS offers several license options.
 
* This product does not have any configuration options.
 
Execution phase starting ...

The following product will be installed to destination:
    DEC AXPVMS TCPIP_ECO V5.4-156          DISK$DPROS_INU:[VMS$COMMON.]
 
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% TCPIP-W-PCSI_INSTALL 
% - BG device exists.
%   To use the version of HP TCP/IP Services for OpenVMS that was just installed
,
%   system must be rebooted.
% 
 Portion done: 100%

The following product has been installed:
    DEC AXPVMS TCPIP_ECO V5.4-156          Patch (maintenance update)
$ PROD SH HIS
----------------------------------- ----------- ----------- --------------------
PRODUCT                             KIT TYPE    OPERATION   DATE AND TIME
----------------------------------- ----------- ----------- --------------------
DEC AXPVMS TCPIP_ECO V5.4-156       Patch       Install     14-APR-2007 10:51:35
CPQ AXPVMS CDSA V2.0-109            Full LP     Install     13-APR-2007 14:51:26
DEC AXPVMS DECNET_OSI V7.3-2        Full LP     Install     13-APR-2007 14:51:26
DEC AXPVMS DWMOTIF V1.3-1           Full LP     Install     13-APR-2007 14:51:26
DEC AXPVMS OPENVMS V7.3-2           Platform    Install     13-APR-2007 14:51:26
DEC AXPVMS TCPIP V5.4-15            Full LP     Install     13-APR-2007 14:51:26
DEC AXPVMS VMS V7.3-2               Oper System Install     13-APR-2007 14:51:26
HP AXPVMS KERBEROS V2.0-6           Full LP     Install     13-APR-2007 14:51:26
----------------------------------- ----------- ----------- --------------------
 
8 items found
$ REBOOT


	SHUTDOWN -- Perform an Orderly System Shutdown
	            on node DPROS1

@SYS$UPDATE:VMSLICENSE.COM

	Remote Printing from VMS to Network Printers via DEC TCP/IP (UCX)
                 
1) lpr/lpd service must be enabled:    @sys$manager:ucx$config.com
	choose menu option 3:   server components
	choose menu option 5:   lpr/lpd	 (should say "enabled", if not
						choose it and configure it)

2) create the queue and the "printcap" entry (lpd uses printer configuration
		file called "printcap" on UNIX machines - UCX makes entries
		in its own version of a printcap file, but you don't go in
		and make the entries by hand as you can in UNIX)

	THIS IS DONE BY USING THE COMMAND:

		$ run sys$system:ucx$lprsetup.exe

	lprsetup will ask for the basic printcap variables entries and
		allow you to define any additional ones.

  3) ucx$lprsetup dialog is as follows:

	
Command  <  add delete view help exit  >:

		(You can view first, if you like, and you can view
			after you think you've added one)

		type:  add
           
Enter printer name to add :   yourprinterquename     (it will allow alias
							names, too)

Enter the FULL name of one of the following printer types:
remote local :
		if the printer is directly connected to your VMS machine,
			then type:  local  (if you are sharing it to the
				world via tcp/ip on the network)
					otherwise

		type:  remote   (it's out there on the network, either as
				as standalone network printer, or connected
			
	to some other mahcine running tcp/ip which
				is already sharing it to the network via lpd)

Enter printer synomym:       you can enter several nicknames for this printer
				one, per line, when you're done with 
				entering synonyms (aliases), then just hit
				Return on a line by itself.  You don't
				need to enter any.



Enter full file specification for spool directory
SPOOLER DIRECTORY 'sd' :  [SYS$SPECIFIC:[UCX_LPD.FOO]] ?

		if you hit RETURN, then it will spool it's output to
		that location listed inside the [ ].  If you want it to
		spool somewhere else, then specify a directory name where
		you want it to spool (it will create this directory for you)


Set LPD Printserver extensions flag 'ps' [] ?
		Hit RETURN (don't give it a value), UNLESS you are actually
			trying to print to a real, live DEC Printserver
			printer out there on the network (there aren't too
			many around here! :-)

Set remote system name 'rm'  []  ?

		IF the printer is a network printer, then type in either
			the full internet domain name or IP number of
			the printer:
				e.g.  oitlw_raw.oit.duke.edu
					or  152.3.202.114

		ELSE IF the printer is a serial or parallel printer
			connected to a machine which is running LPD
			enter the full internet domain name or IP number of
			the system it is connected to:
				e.g.  benzy.ac.duke.edu
					152.3.202.94

			If the printer is connected to YOUR system, then
			give your system's name or IP number.

		NOTE:  the 'rm' parameter stands for:  "remote machine" name



Set remote printer name 'rp'  [] ?

		IF the printer is a network printer, this parameter is a
		bit redundant.  In a few cases, depending on the type of
		printer, this parameter is used in a special way 
		(e.g.  Apple Laserwriter 16/600PS printer lets you set 
		rp=text  or  rp=raw  to tell the printer whether you're
		printing text or "raw" postscript, eliminating the need to
		pass your output through filters first)  In many cases, this
		parameter is ignored, since it's redundant.  If you aren't
		instructed to define it as something special, then just give
		it the printer's internet domain name or IP number again.


		IF the printer is a serial or parallel printer connected to
			another system running LPD, then give the printer
			name as defined in the printcap file on that remote
			system (you can also refer to synomyms or aliases,
			but it's usually best to refer to the first name)

			e.g.   foo    or   jerry_LA50  
					(now don't all rush to print to
						that one!!! :-)

			If the printer is connected to your machine, then
			use the printer que name.


Set printer error log file  'lf'  [SYS$SPECIFIC:[UCX_LPD]FOO.LOG] ?

		This will be the name and location of where the printer
		error log.  If you want to just accept the default name
		and location that it will create automatically for you,
		just hit RETURN.


Next, it will say

Enter the name of the printcap symbol you wish to modify.  Other
valid entry is :
	'q'	to quit (no more changes)
The names of the printcap symbols are:

 sd for the printer spool directory
 lf for the printer error log file
 lp for the name of the local printer
 ps for the LPD PrintServer extensions flag
 rm for the name of the remote host
 rp for the name of the remote printer
 fm for the printer form field
 pa for the /PASSALL flag
 p1-p8 for the /PARAMETER=(p1,...,p8) field


Enter symbol name:


		For many printers, you will not have to define anymore
		parameters, so you can just type   q   now.  In some
		cases (e.g. HP Laserjets,... :-(  you may have to define
		additional printcap parameters.  Basically, look at the
		printcap file on the machine it's connected to, or look at
		a printcap file on some UNIX box that's printing to it already
		(or to someone else running UCX and lpd) and TRY those 
		definitions.  It can be a real trip trying to figure it out!
		Again, you may already be done.  Just type q to quit and try
		it.  If it doesn't work, you may have to then come back and
		edit this printcap definition.


Next you will be shown the information that you've just specified and be
given the chance to change them or accept them as is:

It will say (e.g.)

                    Symbol  type  value
                    ------  ----  -----
Error log file    :  lf     STR   /SYS$SPECIFIC/UCX_LPD/FOO.LOG
Printer Queue     :  lp     STR   FOO
PS extensions flag:  ps     STR
Remote Host       :  rm     STR   benzy.ac.duke.edu
Remote Printer    :  rp     STR   jerry_la50
Spool Directory   :  sd     STR   /SYS$SPECIFIC/UCX_LPD/FOO

Are these the final values for printer FOO ? [y]



If you hit RETURN, you will be saying, "yes" they are correct.  If you hit
n  for no, then you will be given a chance to change them.

Note: the minimum number of printcap parameters were defined in the above
example.    lf, lp, rm, rp, and sd


Next, it will allow you to enter comment lines to this printcap entry
(describing, e.g. where the printer is, etc)

It will say:

Adding comments to printcap file for new printer, type '?' for help.
Do you want to add comments to the printcap file [n] ? :

You don't have to enter any comments.  If you type  y, then it will ask for
a line at a time.  When you are done entering comment lines for this printer
definition, then just hit RETURN on a line by itself.


Next, it will ask about defaulting to print flag pages:


Do you want the queue to default to print flag pages [y] :

		       (type  y  or  n  or hit return for y)
                    If you don't know, type n  (or type y, since it's the
			default?)

Lastly, it will ask if you want this procedure to start the queue on your
	system (remember, it creates a queue on your system that goes out
		over the network via tcp/ip to the remote system and/or
		printer)

type:  y     (sure you want it to start up!!!)
      

It will then give you the following messages:


Creating execution queue: FOO
Updating UCX$LPD_STARTUP.COM
Updating UCX$LPD_SHUTDOWN.COM



        ***********************************************
        * UCX$LPD_STARTUP.COM     UCX$LPD_PRINTCAP    *
        *    and   UCX$LPD_SHUTDOWN.COM               *
        *  have been updated for this printer         *
        *                                             *
        * Set up activity is complete for this printer*
        ***********************************************


Command  < add delete view help exit >:


If you're curious about what the printcap entry you just created looks like,
	then type view, else type add to add another, delete if you changed
	your mind about adding that last printer, or exit if everything's cool.

Congratulations!  You've done the configuration work.  (Unless you had to
	come up with some additional printcap parameter definitions, you
	have to admit that it was rather painless!)


Now, how to print to this remote printer?   You don't use a special print
command, such as lpr.  THERE IS NO LPR COMMAND!!!!

Use the VMS PRINT COMMAND:


PRINT/QUE=remote_printer_name_as_listed_in_your_printcap filename(s)

and the SHOW QUE command will show if it's gone out the door yet.

Enjoy!