Re: [cobalt-users] problems with Qube3 (was Macintosh, AppleShare IP Users)

[Malcolm McLeary <mmcleary@xxxxxxx>]

Hi Gary,

on 6/4/01 8:58 AM, Gary Melendez at gmelendez@xxxxxxxxxxxxxxxx wrote:

>> No, just on the Qube3, add the IP to the /etc/hosts file. It's the Qube 3
>> sendmail program that is looking for the IP->hostname resolution
> 
> Hmmm ..... Wouldn't, then, this be an issue with using DHCP to assign the IP
> addresses to clients? I mean if I list static IPs for all the client
> machines on the Qube's hosts file, and they get different IP addresses, I
> would be back in the same boat. No?

Not really.  The names used for reverse lookup can be "generic".  If they
are DHCP clients then you really don't care what they are actually called
because you won't be doing a forward lookup on them ... they are clients.

You would assign static addresses to servers, and they need forward lookups.

The issue here is that sendmail wants to do a reverse lookup as a means of
"authentication" or "validation" ... you really don't care what name it
comes back with ... something consistent with the IP address is the norm.

In the case of the Gateway Microserver, the DNS is fully populated with
reverse entries for the 192.16.100.x address space.  This sendmail reverse
lookup issue not a problem.  It is a problem if you need to deploy a Gateway
Qube into an existing IP address range ... this is probably why Cobalt don't
pre-populate.  Having said that, Gateway were targeting customers who have
no infrastructure so the Microserver defines the IP setup.

Cheers,  Malcolm

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

                       Information Alchemy Pty Ltd
                             ACN 089 239 305
                           Canberra, Australia

Malcolm McLeary                                Mobile:     0412 636 086
Managing Director                              Email:  mmcleary@xxxxxxx

     This message was sent using Outlook Express 5.0 for Macintosh.