10-28-2014 06:04 AM
I hope you are rocking out there.
Can someone please help me with following scenario?
The customer has registered all the required domain with .ae tld.
However there are a few domain names which doesn't have any web servers or web app mapped, (basically they registered it just for reservation purpose).
How can we forward queries to a particular URL which doesn't hosting any web service? Ultimately customer doesn't want to display "Page cannot displayed" page, instead it should forward it to a particular URL.
Total number of such domains are around 100. So mapping CNAME for each would be a lot of administrative overhead. Any suggestion in this case?
10-28-2014 06:08 AM
But you can create an A record in a Shared Record Group at the domain level (and perhaps the www equivalents) and set the IP address to the same IP of the web server you want the end users to go to. Then you would associate the shared record group with all of the "vanity" domains.
A URL is an HTTP/HTTPS protocol specific thing and the DNS server is completely unaware of the URL. The only thing it can process is the domain name portion based on the query it gets from the client.
10-28-2014 12:01 PM
You'll want to review the Admin Guide, chapter 19, About Shared Record Groups. That's a good start to understand how they can be leveraged. Follow the steps below for a practical application.
First, create a Shared Record Group and call it something like "Common Records".
- Navigate to Data Management -> DNS -> Shared Record Groups (SRG)
- Create a new SRG and assign the name, then click Next
- Associate the SRG with all of your "vanity" zones
- Save the SRG
Next, you'll click into the SRG and create your records
- Generally, you would create a "www" A record with the IP address of the web server you want to redirect to your primary web server
- You can optionally create a "blank hostname" record with the same IP address as well (this is for when people enter "company.com" instead of "www.company.com"
That's it. Now any time you look at your zone, you'll see these additional A records but they will be indicated as "(Shared)" in the type field. They will resolve and point all clients/users to same place.
One optional configuration that you can use is to leverage a "wildcard" instead of creating a "www" and "blank" record. To use this hostname (represented by a "*"), you MUST change the hostname policy of the SRG from "Allow Underscore" to "Allow Any". That will capture any hostname and redirect it. It may or may not be appropriate for your use and you must be careful not to use this wildcard in a "regular" zone without considering implications.
10-30-2014 02:24 AM
Is it possible to add multiple vanity hostnames instead adding individually? As those are apporximately 100. And it is not feasible to add them one by one, any idea what can be done here? Data import would be useful?
10-30-2014 02:15 PM
What kind of vanity hostnames are you referring to? Generally, a vanity name refers to a domain, not a host. For example, you might have company.com, company-is-great.com, company-is-stupid.com and you want to redirect any DNS request from any of those domains to come back with the same IP address that serves www.company.com.
In that case, you'd either use a wildcard or redirect www using the methods I've described above.
11-04-2014 01:14 AM
There are changes in the requirement now. They are owning plnety of domain names, which they want to forward to a particular domain name. Basically they are vanity names (for eg. abc.com, xyz.com, company.com etc). They need to forward each of these to mycompany.com for example.
For different host names, I cannot keep them under same zone and I need to have individual zones for individual domains, right? But here the question comes, how can I forward them to a partcular domain?
11-04-2014 04:58 AM
The DNS Firewall license may work for you (and is much easier to manage) but you can also leverage just creating a copy of the zone that you want to redirect and either create a CNAME pointing to the new domainname or use a DNAME. DNAMEs are deprecated so I'm not sure how long support will remain available in the DNS engine. You can also use wildcard records in case the redirection needs to happen at the apex of the domain.
I highly recommend talking to your local sales team given the shifting requirements that your customer has. There is likely a lot more information that would be helpful in determining the best approach.
08-24-2015 10:04 AM