Re: reading MS outlook-file under linux

From: Kevin Nathan (knathan_at_project54.com)
Date: 08/17/03


Date: Sun, 17 Aug 2003 09:24:29 -0600

On Sun, 17 Aug 2003 09:58:19 +0200
Steve <steve@NOMAILwebvivant.com> wrote:

>
> Thanks for the info - I'll go take a look, though I may be back with
> questions!

That's what we're here for -- ask away! :-)

> The last time I tried looking up info on the web I found
> most of the info reasonably easy to understand, but I always tripped
> up over some detail or other. For example, an instruction might be
> "type your fully-qualified domain name here", at which point I would
> realise that the instructions I was following were written by
> someone setting up a campus/corporate system with a permanent
> Internet connection, whereas I'm using POP3 mail from a commercial
> ISP via a dial-up connection via a router with a dynamic IP address.
> So I thought, "what do I put in here"? Anyway, when my server
> arrives, I'll give it a go...

To answer your "example" question, a FQDN (Fully Qualified Domain
Name) is used by some programs regardless of whether you are part of
a larger network, or not. IIRC, SuSE usually defaults the domain to
"local" and then names your machine "localhost", so the domain name
becomes "localhost.local". I may be in error on the ".local" part of
it since I've used "linux.local" ever since I started using Linux.
The "local" part of the name is the Top Level Domain (TLD) and is
*not* a valid TLD so is considered safe to use. Do *not* use a valid
TLD name, such as ".com" or ".net", etc., unless the name is actually
assigned to you.

Usually, when a program asks for a FQDN you can enter "localhost" on a
standalone machine without problems -- some even let you skip it and
it will assume "localhost". If you do something like I do and use a
name like "linux.local", that is your FQDN as long as it's the only
machine. When you add machines to your network, you want to add the
names of the machines to it: "machinename.linux.local".

Another site I used (but haven't been to in quite a while) is:

   www.practicallynetworked.com

It has good info on it (or, at least, "had") and covers the hardware
aspects pretty well.

-- 
Kevin Nathan (Montana, USA)
Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.4.20-4GB-athlon
  9:05am  up 12 days 12:20,  9 users,  load average: 0.04, 0.03, 0.00


Relevant Pages

  • Re: does a home user on dialup need a domain name?
    ... As far as inaccessible domainnames is there a TLD reserved (the way that ... I'm not aware of any specially allocated TLD name string that is ... for my local domain is use 'lan', so the host I'm using to compose ... insists on having well formed FQDN entries in /etc/hosts. ...
    (Debian-User)
  • Re: How to install Virtual Server 2005 on SBS2003
    ... Add the FQDN to your trusted sites or your Intranet sites and it should work. ... When browsing the url bit changing the FQDN to localhost all works fine, using the fqdn gives me the errors.. ... They're not huge email users, so the load on the server is manageable. ...
    (microsoft.public.windows.server.sbs)
  • RE: Virtual SMTP server not relaying to home domain
    ... OK i tried my config stated at the bottom of the first post about localhost. ... First off it doesnt like anything but FQDN for the smarthost, ...
    (microsoft.public.windows.server.setup)
  • Re: I broke slrn
    ... version 1.11.3.rel running at localhost (my ... You should *not* use this FQDN for posting, ... I'm going to give slrn another go. ... Connection closed. ...
    (news.software.readers)
  • Re: mail confusion
    ... if you're using names then there probably are cases that a FQDN ... >> I certainly find having a local network domain name useful. ... On one PC that I have, it didn't associate "localhost" with the ... > insisted that a reserved domain name is needed for local networks; ...
    (Fedora)