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

Domain Name Service

Get HP Visualize J210XC - Workstation PDF manuals and user guides View all HP Visualize J210XC manuals
Add to My Manuals
Save this manual to your list of manuals

Page 73 highlights

10. Domain Name Service DNS Under IRIX BIND Configuration Files hoResolution with /etc/resolv.conf The only configuration file required by BIND clients is the /etc/resolv.conf file. The resolv.conf file has several functions: • It defines the default domain or the default domain search list. • It specifies the ordering of host resolution services used by gethostbyname and gethostbyaddr. • It lists Internet addresses of name servers. The first two items apply to both client and server stations. The last item is required only by client stations. To set up a station as a client of remote servers, add nameserver entries for the Internet addresses of the name servers to /etc/resolv.conf. For example: nameserver 128.32.130.12 You can specify up to three nameserver entries. On client and server stations, the name in /etc/sys_id should be set to the fully qualified domain name. However, if you choose not to use fully qualified domain names, add a line with the keyword domain and the station's domain to the resolv.conf file. The gethostbyname and gethostbyaddr library routines normally access station information in this order: • NIS • BIND • Local /etc/hosts file Configuring the Primary BIND Server Use this procedure to configure a primary server: 1. Login as root. 2. Move to the named example directory cd /var/named/Examples and copy the template files to the /var/named directory: cp named.boot.master root.cache named.hosts \ named.rev localhost.rev /var/named 3. Move named.boot.master to named.boot. 4. Edit named.boot to something similar to the following: ; ; Boot file for apple.fruit.com, primary for fruit.com ; directory /var/named ;type domain source host/file backup file cache . root.cache primary fruit.com fruit.named.hosts 5. Modify the named.hosts file, here called fruit.named.hosts, to something similar to the following: ; Authoritative data for fruit.com 68

  • 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
68
10. Domain Name Service
DNS Under IRIX
BIND Configuration Files
hoResolution with /etc/resolv.conf
The only configuration file required by BIND clients is the
/etc/resolv.conf
file. The
resolv.conf
file has
several functions:
•
It defines the default domain or the default domain search list.
•
It specifies the ordering of host resolution services used by
gethostbyname
and
gethostbyaddr
.
•
It lists Internet addresses of name servers.
The first two items apply to both client and server stations. The last item is required only by client stations.
To set up a station as a client of remote servers, add
nameserver
entries for the Internet addresses of the
name servers to
/etc/resolv.conf
.
For example:
nameserver 128.32.130.12
You can specify up to three
nameserver
entries. On client and server stations, the name in
/etc/sys_id
should be set to the fully qualified domain name. However, if you choose not to use fully qualified domain
names, add a line with the keyword
domain
and the station±s domain to the
resolv.conf
file.
The
gethostbyname
and
gethostbyaddr
library routines normally access station information in this order:
•
NIS
•
BIND
•
Local
/etc/hosts
file
Configuring the Primary BIND Server
Use this procedure to configure a primary server:
1.
Login as
root
.
2.
Move to the named example directory
cd /var/named/Examples
and copy the template files to the
/var/named
directory:
cp named.boot.master root.cache named.hosts \
named.rev localhost.rev /var/named
3.
Move
named.boot.master
to
named.boot
.
4.
Edit
named.boot
to something similar to the following:
;
; Boot file for apple.fruit.com, primary for fruit.com
;
directory /var/named
;type domain source host/file backup file
cache . root.cache
primary fruit.com fruit.named.hosts
5.
Modify the
named.hosts
file, here called
fruit.named.hosts
, to something similar to the following:
; Authoritative data for fruit.com