nameservers and perls of buying cheap domain name

"Andrei Ivanov" <iva@racoon.riga.lv> wrote in message
news:3fp8laF8vsmnU1@individual.net...
> newsreader <cc0101172@minix.midltn01.nj.comcast.net> wrote:
>> www.mydname.com. 20S IN CNAME premium5.geo.yahoo.akadns.net.
>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.46
>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.47
>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.44
>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.45
>
> Did you see my posting on 5/24/2005?
> If so, then what part of it didn't you understand?
>
> --
> andrei

Andrei,
I saw the post and tried adding the following to section 3 of the httpd.conf

NameVirtualHost <69.7.239.163:80>

<VirtualHost 69.7.239.163>
ServerName www.mydname.com
ServerAlias mydname.com
#ServerAlias www.mydname.com
# DocumentRoot /users/4sale/
</VirtualHost>

I then tried switching ServerName to mydname.com and alias to
www.mydname.com but this
didn't work either. I added 69.7.239.163 www.mydname.com to /etc/hosts and
also adding
www.mydname.com to ServerName in section 2 of httpd.conf I added IP address
entries to
Listen and BindAddress in conf file, but typing www.mydname.com/anypath to a
browser address
bar redirects all requests back to main IP address 69.7.239.163 as specified
by yahoo redirect.
For a while I had it working when dropping off www but I have tried so many
permutations I have forgotten which way I had it configured. I will have to
look in the O'Reily DNS
book I have at work.

In answer to your question, I wasn't familiar with terms "2nd and 3rd level
domain". Please excuse my
ignorance, this is a work in progress and something I haven't tackled
before.

Thanks for your help

MikeD.

Mike Dundas <mdundas@nospamthanks.comcast.net> wrote:
>>> www.mydname.com. 20S IN CNAME premium5.geo.yahoo.akadns.net.
>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.46
>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.47
>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.44
>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.45
>
> I then tried switching ServerName to mydname.com and alias to
> www.mydname.com but this didn't work either.

You've mentioned that you have control over your DNS records.
And I suggested that "both A-records, for "mydname.com" and
"www.mydname.com", should point to the same ip address,
69.7.239.163".

Right now the "mydname.com" domain name resolves to four
IP addresses. The "www.mydname.com" domain name also points
to the same IPs (premium5.geo.yahoo.akadns.net). Instead, both
should point to IP address of your own web server, 69.7.239.163.

Dig's output should report something like this:

mydname.com. 30m IN A 69.7.239.163
www.mydname.com. 30m IN A 69.7.239.163

Or this:

mydname.com. 30m IN A 69.7.239.163
www.mydname.com. 30m IN CNAME mydname.com.

Can you do that?

--
andrei

Andrei Ivanov <iva@racoon.riga.lv> wrote:
> Mike Dundas <mdundas@nospamthanks.comcast.net> wrote:
>>>> www.mydname.com. 20S IN CNAME premium5.geo.yahoo.akadns.net.
>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.46
>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.47
>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.44
>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.45
>>
>> I then tried switching ServerName to mydname.com and alias to
>> www.mydname.com but this didn't work either.
>
> You've mentioned that you have control over your DNS records.
> And I suggested that "both A-records, for "mydname.com" and
> "www.mydname.com", should point to the same ip address,
> 69.7.239.163".
>
> Right now the "mydname.com" domain name resolves to four
> IP addresses. The "www.mydname.com" domain name also points
> to the same IPs (premium5.geo.yahoo.akadns.net). Instead, both
> should point to IP address of your own web server, 69.7.239.163.
>
> Dig's output should report something like this:
>
> mydname.com. 30m IN A 69.7.239.163
> www.mydname.com. 30m IN A 69.7.239.163
>
> Or this:
>
> mydname.com. 30m IN A 69.7.239.163
> www.mydname.com. 30m IN CNAME mydname.com.
>
> Can you do that?
>
Andrei

I changed the A Record for www.mydname.com and mydname to point to
my IP but then yahoo somehow links the dominnames to a default homepage
which is basically a template on yahoo with rigid structure. I really dont
have much control over it and cannot embed html in the template.

If I set the "domain forward" to my ipaddress it goes to my site. As I
said I had it working for mydname.com (for a while at least) but adding
www to the domainname just sends me to the IP address and shows doc root.

should I have to add entries to Listen and BindAddress etc or just the
Virtual hosts directives?

I do have control over the Nameservers. Are these the authoritative servers?
If I were to set up DNS or Bind on my server is this an option, or is this a
huge task!

Thanks again,

Mike D

On Fri, 27 May 2005, newsreader <cc0101172@minix.midltn01.nj.comcast.net>
wrote:
> Andrei Ivanov <iva@racoon.riga.lv> wrote:
>> Mike Dundas <mdundas@nospamthanks.comcast.net> wrote:
>>>>> www.mydname.com. 20S IN CNAME premium5.geo.yahoo.akadns.net.
>>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.46
>>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.47
>>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.44
>>>>> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.45
>>>
>>> I then tried switching ServerName to mydname.com and alias to
>>> www.mydname.com but this didn't work either.
>>
>> You've mentioned that you have control over your DNS records.
>> And I suggested that "both A-records, for "mydname.com" and
>> "www.mydname.com", should point to the same ip address,
>> 69.7.239.163".
>>
>> Right now the "mydname.com" domain name resolves to four
>> IP addresses. The "www.mydname.com" domain name also points
>> to the same IPs (premium5.geo.yahoo.akadns.net). Instead, both
>> should point to IP address of your own web server, 69.7.239.163.
>>
>> Dig's output should report something like this:
>>
>> mydname.com. 30m IN A 69.7.239.163
>> www.mydname.com. 30m IN A 69.7.239.163
>>
>> Or this:
>>
>> mydname.com. 30m IN A 69.7.239.163
>> www.mydname.com. 30m IN CNAME mydname.com.
>>
>> Can you do that?
>>
> Andrei
>
> I changed the A Record for www.mydname.com and mydname to point to
> my IP but then yahoo somehow links the dominnames to a default homepage
> which is basically a template on yahoo with rigid structure. I really dont
> have much control over it and cannot embed html in the template.
>
> If I set the "domain forward" to my ipaddress it goes to my site. As I
> said I had it working for mydname.com (for a while at least) but adding
> www to the domainname just sends me to the IP address and shows doc root.
>
> should I have to add entries to Listen and BindAddress etc or just the
> Virtual hosts directives?
>
> I do have control over the Nameservers. Are these the authoritative servers?
> If I were to set up DNS or Bind on my server is this an option, or is this a
> huge task!

What you fail to grasp is that you are using a redirection or forwarding
service, so they determine what shows in the first part of the URL bar.
Nothing you do in apache is going to change that until you do away with
the redirection or forwarding altogether, and have names resolve in
"public" DNS directly to the public IP of your server (your comcast
connection?).

Until you can get host or nslookup or dig to resolve your names to the
public IP of "your" server, any attempt to reconfigure your apache to show
your domain name will be futile. For now, the names apparently resolve to
the redirection or forwarder service that is not under your control.

"David Efflandt" <efflandt@xnet.com> wrote in message
news:slrnd9gih7.24f.efflandt@typhoon.xnet.com...

> > What you fail to grasp is that you are using a redirection or forwarding
> service, so they determine what shows in the first part of the URL bar.
> Nothing you do in apache is going to change that until you do away with
> the redirection or forwarding altogether, and have names resolve in
> "public" DNS directly to the public IP of your server (your comcast
> connection?).
>
> Until you can get host or nslookup or dig to resolve your names to the
> public IP of "your" server, any attempt to reconfigure your apache to show
> your domain name will be futile. For now, the names apparently resolve to
> the redirection or forwarder service that is not under your control.

David,
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!

Thank you,

Mike D

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.

On Sat, 28 May 2005, Mike Dundas <mdundas@Nospamthanks.comcast.net> wrote:
>
> "David Efflandt" <efflandt@xnet.com> wrote in message
> news:slrnd9gih7.24f.efflandt@typhoon.xnet.com...
>
>> > What you fail to grasp is that you are using a redirection or forwarding
>> service, so they determine what shows in the first part of the URL bar.
>> Nothing you do in apache is going to change that until you do away with
>> the redirection or forwarding altogether, and have names resolve in
>> "public" DNS directly to the public IP of your server (your comcast
>> connection?).
>>
>> Until you can get host or nslookup or dig to resolve your names to the
>> public IP of "your" server, any attempt to reconfigure your apache to show
>> your domain name will be futile. For now, the names apparently resolve to
>> the redirection or forwarder service that is not under your control.
>
> David,
> 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!

Typically for your own nameserver to do public DNS, it would need to be a
static IP (DHCP that rarely changes may not be good enough) and would be
need to be set as a nameserver for your domain with your domain registrar.
Most require at least 2 nameservers. That also assumes that you can
properly configure bind (named).

If you have a dynamic IP or are unsure of your abilites to configure a
nameserver, there are other services that can do that. I may have
mentioned that I use no-ip.com, but you can find others with a web search
for 'dns hosting'. Just remember that you need to tell your registrar the
nameservers for your domain before they will work for the public. And if
previous expire time was too long, it may take awhile (days to a week)
before it will expire from present DNS caches. Dynamic DNS services may
expire in 1 to 5 minutes, so they do not remain in cache very long.