ONLY use comcast hosted web site

Hello daveoman and welcome,

So, you have a domain that is hosted by Google and you do not want to transfer that domain under the Comcast umbrella. Also, in accordance with your " Our www and naked domain point to a web server on our old ISP. " statement, I construe this to mean that your domain has internal HTML code that accesses a web server within your Google ISP provider.

If you want to verify your Comcast domain(s) records information this can be done here. However,  you'll have to provide some more clarity on your " I really just want an IP address so I can create a CNAME for the www. " objective? I would also recommend that you register your free Comcast domain using the following  Register a custom domain .

My assumption 1: is that if you are looking for the intrinsic IP address of your customer.comcastbiz.net that you have already registered, just simply ping customer.comcastbiz.net. This will not be able to be used as a CNAM alias because this is not part of your naked domain pointing to your other server being hosted by Google. DNS records are not used for this implementation. 

My assumption 2: is that if you want to access your customer.comcastbiz.net from within your web server on your old ISP, then you can use specific XML constructs within your webserver on your old ISP to accomplish this. This would take some small web site development and Comcast does have web hosting facilities to assist you here .  

Hope this helps you out.

Hi Rich,

Firstly, thanks so much for the reply.

1)  I actually don't have any HTML within the google isp.  We just use that for email for our domain.  So, "mail." points there via a CNAME today.

2)  My objective with the "www." was to get to our customer.comcastbiz.net server that now has our HTML, but I really don't want any "customer.comcastbiz.net" name support at all.  I really just want "www.our domain.com" to point to the html on our "customer.comcastbiz.net" server.  The HTML references "www.our domain.com" internally.

3)  I'd like our naked domain to also point to the HTML.

4)  I don't want the MX records disrupted, as they point to the google hosted email today.

5)  I'm also curious if the naked domain is typically pointed to the web server, or if it points to the mail server in any occasions?  I know that when configuring email clients, it seems that they ask for that naked domain, do magic, and can then set email up without any other settings (besides username and password.)  I wonder if that's the naked domain pointing to the email server, or if the clients are smart enough to just go find the mx records of that domain and the naked domain isn't used for that purpose.

What is the best record scenario to accomplish the above?

Hi daveoma,

Please see my responses below.

Firstly, thanks so much for the reply.

You are welcome.

1)  I actually don't have any HTML within the google isp.  We just use that for email for our domain.  So, "mail." points there via a CNAME today.

Okay the above makes perfect sense.

2)  My objective with the "www." was to get to our http://customer.comcastbiz.net server that now has our HTML, but I really don't want any "customer.comcastbiz.net" name support at all.  I really just want "www.our domain.com" to point to the html on our "http://customer.comcastbiz.net" server.  The HTML references "www.our domain.com" internally.

If you just want to have your http://www.ourdomain.com (wodc) to access your new http://customer.comcastbiz net (ccn) website, then this will take some XML code inside your wodc. Your should be able to contact your Google wodc administrator and just give him the actual name of your ccn registered website, and this should provide access. If you currently have ccn HTML that accesses your wodc now, then you will need either a standard XML back construct in your  wodc that a user can navigate back to you ccn.  

3)  I'd like our naked domain to also point to the HTML.

Same response here as just above will get this accomplished.

4)  I don't want the MX records disrupted, as they point to the google hosted email today.

That is fine if you would like for Google to continue hosting your email. 

5)  I'm also curious if the naked domain is typically pointed to the web server, or if it points to the mail server in any occasions?  I know that when configuring email clients, it seems that they ask for that naked domain, do magic, and can then set email up without any other settings (besides username and password.)  I wonder if that's the naked domain pointing to the email server, or if the clients are smart enough to just go find the mx records of that domain and the naked domain isn't used for that purpose.

The answer to your above question is that your comcastbiz.net naked domain does in fact use this as the suffix for all email addresses hosted by customer.comcastbiz.net.   

What is the best record scenario to accomplish the above?

There is no best record option I am aware of to accomplish your objective. I have provided the XML means by which you can get back from your wodc after you access it form your HTML in your ccn website.

Hope this helps you out and regards... 

Hi Rich,

I think I'm getting closer...some more clarifications below:

2)  My objective with the "www." was to get to our http://customer.comcastbiz.net server that now has our HTML, but I really don't want any "customer.comcastbiz.net" name support at all.  I really just want "www.our domain.com" to point to the html on our "http://customer.comcastbiz.net"server.  The HTML references "www.our domain.com" internally.

If you just want to have your http://www.ourdomain.com (wodc) to access your newhttp://customer.comcastbiz net (ccn) website, then this will take some XML code inside your wodc. Your should be able to contact your Google wodc administrator and just give him the actual name of your ccn registered website, and this should provide access. If you currently have ccn HTML that accesses your wodc now, then you will need either a standard XML back construct in your  wodc that a user can navigate back to you ccn.  

I have duplicated our current website at our comcastbiz url with comcast (via ftp.)  I now want that comcastbiz url to not be necessary whatsoever.  So, I thought the way to go about was to go to my registrar and change the A record for our custom domain to now point to a different (the comcast) server (along with the naked domain.)  I can just ping the comcastbiz name and get an IP address and use it, but my fear would be that comcast changes the IP address at some point.

There is also the matter of the DNS records.  Right now, they still point to my "old" ISP, but I can easily change them to point to the comcast DNS numbers.

3)  I'd like our naked domain to also point to the HTML.

Same response here as just above will get this accomplished.

I would think this would only get accomplished if I actually change the A records to point to the comcast servers?

4)  I don't want the MX records disrupted, as they point to the google hosted email today.

That is fine if you would like for Google to continue hosting your email. 

As this is currently the way the MX records are set, this seems fine.

5)  I'm also curious if the naked domain is typically pointed to the web server, or if it points to the mail server in any occasions?  I know that when configuring email clients, it seems that they ask for that naked domain, do magic, and can then set email up without any other settings (besides username and password.)  I wonder if that's the naked domain pointing to the email server, or if the clients are smart enough to just go find the mx records of that domain and the naked domain isn't used for that purpose.

The answer to your above question is that your comcastbiz.net naked domain does in fact use this as the suffix for all email addresses hosted by customer.comcastbiz.net.   

I really have no need for the comcastbiz domain.  I have a custom domain already registered, but I just want to point it to my HTML code on the comcast servers.  I also have no need for any email from the comcastbiz domain.

What is the best record scenario to accomplish the above?

There is no best record option I am aware of to accomplish your objective. I have provided the XML means by which you can get back from your wodc after you access it form your HTML in your ccn website.

I'm sorry...I meant "record" suggesting the way to manipulate the A, CNAME, and DNS records at my registrar.  I was thinking that I needed:

A record for mydomain -> comcast server that has my HTML  (this will then cause URLs of mydomain.com and www.mydomain.com to find the comcast server I hope)

CNAME record for mail.mydomain.com -> googlehosted (this currently works fine)

DNS records -> point to the comcast dns (so all mydomain.com requests will get resolved to the comcast server).

I think that is it?  I was just really concerned about what the comcast portal would be doing when I started going through the steps of "bring over a custom domain."  I didn't want my email disrupted.

Thanks again.