[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #ZIL-446337]: aliased domain names

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDD #ZIL-446337]: aliased domain names
  • Date: Thu, 13 Nov 2008 12:49:48 -0700
> Hi Mark,
> 
> 
> Here is what we suggest you do:
> 
> 
> Create a virtual interface on sundowner that has a unique IP address
> for foehn.  That way it will have a unique forward/reverse DNS which the
> remote LDM sites will need unless their allow entries are changed.
> 
> The construct (on Linux) will look something like;
> 
> ifconfig eth0:1 128.138.136.<xxx> netmask <xxx> up
> 
> which will need to be propagated after subsequent systems re/boots.
> 
> 
> ..and if this is too much, we can always notify the other LDM's you connect 
> to..to change the name from foehn to sundowner :)
> 
> Cheers,
> 
> Jeff
> Jeff Weber
> Unidata User Support
> http://www.unidata.ucar.edu


Hi Mark, 

I noticed that some characters did not make it into the response:

> The construct (on Linux) will look something like;
> 
> ifconfig eth0:1 128.138.136.<xxx> netmask <xxx> up

Should read:

ifconfig eth0:1 128.138.136.(xxx) netmask (xxx) up

Cheers,

Jeff

Jeff Weber
Unidata User Support
http://www.unidata.ucar.edu

Ticket Details
===================
Ticket ID: ZIL-446337
Department: Support IDD
Priority: Normal
Status: Open