|
I am thinking about buying the Custom DNS service, but not 100% sure if things will work out as I expect. Lets say I/or my company owns http://example.de (Yes it is a German domain, which may cause problems?). It is hosted with a provider which also does the website and other stuff. So I am not able to leave that provider/hoster. (Even if I would like to. :D) I want to be able to use for example http://test1.example.de and test2.example with a server within my company's network (with dynamic IP). If I now buy Custom DNS for http://example.de and change the NS records for my desired subdomains with the DNS servers provided by DynDns, will I be able to resole the subdomains to my dynamic IP. And do sub-subdomains or wildcards work automatically? Can I use http://xx1.test1.example.de and so on without changing something with http://example.de's hoster? Would be great to test some beta services. As described in the How To .DE domains have some problems, because they have to provide all 5 NS records. Does this affect me? Yes I know this question has been discussed on the forums at least a hundred times, but I just want to get sure. Would be glad for any advice. Thanks. |
|
The way DNS works is you delegate a domain name (such as http://example.de) to a DNS provider. That DNS provider would then provide DNS that domain. You can then have one or more subdomains delegated to other DNS providers (using NS records) if you so wish. There are two scenarios you can choose between: 1) Have DynDNS handle all of your DNS for your domain. That means delegating your domain name to the DynDNS Custom nameservers. You create all of your DNS records on DynDNS. This is by far the simplest (and cheapest) solution and what I recommend. This guide would cover the above scenario: http://www.dyndns.com/support/kb/de_domains_in_custom_dns.html 2) Have the DNS for most of your domain at another DNS provider. For the couple of subdomains that you need Dynamic DNS for, you would purchase DynDNS Custom for each of those subdomains. You then create NS records at your current DNS provider that delegate the subdomain to DynDNS' nameservers. This scenario is more complicated (and expensive). This guide will cover scenario #2: http://www.dyndns.com/support/kb/using_custom_dns_with_subdomains.html Thanks. Really appreciate your help. Good explanation.
Feb 27 at 11:08 AM
webstyler
|
|
To do it the way you describe you'd have to purchase 2 separate packages, one for You would, if you did that, find that all subdomains of the 2 names would work automatically once created in Custom DNS. You will however need either multiple public IP addresses, to use a reverse proxy (like HAProxy) to forward requests to the correct host or to use a different port for each device on the LAN.
Because anybody using the Internet Guide DNS service would only see your DNS records held at DynDNS. They wouldn't see the rest of your DNS unless you duplicated the records there.
I don't know - it would depend on how you performed the delegation of those 2 sub-hosts.
Nobody else would normally be querying the DynDNS DNS servers for a domain which has a WhoIs entry that points to other DNS servers.
I don't know what the actual separation of those platforms is, and how it all hooks together. I'd assume the worst case scenario without anything further to go on (as I've been there before). Thank you for your help. Really appreciate it.
Feb 19 at 08:52 PM
webstyler
You said "Because anybody using the Internet Guide DNS service would only see your DNS records held at DynDNS". Why is this limited to IG users only?
Feb 26 at 06:36 PM
RotBlitz ♦
Sorry, I still don't see it. DynDNS' recursive DNS service is pretty much logically separated from their authoritative DNS services. I would not expect IG doing something totally different from any other recursive DNS service. Would be interesting to verify your theory with a real existing domain.
Feb 26 at 09:05 PM
RotBlitz ♦
|
|
Just got a new idea. (Sorry bringing up this topic again.) You said that it is not good to register http://example.de with DynDns Custom, but only use some subdomains, because people using Internet Guide wouldnt find http://example.de (hosted on an other server) any more. I got that. My idea is: I register http://example.de with DynDns Custom, but then redirect DNS requests for http://www.example.de and http://example.de to the original server via a NS record. So I would use all my subdomains with my dynamic server, but all the traffic for http://www.example.de and http://example.de would still arrive at the original http://example.de server. Is this possible or just a completely stupid idea? (It would help to make the entire thing cheaper.) Thanks for any replies in advance. |
|
I don't think you could make that work, redirecting only higher level domains. DNS is designed to work the other way up, delegating only sub-domains. Ok. Thanks. Was just a stupid idea. Got it. :D
Feb 27 at 12:22 AM
webstyler
|
|
Thanks for your help. Can you explain why it is not possible to purchase http://example.de but only use the subdomains? Would, as you said, much more cost effective. Regarding the problem with .DE domains mentioned in the how to (http://www.dyndns.com/support/kb/de_domains_in_custom_dns.html), do you think this would affect me? |