biolocal:ServerConfigurationDns
From Wiki CEINGE
| Revision as of 12:10, 20 October 2009 (edit) Angelo (Talk | contribs) m ← Previous diff |
Current revision (12:35, 25 November 2009) (edit) (undo) Mauro (Talk | contribs) |
||
| (2 intermediate revisions not shown.) | |||
| Line 5: | Line 5: | ||
| ceingeauth02 | ceingeauth02 | ||
| ceingewebmail | ceingewebmail | ||
| - | ceingefs | + | ceingefs |
| ceingestg | ceingestg | ||
| ceingeweb | ceingeweb | ||
| ceingevls | ceingevls | ||
| biodb | biodb | ||
| - | ceingenagios | + | ceingenagios |
| - | ceingeservchair | + | ceingeservchair |
| search computing.ceinge.unina.it | search computing.ceinge.unina.it | ||
| Line 23: | Line 23: | ||
| search computing.ceinge.unina.it | search computing.ceinge.unina.it | ||
| - | nameserver 192.168.191.7 (auth01) | + | nameserver 192.168.191.7 #(auth01) |
| - | nameserver 192.168.191.8 (auth02) | + | 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. | 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. | ||
| Line 33: | Line 33: | ||
| ''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.'' | ''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 | + | ''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.'' |
| + | |||
| + | In case of other servers (i.e. with no access to private network or not-diskless) the configuration is: | ||
| + | search ceinge.unina.it | ||
| + | nameserver 127.0.0.1 | ||
| + | nameserver 143.225.151.25 #(auth01) | ||
| + | nameserver 143.225.151.32 #(auth02) | ||
Current revision
Configuration active on centos5srv
ceingemail ceingeauth01 ceingeauth02 ceingewebmail ceingefs ceingestg ceingeweb ceingevls biodb ceingenagios ceingeservchair
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.
In case of other servers (i.e. with no access to private network or not-diskless) the configuration is:
search ceinge.unina.it nameserver 127.0.0.1 nameserver 143.225.151.25 #(auth01) nameserver 143.225.151.32 #(auth02)
