Bluehost to FreeDNS to Weebly- urgent

[sirdouglas]

I apologize for the urgency of this post, but my e-commerce website is supposed to be launched by now but is still not working. My domain is registered through Bluehost, but I only have hosting through Weebly, which means I cannot access the advanced DNS settings in the Cpanel to point my domain to the correct IP address on Weebly.

Bluehost customer support recommended that I use freeDNS.afraid.org to modify any DNS settings, but they could not provide further support specifically about FreeDNS. I successfully added ns1.afraid.org as a custom nameserver on Bluehost and can now modify the settings on FreeDNS, but am having diffulties.

I need to point my domain to 199.34.228.100 by creating two A-records, one for "www" and another for either "*" or "@". On FreeDNS I can edit my subdomain with the following options:

Type: (I chose A)
Subdomain: (I can type anything, not sure what to do though)
Domain: (I selected the domain from a dropdown menu)
Destination: (I put 199.34.228.100)
TTL: _____ seconds (it's optional to fill in)
Wildcard: (There's a checkbox to enable for all subscribers)

What must I fill in to do BOTH A-records? I don't see any options regarding the "www" and "*" or "@". Interstingly, I filled in as much as I know and my domain would just forward to the freeDNS website. This morning, it was actually working with my domain, but then it mysteriously stopped, so it forwards to FreeDNS again. What am I doing wrong, and how can I ensure that it consistently works?

If anyone can help me out with this I'd really appreciate it.

Thanks!

Doug

[sirdouglas]

Strangely, it is working again. However, I may have modified the DNS settings incorrectly yet since it seems to be working off and on. Let me know if it should be set up differently.

Thanks,

Doug

[sirdouglas]

... and now it's not working once again. It just forwards to the FreeDNS website, so something must still be wrong. Any ideas? Thanks again.

[Brent2]

It sounds like you may only have your DNS partially set up (with some still pointing to Bluehost). You mentioned that you put ns1.afraid.org as a custom nameserver. Did you do both ns1.afraid.org and ns2.afraid.org? If you left half BH (ns2.bluehost.com) and half FreeDNS (ns1.afraid.org) then I'd fully expect to see the intermittent error you're experiencing.

If so, just replace ns2.bluehost.com with ns2.afraid.org and wait a day or three for everyone to catch up. If not, maybe also give us the domain so we can look at the public DNS records and see what needs to be changed.

[sirdouglas]

Thanks for the help. I do actually have both ns1 and ns2 correctly entered though, so there must be another problem. The domain is forwarding to the FreeDNS website still. The domain is www.datababies.com. Are you able to see anything in the public DNS records that might be causing this?

Thanks again,

Doug

[sirdouglas]

Hey again. Could someone please help me with this? A story was published about my product just today, and I have been receiving emails from customers trying to purchase my product who are unable to access the site. FreeDNS has not been responding to my emails, and I desperately need to resolve this issue.

I sent another email to FreeDNS re-explaining all the details, so I will copy/paste the details here once again:

Hey I have a domain (www.datababies.com) with Bluehost that I need to have pointed to Weebly, but I cannot access the DNS settings in Bluehost. So I added both ns1.afraid.org and ns2.afraid.org to my nameservers in Bluehost.

I need to create both A-Records for BOTH "www" and for "*" or "@", pointing the domain to 199.34.228.100. I accessed my domain manager in my FreeDNS account and have 6 subdomains:
ftp.datababies.com (G) Not Yet Configured
irc.datababies.com (G) Not Yet Configured
mail.datababies.com (G) Not Yet Configured
datababies.com (G) A 199.34.228.100
datababies.com (G) MX 10: mail.datababies.com
www.datababies.com (G) A 199.34.228.100

For dataBabies.com I have:
Type: A
Subdomain: blank
Domain: datababies.com (public)
Destination: 199.34.228.100
TTL: Subscribers only
Wildcard: unchecked

For www.datababies.com I have:
Type: A
Subdomain: www
Domain: datababies.com (public)
199.34.228.100
TTL: Subscribers only
Wildcard: unchecked

Thanks,

Doug

[sirdouglas]

I might have resolved it, added ns3.afraid.org and ns4.afraid.org to my nameservers. We'll see how that works. Otherwise I'll post back again! Thanks guys!

Doug