From: Vwaju on
I have a new Slackware 9.1 installation (too many problems installing
12.0 on my old Dell Dimension 4100, but let's not get into that!).

When I configure the network with netconfig, the second step is to
give a domaine name for the machine (of the form "example.org"). Do
you have to supply a REGISTERED domain name here? I have a registered
domaine name (manhattanhandyman.com) but it currently maps to an IP
address at my web host in California. Therefore, it assume I cannot
use it.

My IP address is assigned by ISP, using DHCP. How is this IP address
mapped to the domain name that I assign to my machine? How do I make
sure that the domaine name I supply is unique on the Internet (and
does not collide with someone else's)?

I'm confused...

Best Regards,
Vwaju
New York City
From: Tom Newton on
On 2008-02-02, Vwaju <lou(a)manhattanhandyman.com> wrote:
> I have a new Slackware 9.1 installation (too many problems installing
> 12.0 on my old Dell Dimension 4100, but let's not get into that!).
>
> When I configure the network with netconfig, the second step is to
> give a domaine name for the machine (of the form "example.org"). Do
> you have to supply a REGISTERED domain name here? I have a registered
> domaine name (manhattanhandyman.com) but it currently maps to an IP
> address at my web host in California. Therefore, it assume I cannot
> use it.
>
> My IP address is assigned by ISP, using DHCP. How is this IP address
> mapped to the domain name that I assign to my machine? How do I make
> sure that the domaine name I supply is unique on the Internet (and
> does not collide with someone else's)?
>
> I'm confused...

Just make one up.

Or let example.org stand.

Tom

From: Grant on
On Fri, 1 Feb 2008 17:51:02 -0800 (PST), Vwaju <lou(a)manhattanhandyman.com> wrote:

>I have a new Slackware 9.1 installation (too many problems installing
>12.0 on my old Dell Dimension 4100, but let's not get into that!).
>
>When I configure the network with netconfig, the second step is to
>give a domaine name for the machine (of the form "example.org"). Do
>you have to supply a REGISTERED domain name here?

You can use 'localnet'.

> I have a registered
>domaine name (manhattanhandyman.com) but it currently maps to an IP
>address at my web host in California. Therefore, it assume I cannot
>use it.
>
>My IP address is assigned by ISP, using DHCP. How is this IP address
>mapped to the domain name that I assign to my machine?

It's not mapped to the local name, just to the network interface, the
domain names are not required for connection to the Internet, just the
IP address. Mapping to a domain name is only a convenience.

> How do I make
>sure that the domaine name I supply is unique on the Internet (and
>does not collide with someone else's)?

You don't, the domain name you choose for the local machine is not seen
on the Internet, therefore there is no clash of names.
>
>I'm confused...

Just give it a go.

Grant.
--
http://bugsplatter.mine.nu/
From: William Hunt on
On Sat, 2 Feb 2008, Tom Newton wrote:
> On 2008-02-02, Vwaju <lou(a)manhattanhandyman.com> wrote:
>> I have a new Slackware 9.1 installation (too many problems installing
>> 12.0 on my old Dell Dimension 4100, but let's not get into that!).
>> When I configure the network with netconfig, the second step is to
>> give a domaine name for the machine (of the form "example.org"). Do
>> you have to supply a REGISTERED domain name here?

That really depends on what you want to be able to do.
You can get away with a bogus name for some purposes.
But if you want to run your own SMTP server (instead of
using your ISP's SMTP server, as per your earlier post),
then you really should have a properly registered domain
name mapped to your ISP-assigned ip#.


>> I have a registered
>> domaine name (manhattanhandyman.com) but it currently maps to an IP
>> address at my web host in California. Therefore, it assume I cannot
>> use it.

Right. But note, depending on your registrar, you might be able
to create a 'third-level' name (ex: foo.manhattanhandyman.com).
Some registrars (ex: joker.com) allow you to do this at no extra
charge. Some registrars may not be so reasonable.


>> My IP address is assigned by ISP, using DHCP.

That's too bad. Ask your ISP
(a) how much for static ip# ?
(b) how much for reverse DNS service for that static ip# ?
If the answers are unsatisfactory, investigate switching ISP.


>> How is this IP address
>> mapped to the domain name that I assign to my machine?

That's called 'reverse DNS', a DNS 'PTR record' and that is
controlled by your ISP, who owns the ip# netblock. Some ISPs will
provide (at no add'l cost) reverse DNS to map their ip# to your
domain name, just as your registrar maps your domain name to your
ISP-assigned ip#. This is easy if you have a static ip# but not
so easy if you have a dynamic ip# supplied by DHCP (since the ip#
may change from time to time, at the whim of the ISP ...)


>> How do I make
>> sure that the domaine name I supply is unique on the Internet (and
>> does not collide with someone else's)?

If you -don't- want to run your own SMTP (or HTTP, rsync, ssh, etc)
then you might use a made-up domain in the '.lan' tld, (ex: foo.lan).
Since .lan is a bogus TLD, it is guaranteed to not be in use on
the net. But if you want your machine to be able to be found by
it's domain name, (which is what domain names are for), then you
need a real domain name.



>>
>> I'm confused...

it can be confusing at first :*)

google a bit for 'free dns' and you'll probably learn something.

HTH.



On Sat, 2 Feb 2008, Tom Newton wrote:
>
> Just make one up.
>
> Or let example.org stand.
> Tom

NO NO NO !!!
--> !! BAD ADVICE !! <--

example.org is a legitimate registered and active domain.

((sheesh!)

--
William Hunt, Portland Oregon USA
From: Grant on
On Sat, 2 Feb 2008 01:53:45 +0000 (UTC), Tom Newton <tom(a)server.invalid> wrote:

>Just make one up.
>
>Or let example.org stand.

~$ host example.org
example.org has address 208.77.188.166

Yeah, right...

Grant.
--
http://bugsplatter.mine.nu/