Re: Sender header?

[prj@po.cwru.edu (Paul Jarc)]

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Barry Fishman <barry_fishman@acm.org>  on Thu, 24 May 2001
>| My login@fqdn is "barry@ecube.local".
> 
> *snrk*.
> 
> That is not a legal fqdn, or did someone create the "local" TLD when I
> blinked? :)

Creating a TLD is easy.  Getting ICANN's root servers to serve it is
the hard part. :)

>| The closest thing to a local mail address is my pop server address
>| "barry_fishman@att.net".  I connect to the internet using a PPP
>| connection PAP authentication with a variety of addresses.  At the moment
>| I'm at "12.78.17.131", but this varies each call and is probably bogus
>| anyway.  I send mail by direct smtp connection to mailhost.att.net.
> 
> The IP is not bogus.  The fact that AT&T has no A record for it is bogus.

We don't know whether there's an A record with that address, because
we don't know what name to look up to find out; we only know that
there's no PTR record for the name 131.17.78.12.in-addr.arpa.  Please
stop pretending to know about DNS.

> That is probably a real pain when you hit an SSH server that refuses your
> connection because it cannot do a reverse IP lookup.

Maybe his provider gives him some way around that.  Since we don't
know, we can't say that this setup is bogus.

> There should be an A record in att.net's DNS associated with that IP, and
> it should include that name in the DHCP packet it gives you when you make
> your dialup connection.

FAYK, this is already the case.

> Your host should set its name to the name specified in that packet
> for the duration of the session.

I don't agree.  The host should use the hostname provided by DHCP for
dealings with that same network, but not necessarily globally, nor on
other networks the host may be on.


paul