biolocal:ServerConfigurationDns
From Wiki CEINGE
| Revision as of 11:52, 20 October 2009 (edit) Angelo (Talk | contribs) m ← Previous diff |
Revision as of 12:08, 20 October 2009 (edit) (undo) Angelo (Talk | contribs) m Next diff → |
||
| Line 1: | Line 1: | ||
| - | ''Configuration | + | ''Configuration active on centos5srv'' |
| ceingemail | ceingemail | ||
| + | ceingeauth01 | ||
| + | ceingeauth02 | ||
| ceingewebmail | ceingewebmail | ||
| - | ceingefs - not yet (resolv.conf is read only) | + | ceingefs - ''not yet (resolv.conf is read only)'' |
| ceingestg | ceingestg | ||
| ceingeweb | ceingeweb | ||
| ceingevls | ceingevls | ||
| biodb | biodb | ||
| - | ceingenagios - not yet (resolv.conf is read only) | + | ceingenagios - ''not yet (resolv.conf is read only)'' |
| - | ceingeservchair - not yet (server has problems on startup) | + | ceingeservchair - ''not yet (server has problems on startup)'' |
| search computing.ceinge.unina.it | search computing.ceinge.unina.it | ||
| Line 19: | Line 21: | ||
| ''Configuration activated on CLST_CENTOS nodes'' | ''Configuration activated on CLST_CENTOS nodes'' | ||
| - | |||
| - | ceingeauth02 | ||
| search computing.ceinge.unina.it | search computing.ceinge.unina.it | ||
| Line 26: | Line 26: | ||
| nameserver 192.168.191.8 (auth02) | nameserver 192.168.191.8 (auth02) | ||
| - | N.B. these configurations are automatically generated by ''' | + | N.B. these configurations are automatically generated by '''dhclient-script''' running on each server, and depends on parameters of '''/etc/dhcpd.conf''' located in '''clustermanager'''. So, any changes must be done by modifying '''/etc/dhcpd.conf''' on clustermanager. |
| + | |||
| + | |||
| + | From Manpage of dhclient-script: | ||
| + | |||
| + | ''The DHCP client network configuration script is invoked from time to time by dhclient. This script is used by the dhcp client to set each interface's initial configuration prior to requesting an address, to test the address once it has been offered, and to set the interface's final configuration once a lease has been acquired. If no lease is acquired, the script is used to test predefined leases, if any, and also called once if no valid lease can be identified.'' | ||
| + | |||
| + | ''This script is not meant to be customized by the end user. If local customizations are needed, they should be possible using the enter and exit hooks provided. These hooks will allow the user to override the default behaviour of the client in creating a /etc/resolv.conf file.'' | ||
Revision as of 12:08, 20 October 2009
Configuration active on centos5srv
ceingemail ceingeauth01 ceingeauth02 ceingewebmail ceingefs - not yet (resolv.conf is read only) ceingestg ceingeweb ceingevls biodb ceingenagios - not yet (resolv.conf is read only) ceingeservchair - not yet (server has problems on startup)
search computing.ceinge.unina.it nameserver 127.0.0.1 nameserver 192.168.191.7 (auth01) nameserver 192.168.191.8 (auth02)
Configuration activated on CLST_CENTOS nodes
search computing.ceinge.unina.it nameserver 192.168.191.7 (auth01) nameserver 192.168.191.8 (auth02)
N.B. these configurations are automatically generated by dhclient-script running on each server, and depends on parameters of /etc/dhcpd.conf located in clustermanager. So, any changes must be done by modifying /etc/dhcpd.conf on clustermanager.
From Manpage of dhclient-script:
The DHCP client network configuration script is invoked from time to time by dhclient. This script is used by the dhcp client to set each interface's initial configuration prior to requesting an address, to test the address once it has been offered, and to set the interface's final configuration once a lease has been acquired. If no lease is acquired, the script is used to test predefined leases, if any, and also called once if no valid lease can be identified.
This script is not meant to be customized by the end user. If local customizations are needed, they should be possible using the enter and exit hooks provided. These hooks will allow the user to override the default behaviour of the client in creating a /etc/resolv.conf file.
