redirect to without ip

Hi All, I hope you are well.

A web designer has designed a site that is hosted somewhere other than where the dns is for one of my customers

He has said that he needs to create a dns entry that will forward to, but he hasn’t got an ip address, only a name ( the ip that this name eventually resolves to will change over time, hence the need for a name.

I effectively need to create a cname for the root of the domain, but obviously I cant do that.

I cant use a 301 redirect either, so I don’t know what to do.

I don’t want to move the dns from where it currently is if I can avoid it.

What I am thinking is I need a service that will give me a static ip address so I can set up a blank A record to point to it. That service will then translate the ip address to the name

I was looking at webhops from dyn, but im not sure if that will work –

anybody got any advice please?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are you talking about doing this for external DNS, or is this your internal (Active Directory) DNS?
247computerdoctorAuthor Commented:
Best solution I see is to get a simple web server with a static address, and then redirect using the .httpaccess (301, permanent redirect) method, and redirect to www.

Your web developer should be able to do this for you, or just get a server with a static address in the first place.
Webinar: Cyber Crime Becomes Big Business

The rising threat of malware-as-a-service is not one to be overlooked. Malware-as-a-service is growing and easily purchased from a full-service cyber-criminal store in a “Virus Depot” fashion. Join us in our upcoming webinar as we discuss how to best defend against these attacks!

247computerdoctorAuthor Commented:
yeah, i agree, but he tells me he cant do that.

i can only do stuff with the dns. he keeps telling me that they can do it with godaddy dns so why cant we do it with our dns hosts. ive said that you just cant do that in dns, it has to be done on the webserver (and again as you say with a 301) but he "disagrees".
Well, CNAME for the root of the domain is not compliant with RFCs, but some DNS providers allow it.  Problem is, you never know when they will stop allowing it and break your website.

DYN, for example, does not allow it.  GoDaddy might, but for him to demand to use a DNS provider that does NOT enforce RFC compliance seems questionable.  Yes, I've also encountered folks who claim, "well it worked for me last time" and then think it's your problem to solve, because they can't be bothered to do things the right way.

My concern would be, if <random_DNS_provider> is not enforcing RFC compliance for this, then what else are they playing fast-and-loose with?

You probably already saw this one, but here's a discussion on ServerFault of this very issue:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
he tells me he cant do that.

Other people can....  ;)

(I know, I know.  This is someone else's project and you got pulled in after the check was written....)
247computerdoctorAuthor Commented:
i agree! ive even sent him the rfc.

godaddy (or 123reg) seem to allow you to put a "*" record into the dns console which allows you to put a name instead of an ip address in it.

it then does this redirect somehow, but even if its in the dns "console" there, it cant actually be in the dns.

what do i do??

all i can see to do is at current dns, put blank A record in with an ip.

get that ip address to translate to a name, then we are good. basically a "dns bridge". its like reverse ddns. which is dns!

is there such a service?
247computerdoctorAuthor Commented:
thanks for the serverfault link by the way, i hadnt seen that
Wildcard records are allowed, and used extensively, but I don't know whether it will redirect for the root of the zone.  

A wildcard will redirect anything that doesn't resolve otherwise.,, etc. will continue to work, while * will redirect any other addresses entered to the www page.   Prevents a page-not-found error if someone fat fingers the address.
Good discussion of wildcard records, here:

To quote RFC 1912, "A common mistake is thinking that a wildcard MX for a zone will apply to all hosts in the zone. A wildcard MX will apply only to names in the zone which aren't listed in the DNS at all."

So by the RFC, a wildcard should not redirect the root of the domain, since the root has SOA, NS, and possibly MX records associated.
247computerdoctorAuthor Commented:
we have one of those, and it works but not for the root

name *
type cname

what you say about a wildcard of the root makes sense as you say,  because then all the other records will be invalid, and you would be just pointing the dns at the place where the wildcard is.

you can do what we want with an A record, but then you have to put an ip address in, not a name.
From the GoDaddy front, yes, they do allow for you to create CName records that reference the wildcard (@) to represent the root domain, however, @ still point to an IP address; e.g. -Capture.JPG-saige-
So I don't think this is solvable purely from the DNS server side.

I still don't understand why the web guy thinks it's OK to have a website on a machine with a dynamic address.  If the address changes, then the site will be down until the TTL on the cached DNS entry expires everywhere and people are forced to query the authoritative server....

Is he trying to set up some kind of failover or global traffic manager or something?  DYN and other providers will do it better.
I agree completely.

247computerdoctorAuthor Commented:
me too!

thanks for the clarification.

i'll leave this open for a bit in case anyone has a better'll get your points in due course!!
247computerdoctorAuthor Commented:
apparantly go daddy do allow you to put a blank cname in
Yes.  You would have to transfer your DNS to GoDaddy.

Even then, however, you're dependent on GoDaddy to continue allowing non-RFC Compliant DNS entries.
247computerdoctorAuthor Commented:
yes, totally agree. i dont want to move it, but im in the middle of the customer and the web guy. however,the web guy seems to be coming over to my way of thinking.
247computerdoctorAuthor Commented:
guys - what do you think of this:

what actually is this? is it actually a blank cname?
Looks like they created a wildcard CNAME record.
247computerdoctorAuthor Commented:
is that a sensible thing to do?
It's what we just decided is not supported by the RFC.  It might work but it is not official and may not be supported by other DNS providers.
The right way to do this would be to have an A record for that points to your web server, and a wildcard CNAME that points to

Alternately, just have a www A record, and forget about redirecting from
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.