Understanding DNS, custom domain forwarding to blogger.com

[OneGrassRoot]

It seems it's just a matter of time before the blog pulls up properly with the custom domain (I realize they say it could take up to 48 hours but I've never had it take more than 8).

However, I want to make sure that's what it appears to be to you guys or if I need to report it.

So, I registered the domain from my regular registrar (btw, I've used Domain Name Systems for 10 years and they've always been awesome - I know godaddy has had issues with domain redirects of late); directed DNS control to my account at mydomain.com; programmed the CNAME and other elements properly according to blogger.com/Google instructions; and set up the blog's publishing information for the custom domain.

I've checked and rechecked and everything seems in order. I've done this before with a different site/domain, the exact same steps, and it worked fine.

I don't get a 404 error. What I get is the "parked" page that comes up from my registrar. At mydomain.com, however it has confirmed since about 8:00 this morning that it is "active in their DNS servers for web browsing."

So, since there is no error, per se, should I just be patient? Has it ever taken this long for any of you when redirecting DNS information?

Thanks! :hi:

[ChromeFoundry]

1. DNS changes get requeried by downstream

caching servers based on the records Time-To-Live (TTL). Be patient, it will propagate eventually.

[OneGrassRoot]

2. Ah, propagate, that's the word. :)

Thanks for confirming patience is what's needed.

:)

[OneGrassRoot]

3. Before bed last night it became page load error...

can't connect to server. Is that part of the process, do you think? Going from that parked page to a page load error (firefox) or can't connect to server (IE)?

[Tandalayo_Scheisskopf]

4. Here is something you can do to speed up your access:

Level 3 has two public DNS servers and great leaping schnickies, are they ever fast. They are at 4.2.2.1 and 4.2.2.3

Point your DSL or Cable modem at them and you will likely see your site.

[OneGrassRoot]

5. I didn't understand any of that. LOL

But I'd like to learn!

Actually, with regard to the domains, the hosting company shows them as active in DNS servers, but the site STILL won't load when using the custom domain. If I revert to the blogspot addy, it comes up, so it must be a glitch with the host server, right?

Oy. This is driving me batshit crazy!

The Blogger Help site just keeps checking and saying there is no CNAME or A name value recognized for the URL; but that information is plugged in correctly.

Any ideas?

Thanks. :)

[OneGrassRoot]

6. To continue on this DNS management subject......

A couple of things:

1. I compared how the DNS controls look for the URL I'm trying to redirect versus ones that currently work just fine. Even though CNAME and A values were fine, and even though I had "disabled email forwarding" according to instructions, there was no value in there, whereas for the other domains there was an email forwarding addy. So, I have done that.

And, even though mydomain.com said the DNS is active in their server for the problematic domain, it said it wouldn't be active for email until the server was recognized -- soooooo maybe the email/MX thingie was the glitch? I'll check in a couple of hours to see.


2. Also, can someone educate me as to why I should use domain redirect using CNAMES and such rather than the stealth URL forward feature? Does it have something to do with SEO and Google searches or something?

:)