Hi. If this has been posted, sorry, I searched. I've been searching for
days, lol. The matter at hand; i just registered a domain and i would
like to configure my slackware machine to use this domain. Basically I
want a to setup it for the home of the domain, like hosting companies
do. For example; shell providers have single machines solely for shell
account hosting, a domain is assigned to the machine. I'm a newbie when
it comes to networking and would like indepth instructions if possible.
Links to newbie articles would be helpful too. Thank you all for your
time.

nycdiesl@gmail.com wrote:
> Hi. If this has been posted, sorry, I searched. I've been searching for
> days, lol. The matter at hand; i just registered a domain and i would
> like to configure my slackware machine to use this domain. Basically I
> want a to setup it for the home of the domain, like hosting companies
> do. For example; shell providers have single machines solely for shell
> account hosting, a domain is assigned to the machine. I'm a newbie when
> it comes to networking and would like indepth instructions if possible.
> Links to newbie articles would be helpful too. Thank you all for your
> time.
>

I'm guessing you'd need to use something like BIND to do some DNS
mapping. Although.. I have a domain name.. which is linked to my ip
address. Seeing as though my IP is dynamic, I have a script to update
the free DynDNS account I have. So when my IP changes, my DynDNS address
is pointing to the new IP address, and my .be domain name points to the
DynDNS address. But of course, maybe working with BIND or something
along the lines of that would be a lot easier (although I'm thinking the
configuration and such will be pretty daunting).

nycdiesl@gmail.com wrote:
> The matter at hand; i just registered a domain and i would
> like to configure my slackware machine to use this domain. Basically I
> want a to setup it for the home of the domain, like hosting companies
> do.

Your question is rather vague. What do you mean "use the domain"?
What do you mean "for the home of the domain"? A domain has a
registrar; you've already gotten that far. It has authoritative name
servers. Is that what you want the host to be? It has various machines
within the domain, as defined by DNS entries, which provide various
services. Is that what you want the host to do?


> I'm a newbie when
> it comes to networking and would like indepth instructions if possible.

No offense, but I do not think you are ready to do this kind of
thing. In order to know how to progress and be able to ask useful
questions, you need to learn a lot more about how the internet works.
Read up on DNS in particular.

--
Oh to have a lodge in some vast wilderness. Where rumors of oppression
and deceit, of unsuccessful and successful wars may never reach me
anymore.
-- William Cowper

Ryan wrote:
> nycdiesl@gmail.com wrote:
>
>>Hi. If this has been posted, sorry, I searched. I've been searching for
>>days, lol. The matter at hand; i just registered a domain and i would
>>like to configure my slackware machine to use this domain. Basically I
>>want a to setup it for the home of the domain, like hosting companies
>>do. For example; shell providers have single machines solely for shell
>>account hosting, a domain is assigned to the machine. I'm a newbie when
>>it comes to networking and would like indepth instructions if possible.
>>Links to newbie articles would be helpful too. Thank you all for your
>>time.
>>
>
>
> I'm guessing you'd need to use something like BIND to do some DNS
> mapping. Although.. I have a domain name.. which is linked to my ip
> address. Seeing as though my IP is dynamic, I have a script to update
> the free DynDNS account I have. So when my IP changes, my DynDNS address
> is pointing to the new IP address, and my .be domain name points to the
> DynDNS address. But of course, maybe working with BIND or something
> along the lines of that would be a lot easier (although I'm thinking the
> configuration and such will be pretty daunting).
>

Got a free domain off a provider recently too. Found bind pretty trickly
to setup in a moments notice so used dnsmasq to do it it's pretty easy.
First things first though grab yourself a copy of the Linux Network
Administrator's Guide from The Linux Documentation Project. (free download)

the /etc/dnsmasq.conf file is pretty easy to edit (man dnsmasq.conf) and
well commented, it should get you up and running within an hour or so.
For long-term I'd guess Bind is the go. That's where LNAG n others will
help. Specially if your gonna set up mail on your server (recently did
sendmail-uwimap-squirrelmail it rocks!)

I'd especially recommend taking the time to read the parts of LNAG that
apply like name resolution n details about the /etc/hosts file.

Karl

<nycdiesl@gmail.com> wrote

> "i just registered a domain and i would like to configure my
slackware machine to use this domain".


Also look into Zone pointing records.
I believe that pointing your domain name to static IP addresses
(supplied by your ISP), using the company you acquired the name from
(the Domain Registrar), would be the easiest way to begin.

Example Zone records:

www. [yourdomain.com] points to static IP address xx.xx.xx.xx
ftp. [yourdomain.com] points to static IP address xx.xx.xx.xx
machinename. [yourdomain.com] points to static IP address xx.xx.xx.xx
etc, etc.
DNS changes usually update within 48 hours.

Your registrar can probably offer something like this...
http://helpdesk.easyspace.com/faq.ph...&articleid=279

Finally, run netconfig on your Slack machine/s and enter the IP
address and domain name you've zone registered. Running any services
for the internet requires serious consideration these days regarding
security though, I'd not recommend you use your private workstation in
a public facing situation if you had that in mind.

If you do not have any static addresses allocated (your IP address
keeps changing) you may want to consider one of the Dynamic DNS
services available, as suggested previously.

If I'm missing the point completely, fill us in.
Best regards
CX

nycdiesl@gmail.com wrote:
> Hi. If this has been posted, sorry, I searched. I've been searching for
> days, lol. The matter at hand; i just registered a domain and i would
> like to configure my slackware machine to use this domain. Basically I
> want a to setup it for the home of the domain, like hosting companies
> do. For example; shell providers have single machines solely for shell
> account hosting, a domain is assigned to the machine. I'm a newbie when
> it comes to networking and would like indepth instructions if possible.
> Links to newbie articles would be helpful too. Thank you all for your
> time.
>

this _sounds_ like you're trying to modify dns records, so that
shell.yourdomain.example.com resolves to your machine and
www.yourdomain.example.com resolves to your website and stuff.

for that, you have two choices - build your own dns server and host it
all yourself or use the facilities of the company your domain name is
registered through.

for example - my domain is rollingviolation.com. register.com handles
the dns records for variuous reasons instead of me running my own
external dns server. (one day I may take over that, but not right now.)

on my internal lan, my /etc/resolv.conf has:
nameserver 192.168.1.3
nameserver 192.168.1.2
search raynic.rollingviolation.com

(I built two internal dns boxes because I'm a computer guy...)
as a result, www.rollingviolation.com is accessed as just webbox by me
internally... but that's probably not what you're looking for.

If you're just looking to change the name of your machine so instead of
it being darkstar, it's darkstar.yourdomain.example.com then run
netconfig as another poster suggested.

Dumb question -> what did you register the domain name for? Do you want
to create a web site? Are you running a web server in your basement?
Are you building a mail server? I'm not quite sure what you're trying
to do, so we might be pointing you in the wrong direction.

Ray