On Wed, 21 Feb 2001, Ignatios Souvatzis wrote:

> On Wed, Feb 21, 2001 at 08:59:12AM -0800, Jeremy C. Reed wrote:
> > On Tue, 20 Feb 2001, Joseph Sarkes wrote:
> > 
> > > Over the last 6 months or so I have been having more and
> > > more email bounce with configuration complaints about a
> > > non resolvable domain name. My system is set up with an
> > > internal fake domain name on the 10. network address and
> > > thinks of itself that way. Since I have a dialup internet
> > > address, I do not have a static name to use. 
> > 
> > Another idea is to really use a real hostname that resolves. You may want
> > to use a dynamic DNS service; I have used dyndns.org successfully.
> 
> This doesn't work for the intended purpose; the reverse lookup will still
> give you your ISPs dynamic port name (like: line04711x.kdt.de, in my case).

Which will probably be a valid host name and resolve to an IP. So the
email shouldn't "bounce with configuration complaints about a
non resolvable domain name."

His email didn't indicate that the problem was having an hostname that
resolved to an IP that resolved to a different hostname (like the paranoid
tcp_wrapper check). Of course, he didn't provide an example of the exact
error message either.

If using a valid hostname (via a dynamic DNS) and valid IP (as assigned
by his ISP) which resolves to some hostname, it seems like everything
should be okay. (At least, that has worked for me on a couple systems for
over a year.)

   Jeremy C. Reed
   http://www.reedmedia.net/