// Admin tip: use a CNAME DNS RR as alias for services like DynDNS.com

Dynamic DNS services like DynDNS are very useful, e.g. for LAN access via VPN in combination with non-static IP addresses. But the dynamic DNS hostname is normally a subdomain of the service (e.g. example.dyndns.org) which is often hard to remember. And this name is tying yourself up to the service you are using because a change may be really annoying (you have to change documentation, inform users and stuff).

I'm always wondering why most admins don't use a simple trick to solve all these problems: Use a sub-domain of your own domain (e.g. vpn) and set a CNAME RR for it. Let it simply point to your dynamic DNS hostname:

vpn.example.com.   CNAME  example.dyndns.org.

That's all, you are be able to use vpn.example.com from now on. A sub-domain of your main address should be much easier to remember and you can switch to another dynamic DNS service whenever you want. Without any noticeable difference for a common user.

Leave a comment…




L P X᠎ W L
  • E-Mail address will not be published.
  • Formatting:
    //italic//  __underlined__
    **bold**  ''preformatted''
  • Links:
    [[http://example.com]]
    [[http://example.com|Link Text]]
  • Quotation:
    > This is a quote. Don't forget the space in front of the text: "> "
  • Code:
    <code>This is unspecific source code</code>
    <code [lang]>This is specifc [lang] code</code>
    <code php><?php echo 'example'; ?></code>
    Available: html, css, javascript, bash, cpp, …
  • Lists:
    Indent your text by two spaces and use a * for
    each unordered list item or a - for ordered ones.
I'm no native speaker (English)
Please let me know if you find any errors (I want to improve my English skills). Thank you!
QR Code: URL of current page
QR Code: URL of current page 2011:01:29:use-dns-cname-for-dynamic-dns-services-like-dyndns (generated for current page)