HP Visualize J210XC IRIX to HP-UX Migration Guide - Page 76

Configuring the Secondary BIND Server

Page 76 highlights

Domain Name Service ; ; formerly NS.ISC.ORG ; . 3600000 F.ROOT-SERVERS.NET. 3600000 ; ; formerly NS.NIC.DDN.MIL ; . 3600000 G.ROOT-SERVERS.NET. 3600000 ; ; formerly AOS.ARL.ARMY.MIL ; . 3600000 H.ROOT-SERVERS.NET. 3600000 ; ; formerly NIC.NORDU.NET ; . 3600000 I.ROOT-SERVERS.NET. 3600000 ; End of File NS F.ROOT-SERVERS.NET. A 39.13.229.241 NS G.ROOT-SERVERS.NET. A 192.112.36.4 NS H.ROOT-SERVERS.NET. A 128.63.2.53 NS I.ROOT-SERVERS.NET. A 192.36.148.17 9. Turn on the named daemon using the chkconfig named on command and reboot the system. Configuring the Secondary BIND Server Use this procedure to configure a secondary server: 1. Login as root. 2. Move to the named example directory: cd /var/named/Examples Copy the template files, named.boot.slave root.cache localhost.rev, to the /var/named directory. Move named.boot.slave to named.boot. 3. Modify named.boot to look something like the following: more named.boot ; Boot file for orange.fruit.com, secondary for fruit.com ; DIRECTORY /VAR/NAMED ; TYPE DOMAIN SOURCE HOST/FILE BACKUP FILE CACHE . ROOT.CACHE SECONDARY FRUIT.COM 128.70.10.1 FRUITHOSTS.BAK 4. Use the same localhost.rev file you installed on your primary server. 5. Use the same root.cache file you installed on your primary server. 71

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125

Domain Name Service
71
;
; formerly NS.ISC.ORG
;
.
3600000
NS
F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET.
3600000
A
39.13.229.241
;
; formerly NS.NIC.DDN.MIL
;
.
3600000
NS
G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET.
3600000
A
192.112.36.4
;
; formerly AOS.ARL.ARMY.MIL
;
.
3600000
NS
H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET.
3600000
A
128.63.2.53
;
; formerly NIC.NORDU.NET
;
.
3600000
NS
I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET.
3600000
A
192.36.148.17
; End of File
9.
Turn on the
named
daemon using the
chkconfig named on
command and reboot the system.
Configuring the Secondary BIND Server
Use this procedure to configure a secondary server:
1.
Login as
root.
2.
Move to the
named
example directory:
cd /var/named/Examples
Copy the template files,
named.boot.slave root.cache localhost.rev,
to the
/var/named
directory.
Move
named.boot.slave
to
named.boot
.
3.
Modify
named.boot
to look something like the following:
more named.boot
; Boot file for orange.fruit.com, secondary for fruit.com
;
DIRECTORY /VAR/NAMED
; TYPE DOMAIN SOURCE HOST/FILE BACKUP FILE
CACHE . ROOT.CACHE
SECONDARY FRUIT.COM 128.70.10.1 FRUITHOSTS.BAK
4.
Use the same
localhost.rev
file you installed on your primary server.
5.
Use the same
root.cache
file you installed on your primary server.