part_one_example_configuration_files/0000755000000000000000000000000011642417464017220 5ustar rootrootpart_one_example_configuration_files/linux01_etc/0000755000000000000000000000000011642355742021353 5ustar rootrootpart_one_example_configuration_files/linux01_etc/nsswitch.conf0000644000000000000000000000073311642355742024067 0ustar rootroot# /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat group: compat shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis part_one_example_configuration_files/linux01_etc/ntp.conf0000644000000000000000000000370411456575636023040 0ustar rootroot# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: server 0.debian.pool.ntp.org iburst server 1.debian.pool.ntp.org iburst server 2.debian.pool.ntp.org iburst server 3.debian.pool.ntp.org iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for # details. The web page # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. #restrict 192.168.123.0 mask 255.255.255.0 notrust # If you want to provide time to your local subnet, change the next line. # (Again, the address is an example only.) #broadcast 192.168.123.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient part_one_example_configuration_files/linux01_etc/resolv.conf0000644000000000000000000000010011642303023023504 0ustar rootrootsearch example.com nameserver 127.0.0.1 nameserver 192.168.2.10 part_one_example_configuration_files/linux01_etc/dhcp/0000755000000000000000000000000011642365073022267 5ustar rootrootpart_one_example_configuration_files/linux01_etc/dhcp/dhcpd.conf.failover0000644000000000000000000000134311642355437026032 0ustar rootroot## dhcpd.conf.failover on linux01 # Current as of Debian 6.0.2.1. # ISC has not yet finished developing failover in dhcpd, so its subject # to future changes. # Run 'man 5 dhcpd.conf' and check the 'DHCP FAILOVER', # 'FAILOVER STARTUP' and 'CONFIGURING FAILOVER' sections # for the most current instructions on how to set it up on future # versions of Debian's dhcpd # "dhcp-failover" is an arbitrary name but it must be consistent # on both primary and secondary servers. failover peer "dhcp-failover" { primary; address linux01.example.com; port 519; peer address linux02.example.com; peer port 520; max-response-delay 60; max-unacked-updates 10; load balance max seconds 3; mclt 3600; split 128; } part_one_example_configuration_files/linux01_etc/dhcp/dhcpd.conf0000644000000000000000000000327011642354371024221 0ustar rootroot#----------------- # Global DHCP parameters # (parameters here apply to all subnets unless supersceded by a subnet # specific parameter of the same type) #----------------- authoritative; log-facility local7; ddns-update-style none; option domain-name "example.com"; option domain-name-servers linux01.example.com, linux02.example.com; option ntp-servers linux01.example.com, linux02.example.com; # Next few lines are needed if Samba is configured as a Netbios Server, # otherwise it is commented out for now. #option netbios-name-servers linux01.example.com, linux02.example.com; #option netbios-node-type 8; #----------------- # Failover parameters #----------------- include "/etc/dhcp/dhcpd.conf.failover"; #----------------- # DHCP scopes #----------------- # We have no use for DHCP in the data centres but dhcpd will complain if it # has no subnet declaration for the default route. We use a dummy subnet # declaration to stop this. As this file (dhcpd.conf) is synced between linux01 # and linux02, dummy both their default routes on both servers. # # DO NOT REMOVE THE NEXT TWO LINES!! YOU HAVE BEEN WARNED. subnet 192.168.1.0 netmask 255.255.255.0 { } subnet 192.168.2.0 netmask 255.255.255.0 { } subnet 192.168.3.0 netmask 255.255.255.0 { option routers 192.168.3.1; option subnet-mask 255.255.255.0; option broadcast-address 255.255.255.255; pool { failover peer "dhcp-failover"; range 192.168.3.20 192.168.3.250; } } subnet 192.168.4.0 netmask 255.255.255.0 { option routers 192.168.4.1; option subnet-mask 255.255.255.0; option broadcast-address 255.255.255.255; pool { failover peer "dhcp-failover"; range 192.168.4.20 192.168.4.250; } } part_one_example_configuration_files/linux01_etc/bind/0002755000000000001520000000000011642660402022222 5ustar rootbindpart_one_example_configuration_files/linux01_etc/bind/db.example.com0000644000000000001520000000160011642302042024725 0ustar rootbind$TTL 86400 ; 1 day $ORIGIN example.com. @ IN SOA linux01.example.com. hostmaster.example.com. ( ; 2011100301 ; Serial number CCYYMMDDRR, where: ; CC = Century, YY = Year, ; MM = Month, DD = Day, ; RR = Release number starting from 01 14400 ; Refresh (4 hours) 7200 ; Retry (2 hours) 604800 ; Expire (1 week) 86400 ; Minimum (1 day) ) @ IN NS linux01.example.com. @ IN NS linux02.example.com. ;------- ; Hosts in the Primary Data Centre - 192.168.1.0/24 ;------- router01 IN A 192.168.1.1 linux01 IN A 192.168.1.10 ;------- ; Hosts in the Secondary Data Centre - 192.168.2.0/24 ;------- router02 IN A 192.168.2.1 linux02 IN A 192.168.2.10 ;------- ; Hosts in the Office Location 1 - 192.168.3.0/24 ;------- router03 IN A 192.168.3.1 ;------- ; Hosts in the Office Location 2 - 192.168.4.0/24 ;------- router03 IN A 192.168.4.1 linux03 IN A 192.168.4.10 part_one_example_configuration_files/linux01_etc/bind/named.conf.local0000644000000000001520000000074411642660401025250 0ustar rootbind// // Do any local configuration here // // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; zone "168.192.in-addr.arpa" { type master; file "/etc/bind/db.168.192.in-addr.arpa"; notify yes; allow-transfer { 192.168.2.10; }; // the linux02 server }; zone "example.com" { type master; file "/etc/bind/db.example.com"; notify yes; allow-transfer { 192.168.2.10; }; // the linux02 server }; part_one_example_configuration_files/linux01_etc/bind/db.168.192.in-addr.arpa0000644000000000001520000000175311642302027025620 0ustar rootbind$TTL 86400 ; 1 day $ORIGIN 168.192.in-addr.arpa. @ IN SOA linux01.example.com. hostmaster.example.com. ( ; 2011100301 ; Serial number CCYYMMDDRR, where: ; CC = Century, YY = Year, ; MM = Month, DD = Day, ; RR = Release number starting from 01 14400 ; Refresh (4 hours) 7200 ; Retry (2 hours) 604800 ; Expire (1 week) 86400 ; Minimum (1 day) ) @ IN NS linux01.example.com. @ IN NS linux02.example.com. ;------- ; 1.168.192.in-addr.arpa. - 192.168.1.0 scope - Primary Data Centre ;------- 1.1 IN PTR router01.example.com. 10.1 IN PTR linux01.example.com. ;------- ; 2.168.192.in-addr.arpa. - 192.168.2.0 scope - Secondary Data Centre ;------- 1.2 IN PTR router02.example.com. 10.2 IN PTR linux02.example.com. ;------- ; 3.168.192.in-addr.arpa. - 192.168.3.0 scope - Office Location 1 ;------- 1.3 IN PTR router03.example.com. ;------- ; 4.168.192.in-addr.arpa. - 192.168.4.0 scope - Office Location 2 ;------- 1.4 IN PTR router04.example.com. 10.4 IN PTR linux03.example.com. part_one_example_configuration_files/linux03_etc/0000755000000000000000000000000011642417421021346 5ustar rootrootpart_one_example_configuration_files/linux03_etc/default/0000755000000000000000000000000011642417522022774 5ustar rootrootpart_one_example_configuration_files/linux03_etc/default/isc-dhcp-relay0000644000000000000000000000067711642417522025535 0ustar rootroot# Defaults for isc-dhcp-relay initscript # sourced by /etc/init.d/isc-dhcp-relay # installed at /etc/default/isc-dhcp-relay by the maintainer scripts # # This is a POSIX shell fragment # # What servers should the DHCP relay forward requests to? SERVERS="192.168.1.10 192.168.2.10" # On what interfaces should the DHCP relay (dhrelay) serve DHCP requests? INTERFACES="" # Additional options that are passed to the DHCP relay daemon? OPTIONS="" part_one_example_configuration_files/linux02_etc/0000755000000000000000000000000011642417306021347 5ustar rootrootpart_one_example_configuration_files/linux02_etc/nsswitch.conf0000644000000000000000000000073311642417306024063 0ustar rootroot# /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat group: compat shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis part_one_example_configuration_files/linux02_etc/ntp.conf0000644000000000000000000000370411642417306023023 0ustar rootroot# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: server 0.debian.pool.ntp.org iburst server 1.debian.pool.ntp.org iburst server 2.debian.pool.ntp.org iburst server 3.debian.pool.ntp.org iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for # details. The web page # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. #restrict 192.168.123.0 mask 255.255.255.0 notrust # If you want to provide time to your local subnet, change the next line. # (Again, the address is an example only.) #broadcast 192.168.123.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient part_one_example_configuration_files/linux02_etc/resolv.conf0000644000000000000000000000010011642417306023517 0ustar rootrootsearch example.com nameserver 127.0.0.1 nameserver 192.168.1.10 part_one_example_configuration_files/linux02_etc/dhcp/0000755000000000000000000000000011642417306022265 5ustar rootrootpart_one_example_configuration_files/linux02_etc/dhcp/dhcpd.conf.failover0000644000000000000000000000130711642417306026025 0ustar rootroot## dhcpd.conf.failover on linux02 # Current as of Debian 6.0.2.1. # ISC has not yet finished developing failover in dhcpd, so its subject # to future changes. # Run 'man 5 dhcpd.conf' and check the 'DHCP FAILOVER', # 'FAILOVER STARTUP' and 'CONFIGURING FAILOVER' sections # for the most current instructions on how to set it up on future # versions of Debian's dhcpd # "dhcp-failover" is an arbitrary name but it must be consistent # on both primary and secondary servers. failover peer "dhcp-failover" { secondary; address linux02.example.com; port 520; peer address linux01.example.com; peer port 519; max-response-delay 60; max-unacked-updates 10; load balance max seconds 3; } part_one_example_configuration_files/linux02_etc/dhcp/dhcpd.conf0000644000000000000000000000327011642417306024220 0ustar rootroot#----------------- # Global DHCP parameters # (parameters here apply to all subnets unless supersceded by a subnet # specific parameter of the same type) #----------------- authoritative; log-facility local7; ddns-update-style none; option domain-name "example.com"; option domain-name-servers linux01.example.com, linux02.example.com; option ntp-servers linux01.example.com, linux02.example.com; # Next few lines are needed if Samba is configured as a Netbios Server, # otherwise it is commented out for now. #option netbios-name-servers linux01.example.com, linux02.example.com; #option netbios-node-type 8; #----------------- # Failover parameters #----------------- include "/etc/dhcp/dhcpd.conf.failover"; #----------------- # DHCP scopes #----------------- # We have no use for DHCP in the data centres but dhcpd will complain if it # has no subnet declaration for the default route. We use a dummy subnet # declaration to stop this. As this file (dhcpd.conf) is synced between linux01 # and linux02, dummy both their default routes on both servers. # # DO NOT REMOVE THE NEXT TWO LINES!! YOU HAVE BEEN WARNED. subnet 192.168.1.0 netmask 255.255.255.0 { } subnet 192.168.2.0 netmask 255.255.255.0 { } subnet 192.168.3.0 netmask 255.255.255.0 { option routers 192.168.3.1; option subnet-mask 255.255.255.0; option broadcast-address 255.255.255.255; pool { failover peer "dhcp-failover"; range 192.168.3.20 192.168.3.250; } } subnet 192.168.4.0 netmask 255.255.255.0 { option routers 192.168.4.1; option subnet-mask 255.255.255.0; option broadcast-address 255.255.255.255; pool { failover peer "dhcp-failover"; range 192.168.4.20 192.168.4.250; } } part_one_example_configuration_files/linux02_etc/bind/0002755000000000000000000000000011642660672022273 5ustar rootrootpart_one_example_configuration_files/linux02_etc/bind/named.conf.local0000644000000000000000000000067611642660672025326 0ustar rootroot// // Do any local configuration here // // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; zone "168.192.in-addr.arpa" { type slave; file "/var/lib/bind/db.168.192.in-addr.arpa"; masters { 192.168.1.10; }; // the linux01 server }; zone "example.com" { type slave; file "/var/lib/bind/db.example.com"; masters { 192.168.1.10; }; // the linux01 server };