LocalDomainPrefix has nothing to do with LocalIP or any IP for that matter. It is related to the domain. It is used in conjuction with DomainName and SystemName to create the FQDN of the server. This is:
$SystemName.$LocalDomainPrefix$DomainName So, for example: DomainName = mydomain.com SystemName = mysystem LocalDomainPrefix = mysubdomain. So the FQDN is: mysystem.mysubdomain.mydomain.com Note the trailing period on the LDP -- required. The LDP itself, however, is not required. It can be left blank. In which case, the FQDN is: mysystem.mydomain.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 1:48 PM To: [EMAIL PROTECTED] Subject: [e-smith-devinfo] {$LocalIP} and {$LocalDomainPrefix} Just a thought... If you set up {$LocalIP} as a variable in a template fragment, it pulls 192.168.1.1 (or whatever IP address is assigned to eth0)... Would you use {$LocalDomainPrefix}.0 to get 192.168.1.0 when the template was expanded? If so, why is there no entry for it in /home/e-smith/configuration? Here is an exceprt from the file: LocalDomainPrefix= LocalIP=192.168.1.1 LocalNetmask=255.255.255.0 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
