DNS & BIND - 동적 업데이트된 DNS 주종 복사
본고가 설정한 정방향 해석의 주종 서비스는 반대로 이치에 맞고 군더더기 없다.
서버에서 영역만 정의하면 됩니다.분석 라이브러리 파일을 제공할 필요가 없다.
master&slave
캐시 서버 구성
vim /etc/named.conf
11 listen-on port 53 { any; };
17 allow-query { any; };
33 dnssec-validation no;
master(172.25.254.11)
vim/etc/named.rfc1912.zones
zone "lalala.com" IN {
type master;
file "lalala.com.zone";
allow-update { none; };
also-notify {172.25.254.10;}; # salve
};
slave(172.25.254.10)
vim/etc/named.rfc1912.zones
zone "lalala.com" IN {
type slave;
masters {172.25.254.11;};
file "slaves/lalala.com.zone";
};
dig -t axfr lalala.com @172.25.254.11
dig -t axfr 254.25.172.in-addr.arpa @172.25.254.11
전체 동기화가 가능한지 확인
[root@desktop ~]# dig -t axfr lalala.com
; <<>> DiG 9.9.4-RedHat-9.9.4-14.el7 <<>> -t axfr lalala.com
;; global options: +cmd
lalala.com. 86400 IN SOA ns1.lalala.com. admin.lalala.com.lalala.com. 20160609 86400 3600 604800 10800
lalala.com. 86400 IN A 172.25.254.100
lalala.com. 86400 IN NS ns1.lalala.com.
lalala.com. 86400 IN NS ns2.lalala.com.
lalala.com. 86400 IN MX 10 mx1.lalala.com.
lalala.com. 86400 IN MX 20 mx2.lalala.com.
*.lalala.com. 86400 IN A 172.25.254.100
ftp.lalala.com. 86400 IN CNAME www.lalala.com.
mx1.lalala.com. 86400 IN A 172.25.254.13
mx2.lalala.com. 86400 IN A 172.25.254.14
ns1.lalala.com. 86400 IN A 172.25.254.11
ns2.lalala.com. 86400 IN A 172.25.254.10
www.lalala.com. 86400 IN A 172.25.254.11
www.lalala.com. 86400 IN A 172.25.254.12
lalala.com. 86400 IN SOA ns1.lalala.com. admin.lalala.com.lalala.com. 20160609 86400 3600 604800 10800
;; Query time: 1 msec
;; SERVER: 172.25.254.11#53(172.25.254.11)
;; WHEN: Sat Jun 10 05:26:06 EDT 2017
;; XFR size: 15 records (messages 1, bytes 345)
분석 로그
1. 전량 전송
master
Jun 10 05:53:45 server named[1859]: client 172.25.254.10#53447 (lalala.com): transfer of 'lalala.com/IN': AXFR started
Jun 10 05:53:45 server named[1859]: client 172.25.254.10#53447 (lalala.com): transfer of 'lalala.com/IN': AXFR ended
slave
Jun 10 05:53:45 desktop systemd: Started Berkeley Internet Name Domain (DNS).
Jun 10 05:53:45 desktop named[3138]: zone lalala.com/IN: Transfer started.
Jun 10 05:53:45 desktop named[3138]: transfer of 'lalala.com/IN' from 172.25.254.11#53: connected using 172.25.254.10#53447
Jun 10 05:53:45 desktop named[3138]: zone lalala.com/IN: transferred serial 2016060903
Jun 10 05:53:45 desktop named[3138]: transfer of 'lalala.com/IN' from 172.25.254.11#53: Transfer completed: 1 messages, 16 records, 363 bytes, 0.001 secs (363000 bytes/sec)
Jun 10 05:53:45 desktop named[3138]: zone lalala.com/IN: sending notifies (serial 2016060903)
2. 증량 전송
master
Jun 10 06:08:56 server named[1859]: client 172.25.254.10#49088 (lalala.com): transfer of 'lalala.com/IN': AXFR-style IXFR started
Jun 10 06:08:56 server named[1859]: client 172.25.254.10#49088 (lalala.com): transfer of 'lalala.com/IN': AXFR-style IXFR ended
slave
Jun 10 06:08:56 desktop named[3138]: client 172.25.254.11#37149: received notify for zone 'lalala.com'
Jun 10 06:08:56 desktop named[3138]: zone lalala.com/IN: Transfer started.
Jun 10 06:08:56 desktop named[3138]: transfer of 'lalala.com/IN' from 172.25.254.11#53: connected using 172.25.254.10#49088
Jun 10 06:08:56 desktop named[3138]: zone lalala.com/IN: transferred serial 2016060904
Jun 10 06:08:56 desktop named[3138]: transfer of 'lalala.com/IN' from 172.25.254.11#53: Transfer completed: 1 messages, 16 records, 363 bytes, 0.003 secs (121000 bytes/sec)
Jun 10 06:08:56 desktop named[3138]: zone lalala.com/IN: sending notifies (serial 2016060904)
이 내용에 흥미가 있습니까?
현재 기사가 여러분의 문제를 해결하지 못하는 경우 AI 엔진은 머신러닝 분석(스마트 모델이 방금 만들어져 부정확한 경우가 있을 수 있음)을 통해 가장 유사한 기사를 추천합니다:
[CS] HTTP/네트워크 기초 Day-37HTTP를 이용해 주고 받는 메시지를 HTTP 메시지라고 부릅니다. 서버가 리소스를 전달하기 위한 API를 구축해놓아야 클라이언트가 이를 활용할 수 있습니다. HTTP 요청에는 메소드라는 것이 존재합니다. HTTP ...
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
CC BY-SA 2.5, CC BY-SA 3.0 및 CC BY-SA 4.0에 따라 라이센스가 부여됩니다.