목차 1. 시작하며 간단한소개 설치...3 1) MySQL 설치...3 2) BIND RPM 설치...3 3) BIND 소스다운로드및설치...3 4) BIND 동작확인...5 5) 설정 스키마생성및테스트도메인입력 na

Size: px

Start display at page:

Download "목차 1. 시작하며 간단한소개 설치...3 1) MySQL 설치...3 2) BIND RPM 설치...3 3) BIND 소스다운로드및설치...3 4) BIND 동작확인...5 5) 설정 스키마생성및테스트도메인입력 na"

미래 양
7 years ago
Views:

1 [365 TIP 18 호 ] BIND MySQL 연동 (DLZ) 작성일자 : 작성자 : slowlygo@net-farm.com ( 주 ) 넷팜 365managed.com

2 목차 1. 시작하며 간단한소개 설치...3 1) MySQL 설치...3 2) BIND RPM 설치...3 3) BIND 소스다운로드및설치...3 4) BIND 동작확인...5 5) 설정 스키마생성및테스트도메인입력 named.conf 설정 질의테스트 마치며...19

3 1. 시작하며 안녕하세요. 벌써 5월의초입입니다. 아직은아침, 저녁은좀쌀쌀하기만, 낮에는따스하고화창해져서어디놀러가고싶어집니다. 이번호에서는 MySQL driver 을이용해서 BIND DLZ(Dynamically Loadable Zones) 을구현해보도록하겠습 니다. 혹시잘못된내용이나문의가있으신경우에는 커뮤니티를 이용하시거나혹은 으로메일주시면감사하겠습니다. 문서에나오는예제들은 CentOS release 5.4 리눅스에서테스트되었습니다. 그럼시작해보도록하겠습니다. -1-

4 2. 간단한소개 아시겠지만보통 BIND 같은경우, 텍스트파일로되어있어실수하기쉽고시작시에 Zone 파일들을구문분석하기때문에시간도오래걸리며변경된내용을적용을위해서는 BIND를 Reload 하거나 Restart 해야합니다. 이를보완하기 (?) 위해나온것이 DLZ(Dynamically Loadable Zones) 이라고하는데, 데이타베이스에존데이타를저장하고이를변경했을시 BIND 의 Reload 나 Restart 없이즉각적용됩니다. 아래이미지는 에서제공하는 Queries Per Second (QPS) 결과입니다. 자세한설명은해당 URL 을참고하시기바랍니다. -2-

5 3. 설치 설정파일을구성하는번거러움을없애기위해 설치는기존 Bind RPM 에덮어쓰는형식으로진행해보도록하겠습니다. 1) MySQL 설치 MySQL 은간단하게 RPM 으로설치하도록하겠습니다. ~]# yum install mysql-server ~]# yum install mysql-devel 2) BIND RPM 설치 src]# yum install caching-nameserver Installing for dependencies: bind bind-libs * caching-nameserver를설치하면 dependencies가걸려 bind 패키지가설치가됩니다. * 설정의번거러움을없애기위해 bind-chroot는설치하지않습니다. 3) BIND 소스다운로드및설치 Bind 최신버전을다운받습니다. - 다운로드 : 참고로해당문서에서는 bind P1 최신버전을다운받았습니다. [root@study src]# wget -3-

6 src]# tar zxvf bind p1.tar.gz src]# cd bind p1 bind p1]# mysql_config Usage: /usr/lib64/mysql/mysql_config [OPTIONS] Options: --cflags [-I/usr/include/mysql -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstackprotector --param=ssp-buffer-size=4 -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv] --include [-I/usr/include/mysql] --libs [-rdynamic -L/usr/lib64/mysql -lmysqlclient -lz -lcrypt -lnsl -lm -L/usr/lib64 -lssl -lcrypto] --libs_r [-rdynamic -L/usr/lib64/mysql -lmysqlclient_r -lz -lpthread -lcrypt -lnsl -lm -lpthread -L/usr/lib64 -lssl -lcrypto] --socket [/var/lib/mysql/mysql.sock] --port [0] --version [5.0.77] --libmysqld-libs [-rdynamic -L/usr/lib64/mysql -lmysqld -lz -lpthread -lcrypt -lnsl -lm -lpthread -lrt -L/usr/lib64 -lssl -lcrypto] bind p1]#./configure --with-dlz-mysql... 중략... checking for Postgres DLZ driver... no checking for MySQL DLZ driver... using mysql from /usr/lib64/mysql and /usr/include/mysql checking for Berkeley DB DLZ driver... no checking for file system DLZ driver... no checking for LDAP DLZ driver... no checking for ODBC DLZ driver... no checking for stub DLZ driver... no checking for DLZ... yes... 중략... bind p1]# make * 여기서간단하게필요한바이너리만복사해넣도록하겠습니다. [root@study bind p1]# mv /usr/sbin/named /usr/sbin/named.ori `/usr/sbin/named' -> `/usr/sbin/named.ori' -4-

7 bind p1]# mv /usr/sbin/named-checkconf /usr/sbin/named-checkconf.ori `/usr/sbin/named-checkconf' -> `/usr/sbin/named-checkconf.ori' bind p1]# mv /usr/sbin/named-checkzone /usr/sbin/named-checkzone.ori `/usr/sbin/named-checkzone' -> `/usr/sbin/named-checkzone.ori' bind p1]# mv bin/named/named /usr/sbin/ `bin/named/named' -> `/usr/sbin/named' bind p1]# mv bin/check/named-checkconf /usr/sbin/ `bin/check/named-checkconf' -> `/usr/sbin/named-checkconf' bind p1]# mv bin/check/named-checkzone /usr/sbin/ `bin/check/named-checkzone' -> `/usr/sbin/named-checkzone' 4) BIND 동작확인 bind p1]# /etc/init.d/named start bind p1]# /etc/init.d/named stop bind p1]# vi /var/log/messages 1 Apr 30 13:06:52 study syslogd 1.4.1: restart. 2 Apr 30 13:06:52 study kernel: klogd 1.4.1, log source = /proc/kmsg started. 3 Apr 30 13:07:03 study named[11700]: starting BIND P1 -u named -c /etc/named.cachingnameserver.conf -t /var/named/chroot 4 Apr 30 13:07:03 study named[11700]: built with '--with-dlz-mysql' 5 Apr 30 13:07:03 study named[11700]: using up to 4096 sockets 6 Apr 30 13:07:03 study named[11700]: loading configuration from '/etc/named.cachingnameserver.conf' 7 Apr 30 13:07:03 study named[11700]: using default UDP/IPv4 port range: [1024, 65535] 8 Apr 30 13:07:03 study named[11700]: using default UDP/IPv6 port range: [1024, 65535] 9 Apr 30 13:07:03 study named[11700]: no IPv6 interfaces found 10 Apr 30 13:07:03 study named[11700]: listening on IPv4 interface lo, #53 11 Apr 30 13:07:03 study named[11700]: generating session key for dynamic DNS 12 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: 127.IN- ADDR.ARPA 13 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: IN- ADDR.ARPA 14 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: IN -5-

8 ADDR.ARPA 15 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: IN-ADDR.ARPA 16 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: IP6.ARPA 17 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: IP6.ARPA 18 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: D.F.IP6.ARPA 19 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: 8.E.F.IP6.ARPA 20 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: 9.E.F.IP6.ARPA 21 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: A.E.F.IP6.ARPA 22 Apr 30 13:07:03 study named[11700]: automatic empty zone: view localhost_resolver: B.E.F.IP6.ARPA 23 Apr 30 13:07:03 study named[11700]: command channel listening on # Apr 30 13:07:03 study named[11700]: the working directory is not writable 25 Apr 30 13:07:03 study named[11700]: zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial Apr 30 13:07:03 study named[11700]: zone in-addr.arpa/IN/localhost_resolver: loaded serial Apr 30 13:07:03 study named[11700]: zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial Apr 30 13:07:03 study named[11700]: zone ip6.arpa/IN/localhost_resolver: loaded serial Apr 30 13:07:03 study named[11700]: zone localdomain/in/localhost_resolver: loaded serial Apr 30 13:07:03 study named[11700]: zone localhost/in/localhost_resolver: loaded serial Apr 30 13:07:03 study named[11700]: running 32 Apr 30 13:08:49 study named[11700]: received control channel command 'stop' 33 Apr 30 13:08:49 study named[11700]: shutting down: flushing changes 34 Apr 30 13:08:49 study named[11700]: stopping command channel on # Apr 30 13:08:49 study named[11700]: no longer listening on #53 36 Apr 30 13:08:49 study named[11700]: exiting -6-

9 5) 설정 기본 caching-nameserver 패키지에서제공해주는것을수정해서사용하도록하겠습니다. 이는단지설정파일을만들고디렉토리구조를생성하는번거러움을덜기위해서입니다. 기본설정파일을보면다음과같습니다. // // named.caching-nameserver.conf // // Provided by Red Hat caching-nameserver package to configure the // ISC BIND named(8) DNS server as a caching only nameserver // (as a localhost DNS resolver only). // // See /usr/share/doc/bind*/sample/ for example named configuration files. // // DO NOT EDIT THIS FILE - use system-config-bind or an editor // to create named.conf - edits to this file will be lost on // caching-nameserver package upgrade. // options { listen-on port 53 { ; listen-on-v6 port 53 { ::1; directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; // Those options should be used carefully because they disable port // randomization // query-source port 53; // query-source-v6 port 53; allow-query { localhost; allow-query-cache { localhost; logging { -7-

10 channel default_debug { file "data/named.run"; severity dynamic; view localhost_resolver { match-clients { localhost; match-destinations { localhost; recursion yes; include "/etc/named.rfc1912.zones"; * 참고로 caching-nameserver 패키지가설치된상태에서는로컬전용이며 in-addr.arpa, the localhost 외에는어떤권한 ( 권위 ) 를가지고있지않습니다. 그냥간단히 in-addr.arpa, the localhost 외에는 caching 전용입니다. 일반적으로메일서버로이용될경우, 설치해서운용하면 DNS 외부질의를줄일수있습니다. 정말캐싱이되는지간단히 tcpdump 를이용해서보면 [root@study ~]# tcpdump port 53 & [2] [root@study ~]# tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes [root@study ~]# nslookup daum.net localhost 00:59: IP xxx.xxx.xxx > c.gtld-servers.net.domain: [1au] A? daum.net. (37) 00:59: IP xxx.xxx.xxx > kns2.kornet.net.domain: PTR? inaddr.arpa. (43) 00:59: IP kns2.kornet.net.domain > xxx.xxx.xxx : /7/8 (343) 00:59: IP xxx.xxx.xxx > kns2.kornet.net.domain: PTR? inaddr.arpa. (43) 00:59: IP kns2.kornet.net.domain > xxx.xxx.xxx : NXDomain 0/1/0 (101) 00:59: IP xxx.xxx.xxx > kns2.kornet.net.domain: PTR? inaddr.arpa. (43) 00:59: IP kns2.kornet.net.domain > xxx.xxx.xxx : /2/0 (110) 00:59: IP c.gtld-servers.net.domain > xxx.xxx.xxx : /5/6 (206) -8-

11 Server: localhost Address: #53 Non-authoritative answer: Address: Address: Address: Address: Address: Address: :59: IP xxx.xxx.xxx > ns5.daum.net.domain: [1au] A? daum.net. (37) 00:59: IP ns5.daum.net.domain > xxx.xxx.xxx : 59798* 6/5/6 A , A[ domain] 00:59: IP xxx.xxx.xxx > kns2.kornet.net.domain: PTR? inaddr.arpa. (46) 00:59: IP kns2.kornet.net.domain > xxx.xxx.xxx : /5/5 (237) 00:59: IP xxx.xxx.xxx > kns2.kornet.net.domain: PTR? inaddr.arpa. (45) 00:59: IP kns2.kornet.net.domain > xxx.xxx.xxx : NXDomain 0/1/0 (105) [root@study ~]# nslookup daum.net localhost Server: localhost Address: #53 Non-authoritative answer: Address: Address:

12 Address: Address: Address: Address: 네. 위에서보듯이 2번째쿼리부터는캐쉬된데이타를사용한다는것은대충알수있습니다. * view에관해간단히말씀드리면 match-clients, match-destinations에따라옵션및같은도메인이라할지라도다른아이피를지정할수있습니다. 여기서 match-clients는아시겠지만, match-destinations은약간혼란스럽습니다. 예제를하나보도록하겠습니다. 우선 listen-on port 53 { ; -> listen-on port 53 { any; 로변경합니다. 서버에는 2개의아이피가세팅되어있습니다. 아이피는 xxx.xxx.xxx 로표시하였습니다. tcp 0 0 xxx.xxx.xxx.56: :* LISTEN 13010/named tcp 0 0 xxx.xxx.xxx.59: :* LISTEN 13010/named tcp : :* LISTEN 13010/named view 를추가로 2 개더생성하였고각 view 마다다른존파일을가지는 test.com 존을설정하였습니다. view localhost_resolver { match-clients { localhost; match-destinations { ; recursion yes; include "/etc/named.rfc1912.zones"; zone "test.com" IN { type master; file "test.zone"; allow-update { none; -10-

13 view test1 { match-clients { localhost; match-destinations { xxx.xxx.xxx.59; recursion yes; include "/etc/named.rfc1912.zones"; zone "test.com" IN { type master; file "test1.zone"; allow-update { none; view test2 { match-clients { localhost; match-destinations { xxx.xxx.xxx.56; recursion yes; include "/etc/named.rfc1912.zones"; zone "test.com" IN { type master; file "test2.zone"; allow-update { none; 각각존파일에는아래와같이설정되어있습니다. test.zone test.com IN A test1.zone test.com IN A test2.zone test.com IN A 자 bind 를재시작후질의를해보면 [root@study named]# nslookup test.com xxx.xxx.xxx.59 Server: xxx.xxx.xxx.59 Address: xxx.xxx.xxx.59#53-11-

14 Name: test.com Address: named]# nslookup test.com xxx.xxx.xxx.56 Server: xxx.xxx.xxx.56 Address: xxx.xxx.xxx.56#53 Name: test.com Address: named]# nslookup test.com Server: Address: #53 Name: test.com Address: 결국 match-clients 는클라이언트아이피에따라제어를하지만, match-destinations 는목적지아이피에따라제어가됩니다. 본론으로돌아가겠습니다. 4. 스키마생성및테스트도메인입력 스키마를꼭이렇게할필요는없지만최대한표준문서에따르도록하겠습니다. create database dns; grant all privileges on dns.* to identified by 'dns'; create table dns_records ( zone text, host text, `type` text, data text, -12-

15 ); ttl int(11), mx_priority, refresh int(11), retry int(11), expire int(11), minimum int(11), serial bigint(20), resp_person text, primary_ns text create table xfr_table ( zone text, `client` text ); alter table dns_records add INDEX host_index (host(20)); alter table dns_records add INDEX zone_index (zone(30)); alter table dns_records add INDEX type_index (type(8)); alter table xfr_table add INDEX zone_client_index (zone(30),client(20)); # 테스트는위해필요한테이타를입력합니다. 간단히아래존파일의내용을입력해보겠습니다. $TTL IN SOA ns.test.com. root.test.com. ( ; Serial ; Refresh ; Retry ; Expire 86400) ; 50 IN NS 50 IN MX IN TXT "v=spf1 ip4: ~all" ns 50 IN A 50 IN A

16 ftp 50 IN A www 50 IN CNAME ftp mail 50 IN A INSERT INTO `dns_records` VALUES ('test.com','@','soa','ns',50,null,28800,14400, ,86400, ,'root','ns.test.com.'), ('test.com','@','ns','ns.test.com.',50,null,null,null,null,null,null,null,null), ('test.com','@','mx','mail.test.com.',50,'10',null,null,null,null,null,null,null), ('test.com','@','txt','v=spf1 ip4: ~all',50,null,null,null,null,null,null,null,null), ('test.com','ns','a',' ',50,null,null,null,null,null,null,null,null), ('test.com','@','a',' ',50,null,null,null,null,null,null,null,null), ('test.com','ftp','a',' ',50,null,null,null,null,null,null,null,null), ('test.com','www','cname','ftp',50,null,null,null,null,null,null,null,null), ('test.com','mail','a',' ',50,null,null,null,null,null,null,null,null); mysql> select * from dns_records; zone host type data ttl mx_priority refresh retry expire minimum serial resp_person primary_ns soa ns 50 NULL root ns.test.com. NS ns.test.com. 50 NULL NULL NULL NULL NULL NULL NULL NULL mx mail.test.com NULL NULL NULL NULL NULL NULL NULL txt v=spf1 ip4: ~all 50 NULL NULL NULL NULL NULL NULL NULL NULL test.com ns A NULL NULL NULL NULL NULL NULL NULL NULL A NULL NULL NULL NULL NULL NULL NULL NULL test.com ftp A NULL NULL NULL NULL NULL NULL NULL NULL test.com www CNAME ftp 50 NULL NULL NULL NULL NULL NULL NULL NULL test.com mail A NULL NULL NULL NULL NULL NULL NULL NULL

17 5. named.conf 설정 그냥 localhost_resolver 에추가하도록하겠습니다. 실제사용시는구분을위해 View 를하나만들어서하시는것이좋겠네요. view localhost_resolver { match-clients { localhost; match-destinations { localhost; recursion yes; include "/etc/named.rfc1912.zones"; dlz "Mysql zone" { database "mysql {host=localhost dbname=dns user=dns pass=dns} {select zone from dns_records where zone = '%zone%'} {select ttl, type, mx_priority, case when lower(type)='txt' then concat('\"', data, '\"') else data end from dns_records where zone = '%zone%' and host = '%record%' and not (type = 'SOA' or type = 'NS')} {select ttl, type, mx_priority, data, resp_person, serial, refresh, retry, expire, minimum from dns_records where zone = '%zone%' and (type = 'SOA' or type='ns')} {select ttl, type, host, mx_priority, data, resp_person, serial, refresh, retry, expire, minimum from dns_records where zone = '%zone%' and not (type = 'SOA' or type = 'NS')} {select zone from xfr_table where zone = '%zone%' and client = '%client%'}"; 위구문에대해간략히설명드리면, 각쿼리는아큐먼트값으로들어가기때문에순서를지켜야합니다. 기본은 findzone() 과 lookup() 쿼리만들어가도작동은합니다. 물론다르게변경해도무방하지만, 하나의 data값으로처리하기때문에출력값이맞게나오도록해야합니다. // dlz driver 사용 dlz "Mysql zone" { // MySQL databases 사용 database "mysql // 접속정보 {host=localhost dbname=dns user=dns pass=dns} -15-

18 // finezone() 쿼리 {select zone from dns_records where zone = '%zone%'} // lookup() 쿼리 {select ttl, type, mx_priority, case when lower(type)='txt' then concat('\"', data, '\"') else data end from dns_records where zone = '%zone%' and host = '%record%' and not (type = 'SOA' or type = 'NS')} // authority 쿼리 {select ttl, type, mx_priority, data, resp_person, serial, refresh, retry, expire, minimum from dns_records where zone = '%zone%' and (type = 'SOA' or type='ns')} // allnodes() 쿼리 {select ttl, type, host, mx_priority, data, resp_person, serial, refresh, retry, expire, minimum from dns_records where zone = '%zone%' and not (type = 'SOA' or type = 'NS')} // allowzonexfr() 쿼리 {select zone from xfr_table where zone = '%zone%' and client = '%client%'} // findzone() 쿼리후존재할경우카운트 {update data_count set count = count + 1 where zone ='%zone%'}"; - 구문에러는없는지 named restart 를통해확인합니다. [root@study ~]# /etc/init.d/named restart named를정지중 : [ OK ] May 3 17:38:33 study named[29888]: received control channel command 'stop' May 3 17:38:33 study named[29888]: shutting down: flushing changes May 3 17:38:33 study named[29888]: stopping command channel on #953 May 3 17:38:33 study named[29888]: no longer listening on #53 May 3 17:38:33 study named[29888]: no longer listening on xxx.xxx.xxx.59#53 May 3 17:38:33 study named[29888]: exiting named를시작중 : [ OK ] [root@study ~]# May 3 17:38:36 study named[29954]: starting BIND P1 -u named -c /etc/named.caching-nameserver.conf May 3 17:38:36 study named[29954]: built with '--with-dlz-mysql' May 3 17:38:36 study named[29954]: using up to 4096 sockets May 3 17:38:36 study named[29954]: loading configuration from '/etc/named.caching-nameserver.conf' May 3 17:38:36 study named[29954]: reading built-in trusted keys from file '/etc/bind.keys' May 3 17:38:36 study named[29954]: using default UDP/IPv4 port range: [1024, 65535] -16-

19 May 3 17:38:36 study named[29954]: using default UDP/IPv6 port range: [1024, 65535] May 3 17:38:36 study named[29954]: no IPv6 interfaces found May 3 17:38:36 study named[29954]: listening on IPv4 interface lo, #53 May 3 17:38:36 study named[29954]: listening on IPv4 interface eth0, xxx.xxx.xxx.59#53 May 3 17:38:36 study named[29954]: generating session key for dynamic DNS May 3 17:38:36 study named[29954]: Loading 'Mysql zone' using driver mysql May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: 127.IN- ADDR.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: IN- ADDR.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: IN- ADDR.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: IN-ADDR.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: IP6.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: IP6.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: D.F.IP6.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: 8.E.F.IP6.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: 9.E.F.IP6.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: A.E.F.IP6.ARPA May 3 17:38:36 study named[29954]: automatic empty zone: view localhost_resolver: B.E.F.IP6.ARPA May 3 17:38:36 study named[29954]: command channel listening on #953 May 3 17:38:36 study named[29954]: the working directory is not writable May 3 17:38:36 study named[29954]: zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42 May 3 17:38:36 study named[29954]: zone in-addr.arpa/IN/localhost_resolver: loaded serial May 3 17:38:36 study named[29954]: zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42 May 3 17:38:36 study named[29954]: zone ip6.arpa/IN/localhost_resolver: loaded serial May 3 17:38:36 study named[29954]: zone localdomain/in/localhost_resolver: loaded serial 42 May 3 17:38:36 study named[29954]: zone localhost/in/localhost_resolver: loaded serial 42 May 3 17:38:36 study named[29954]: running -17-

20 6. 질의테스트 간단히몇가지만테스트해보도록하겠습니다. ~]# nslookup -type=ns test.com localhost Server: localhost Address: #53 test.com nameserver = ns.test.com. [root@study ~]# nslookup -type=mx test.com localhost Server: localhost Address: #53 test.com mail exchanger = 10 mail.test.com. [root@study ~]# nslookup -type=txt test.com localhost Server: localhost Address: #53 test.com text = "v=spf1 ip4: ~all" [root@study ~]# nslookup -type=a test.com localhost Server: localhost Address: #53 Name: test.com Address: [root@study ~]# nslookup -type=a ns.test.com localhost Server: localhost Address: #53 Name: ns.test.com Address:

21 ~]# nslookup -type=cname localhost Server: localhost Address: #53 canonical name = ftp.test.com. # 바로적용되는지확인을위해아이피를 로업데이트해보았습니다. [root@study ~]# echo "update dns_records set data=' ' where zone='test.com' and host='@' and type='a'" mysql -udns -pdns -Ddns [root@study ~]# nslookup -type=a test.com localhost Server: localhost Address: #53 Name: test.com Address: 마치며 이번호는이래저래많이늦어졌습니다. DLZ 같은경우, 알아두시면나름필요하실때유용하게써먹을수있을거라생각합니다. 다음호에서는더좋은내용으로찾아뵙겠습니다. -- 수고많이하셨습니다. -- [ 본문서의수정및재배포를금합니다.] -19-

KISA-GD

KISA-GD KISA-GD-2011-0002 2011.9 1) RD(Recursive Desired) 플래그 : 리커시브네임서버로하여금재귀적 (recursive) 질의 ( 항목 1.3. 참고 ) 요청을표시함. RD 플레그값이 0 이면반복적 (iterative) 질의를요청 2) AA 플래그 : Authoritative Answer 의약자로써, 네임서버가해당응답데이터를자신이보유하고있는지유무를표시