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

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



----- Original Message -----
From: "Malcolm McLeary" <mmcleary@xxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Thursday, April 05, 2001 7:26 PM

[SNIP]

> 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.

OK

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

Understood.

> 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.

Got it.

> 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.

Okay, all understood - although I'm a little puzzled about how the Gateway
Microserver got in here. I haven't actually ever heard of it before. Did I
miss something in another post?

At any rate, thanks a bunch for the help.

Later,
Gary