No, that's incorrect - see https://en.wikipedia.org/wiki/CNAME_record

Bzzzzzzzz..... (sound of a Yak being shaved!)

Brad

I think you are misunderstanding what the Wikipedia article is telling you. From the article:

A Canonical Name record (abbreviated as CNAME record) is a type of resource record in the Domain Name System (DNS) used to specify that a domain name is an alias for another domain, the "canonical" domain. All information, including subdomains, IP addresses, etc., are defined by the canonical domain.

What this means is that www.bcstechnology.net should point to an IP address and hence be an 'A' record, whereas bcstechnology.net should point to a machine's fully-qualified domain name (FQDN) and hence would be a CNAME.

Please read farther down in the Wikipedia record and you will see a proper CNAME example:

Code:

NAME                    TYPE   VALUE
--------------------------------------------------
bar.example.com.        CNAME  foo.example.com.
foo.example.com.        A      192.0.2.23

The above conforms to RFCs 1034 and 2181.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

But being a cname or an A-record shouldn't matter for a browser in any case.

You're correct. However, whatever is dishing out DNS information to the browser might have a problem with a CNAME pointing to an IP address instead of a machine name..

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Perhaps in future if one of us discovers a non-working link in a post, we can just send a PM to the poster?

Then we might avoid enormous digressions in technical threads.

AKA... "Shaving a Yak".

http://www.hanselman.com/blog/YakShavingDefinedIllGetThatDoneAsSoonAsIShaveThisYak.aspx

Brad