PHWinfo - Afficher un message - nameservers and perls of buying cheap domain name

30/05/2005, 05h31

On Sat, 28 May 2005 19:39:06 -0400,
"Mike Dundas" <mdundas@Nospamthanks.comcast.net> posted:

> is it then possible to have the address resolved by my own dns server. Or,
> as you point out, (Re: fail to grasp), this also has nothing to do with it
> and even using my own nameservers will not change this!

You need to change a few things.

You need a webserving host that you can properly control. One that you can
set the domain name that it responds to. That's a webserver configuration
and a DNS configuration issue.

You need your domain name registered with a service that allows you to set
the domain name to point to the IP that you want, directly. No redirection
services.

Let's say you register the domain "example.com", and you also pay for
website hosting from some webhost that serves from the numerical IP address
of 192.0.34.166.

You configure your DNS records to point example.com to 192.0.34.166, and
vice versa, using 192.0.34.43 and 193.0.0.236 as the authoritative name
server for your domain. (Do a dig on that domain name to see.) You'd
probably also configure www.example.com to point to the same 192.0.34.166
numerical IP address.

Alternatively, you might use the webhost's DNS servers as your
authoritative DNS server. You don't have to. You can manage your DNS
anywhere that you care to, so long as the other host that's serving your
files doesn't enforce some annoying restrictions on you.

Then comes the configuration for the webserver. In some cases there
mightn't need to be any customisation, it might simply respond to requests
it receives as they come. But, these days, most low budget hosts use one
webserver to serve out multiple websites (virtual hosting). They need each
site to be configured for the domain name(s) that they respond to.

But if you use some cheap redirecting service, you can throw all of that
out the window. The DNS data points to the redirecting serving in the
middle. And the point I made earlier still stands, there's not that much
price difference between this silly way of doing it, and the proper way of
doing it. You've just to got to look around a bit to find the services
that you need.

As a general warning, be careful about paying to register a domain name
through the same company that will host your webpages. You might find it
difficult to separate the two, if you need to (some contract you into a
corner, others are just plain annoying to try and deal with). You may also
find that they own the domain name (e.g. example.com), and you're just
paying for a sub-domain (e.g. myspace.example.com).

--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.

This message was sent without a virus, please delete some files yourself.

30/05/2005, 05h31	#10
Tim Messages: n/a Hébergeur:	Re: nameservers and perls of buying cheap domain name On Sat, 28 May 2005 19:39:06 -0400, "Mike Dundas" <mdundas@Nospamthanks.comcast.net> posted: > is it then possible to have the address resolved by my own dns server. Or, > as you point out, (Re: fail to grasp), this also has nothing to do with it > and even using my own nameservers will not change this! You need to change a few things. You need a webserving host that you can properly control. One that you can set the domain name that it responds to. That's a webserver configuration and a DNS configuration issue. You need your domain name registered with a service that allows you to set the domain name to point to the IP that you want, directly. No redirection services. Let's say you register the domain "example.com", and you also pay for website hosting from some webhost that serves from the numerical IP address of 192.0.34.166. You configure your DNS records to point example.com to 192.0.34.166, and vice versa, using 192.0.34.43 and 193.0.0.236 as the authoritative name server for your domain. (Do a dig on that domain name to see.) You'd probably also configure www.example.com to point to the same 192.0.34.166 numerical IP address. Alternatively, you might use the webhost's DNS servers as your authoritative DNS server. You don't have to. You can manage your DNS anywhere that you care to, so long as the other host that's serving your files doesn't enforce some annoying restrictions on you. Then comes the configuration for the webserver. In some cases there mightn't need to be any customisation, it might simply respond to requests it receives as they come. But, these days, most low budget hosts use one webserver to serve out multiple websites (virtual hosting). They need each site to be configured for the domain name(s) that they respond to. But if you use some cheap redirecting service, you can throw all of that out the window. The DNS data points to the redirecting serving in the middle. And the point I made earlier still stands, there's not that much price difference between this silly way of doing it, and the proper way of doing it. You've just to got to look around a bit to find the services that you need. As a general warning, be careful about paying to register a domain name through the same company that will host your webpages. You might find it difficult to separate the two, if you need to (some contract you into a corner, others are just plain annoying to try and deal with). You may also find that they own the domain name (e.g. example.com), and you're just paying for a sub-domain (e.g. myspace.example.com). -- If you insist on e-mailing me, use the reply-to address (it's real but temporary). But please reply to the group, like you're supposed to. This message was sent without a virus, please delete some files yourself.