On Sat, Aug 26, 2006 at 10:29:24AM -0400, suse@rio.vg wrote:
John Andersen wrote:
On Saturday 26 August 2006 06:04, suse@rio.vg wrote:
However, you shouldn't be adding ip addresses to the loopback, unless absolutely necessary. Add it to eth0 instead. Just `ifconfig eth0:1 192.168.2.231`.
Why shouldn't you add ip addresses to loopback?
What would be the point? Nothing else on that network could access it. loopback is specifically for the local machine only, there's no reason to have multiple ip addresses for it, unless you're doing something very strange.
Running tinydns on a loopback address for an internal domain is not strange at all. Then you can run dnscache on eth interface and point it to tinydns on loopback for that internal domain. This allows to use the same host for multiple internal domains. For example, you have dev, QA, and prod environments. All use the same domain but should resolve to different IP addresses in different environments. Using multiple loopback addresses on the same host you can run tinydns for all your environments on the same host. On top of that, run multiple instances of dnscache bound to different secondary addresses on eth interface. Then point DNS resolver to a diiferent dnscache depending on the environment (dev, qa, prod) and you get a way of testing your application in different environments using the same FQDNs. -Kastus