home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cbmvax!bagate!dsinc!cs.widener.edu!eff!sol.ctr.columbia.edu!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!torn!nott!bnrgate!bmerh85!bmerh85!hamish
- From: Hamish.Macdonald@bnr.ca (Hamish Macdonald)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Matthew Dillon's email address
- Message-ID: <1993Jan27.145603.3311@bmerh85.bnr.ca>
- Date: 27 Jan 93 14:56:03 GMT
- References: <9300513.1602@mulga.cs.mu.OZ.AU> <C1Gqtw.945@lysator.liu.se>
- <EMCOOP.93Jan26105709@bcars148.bnr.ca>
- Sender: news@bmerh85.bnr.ca (Usenet News)
- Organization: Bell Northern Research
- Lines: 29
- In-Reply-To: emcoop@bnr.ca's message of Tue, 26 Jan 1993 15:57:09 GMT
-
- >>>>> On Tue, 26 Jan 1993 15:57:09 GMT,
- >>>>> In message <EMCOOP.93Jan26105709@bcars148.bnr.ca>,
- >>>>> emcoop@bnr.ca (hume smith) wrote:
-
- hume> the capitalisation shouldn't matter, i think the problem is the
- hume> domain part of the address. i can't ping
- hume> overload.berkeley.ca.us, but overload.berkeley.edu is fine. IP
- hume> address 128.32.184.58. i can't finger it for some reason...
-
- Domain-style email addresses are not necessarily pingable; i.e. they
- are not necessarily directly connected to the internet.
-
- The DNS system has the concept of a "mail exchange record".
-
- The DNS "database" can contain an entry (mail exchange record) for a
- particular hostname (A) which doesn't have an address record. This
- mail exchange record points to another internet host (B) which will
- accept mail for host A. The idea is that host B knows how to route
- the mail (possibly via UUCP) to host A.
-
- In this particular case, mail to overload.berkeley.ca.us will go to
- either relay1.uu.net or relay2.uu.net, which will then route it to
- overload.berkeley.ca.us.
-
- I used the command:
-
- % nslookup -type=mx overload.berkeley.ca.us
-
- to determine this.
-