Mark McDonald wrote:

I've registered my domain.
Now I'd like to serve it.

I've read and setup the DNS HOWTO and everything works well (for my
internal network). [DSL connection with almost static IP].



If your connection is *almost* static, I don't think you can use traditional name servers. They'll go bonkers when your IP changes (or actualy won't work at all).


Take a look at dyndns.org . This seems right up your alley. They are free to cheap, depending on what service you opt for. And they won't cut you off if your IP address changes. They are totally set up for dynamic IP addresses already, so you should be a shoo in.

Basically, you download a small program on your server that runs whenever your server starts, and sends them your new IP address. They do the rest, serving your IP address to who ever asks for it. I think they know when you shutdown as well so they can handle unreachable connections gracefully. They have a lot of other services too, which I haven't really looked at, but seem cool.


This HOWTO
is essentially a cacheing nameserver.

Now I'd like to have named point to my external IP address - that is
pretty easy.


The trick seems to be setting the nameserver on the domain (ie where I
registered it).  The nameserver has to be a fully qualified name (ie IP
address doesn't work), so how do I get it to point to my computer - it
seems to be a chicken and egg situation...

I think the answer is that I need someone to be a secondary dns server
for me - am I right, and if so is there a freebe way of doing this?

My end goal here is to set up a family email and web server - so I'm
trying to keep costs to a minimum.

Mark.







-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to