Setting up External Addon Domain

[mr_ian84]

Hi
I'm a potential customer to bluehost and I would like to know if the setup i want is supported.

I have already a domain which i cannot transfer. I had a look at your demo login and noticed that you support addon domains and offer 3 choices to verify ownership. One is to change the nameservers of the domain in question, the other to change the A record of the domain to point to 69.89.30.141 or creating some html page with some value.
The problem is that when i typed in the subdomain www (www.domain.com) the system would not let me. But something like subdomain.domain.com is ok.

Is the www subdomain supported please? I would just like to keep my existing domain settings, just create an A record and point it to bluehost servers. Then everything should work with the Host http header.

Ian

[felgall]

www just points to the same place as the domain name without the www so www.example.com and example.com are equivalent.

[Mindfield]

For what it's worth, I'm having the same problem.

I am hosting another site related to my site's interests. He has registered the domain (www.iwebkit.net) and pointed the DNS servers to ns1 and ns2.bluehost.com, plus added the proper IP address to his DNS "A" record, so everything should work fine.

The problem is that I can't associate his domain. Whenever I try to add an addon domain, the domain manager tells me that verification is required when I enter "iwebkit.net" as the addon domain. His DNS records are correct, but the domain manager says that his DNS servers are still pointing at NS1 to NS4.domainsite.com. Doing a whois on iwebkit.net confirms this.

The strange thing is that going to www.iwebkit.net takes me to Bluehost like it should (not his subdomain yet because it's not yet associated as an addon domain), but going to just iwebkit.net goes to a parked domain template site.

Is this an issue of propagation? Will iwebkit.net eventually take like www.iwebkit.net has already, or is further action required?

[felgall]

How long ago did you make the change? If it is only in the last day or two then it is possible that the DNS that BlueHost are looking up hasn't been updated yet.

DNS get updated at different times based on the schedules that the thousands of different DNS owners set. While most are updated within hours of a change and most are updated within a day or two, there are a few DNS that only get updated every few weeks. Where a domain appears to be depends on which of the thousands of different DNS gets used for the lookup.

[mr_ian84]

this did not answer my question so let me rephrase

can i have an addon domain say www.mydomain.com where it's name servers still point to my original name servers and not bluehost's nameservers. Thus the changes i would do is create an A record for mydomain.com and www.mydomain.com to point to bluehost's ip addresses

thanks
Ian

[felgall]

An add-on domain is one that is in a folder within your existing hosting. It can't be in a folder on your hosting and be somewhere completely external to your hosting at the same time. If a domain isn't on the same hosting then it isn't an add-on domain.

BlueHost does not currently have a domain name control panel to handle externally hosted sites - it only handles sites hosted on BlueHost. If you want a domain to point to hosting elsewhere you'd need to get support to set it up for you.