<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Is there a workaround to the DNS option 'multiple-cnames'? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696900#M21103</link>
    <description>You can safely change CNAME to A records. Anyway, when you use CNAME, the CNAME is resolved to another name, and then the another name to the A record. So, you could  even reduce que number of queries by specifying directly an A record instead of CNAME.&lt;BR /&gt;&lt;BR /&gt;Happy Xmas for you also!&lt;BR /&gt;</description>
    <pubDate>Thu, 22 Dec 2005 13:01:12 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2005-12-22T13:01:12Z</dc:date>
    <item>
      <title>Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696899#M21102</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;    I've be chasing the internet for a workaround regarding 'multiple-cnames' no more being "supporte" by BIND 9.2x (actually multiple-cnames has never been DNS compliant as stated in the RFC 1034 - but RFC 1034 has been loosen up to meet RFC 2181 for DNSSEC... ).&lt;BR /&gt;&lt;BR /&gt;    My customer is using BIND 8.x thus the option 'multiple-cnames' can still be used. But we are migrating towards BIND 9.2.3 which does not support that option any more thus leading to failed zones transferts...&lt;BR /&gt;&lt;BR /&gt;    How can I get things working... I can change the CNAME to A RRs but I not quite sure if it is the best solution. Can anyone help me out!&lt;BR /&gt;&lt;BR /&gt;    Many thanks and by the way happy Xmas!&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;\Viseth</description>
      <pubDate>Thu, 22 Dec 2005 11:29:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696899#M21102</guid>
      <dc:creator>viseth</dc:creator>
      <dc:date>2005-12-22T11:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696900#M21103</link>
      <description>You can safely change CNAME to A records. Anyway, when you use CNAME, the CNAME is resolved to another name, and then the another name to the A record. So, you could  even reduce que number of queries by specifying directly an A record instead of CNAME.&lt;BR /&gt;&lt;BR /&gt;Happy Xmas for you also!&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Dec 2005 13:01:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696900#M21103</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-12-22T13:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696901#M21104</link>
      <description>I need to understand more what the client wants.&lt;BR /&gt;&lt;BR /&gt;Yes 'multiple-cnames' is no longer an option - but what are they trying to do with cnames?&lt;BR /&gt;&lt;BR /&gt;Are they trying to point say blue to the a records of hosta and hostb?&lt;BR /&gt;&lt;BR /&gt;Are they trying "poor mans" round robin?&lt;BR /&gt;&lt;BR /&gt;You can create an A record for blue twice - pointing to the ip address of hosta and hostb.&lt;BR /&gt;&lt;BR /&gt;Not a good thing to do really:&lt;BR /&gt;&lt;BR /&gt;By being A records - there is no true round robin - only hit and missâ ¦..&lt;BR /&gt;&lt;BR /&gt;Example - if say hosta is downâ ¦and a server does a ping to blue - there is a 50% chance that it will resolve to hosta - and if it does - it will fail - 100% packet loss...&lt;BR /&gt;&lt;BR /&gt;The correct way to do round robin for example email - is to create MX recordsâ ¦&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;blue.cliendomain.net.   3600    IN      MX      10 hosta.cliendomain.net.&lt;BR /&gt;smtpcal1.pcacorp.net.   3600    IN      MX      10 hostb.cliendomain.net.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Dec 2005 16:47:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696901#M21104</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-22T16:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696902#M21105</link>
      <description>Hi Geoff!&lt;BR /&gt;&lt;BR /&gt;    First, thanks for your answer. But can you explain how you can do round-robin with your MX example?&lt;BR /&gt;&lt;BR /&gt;    I agree with you that it can fail if we set this configuration: &lt;BR /&gt;&lt;BR /&gt;Replace faulty configuration using multiple-cnames:&lt;BR /&gt;foo1.bar.baz.   60   IN   A   192.168.1.1&lt;BR /&gt;foo2.bar.baz.   60   IN   A   192.168.1.2&lt;BR /&gt;foo3.bar.baz.   60   IN   A   192.168.1.3&lt;BR /&gt;foo.bar.baz.    60   IN   CNAME  foo1.bar.baz.&lt;BR /&gt;foo.bar.baz.    60   IN   CNAME   foo2.bar.baz.&lt;BR /&gt;foo.bar.baz.    60   IN   CNAME   foo3.bar.baz.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;by that one:&lt;BR /&gt;&lt;BR /&gt;foo1.bar.baz.   60   IN   A   192.168.1.1&lt;BR /&gt;foo2.bar.baz.   60   IN   A   192.168.1.2&lt;BR /&gt;foo3.bar.baz.   60   IN   A   192.168.1.3&lt;BR /&gt;foo.bar.baz.    60   IN   A   192.168.1.1&lt;BR /&gt;foo.bar.baz.    60   IN   A   192.168.1.2&lt;BR /&gt;foo.bar.baz.    60   IN   A   192.168.1.3&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I think true round-robin will occur. Maybe it is better to set the TTL to 0 (no caching)?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;\Viseth&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Dec 2005 03:59:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696902#M21105</guid>
      <dc:creator>viseth</dc:creator>
      <dc:date>2005-12-23T03:59:24Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696903#M21106</link>
      <description>Sure - by setting the MX value the same on both servers (10 in my case) - when another server wants to send me mail - it looks up the MX record - chooses the lowest route - in this case - both are the same - so it just picks one - and sends the email.&lt;BR /&gt;&lt;BR /&gt;Benefit is - if hosta is busy (or down) then the mail goes directly to hostb.&lt;BR /&gt;&lt;BR /&gt;How to add with nsupdate:&lt;BR /&gt;&lt;BR /&gt;# nsupdate&lt;BR /&gt;&amp;gt; update add blue.cliendomain.net. 3600 IN MX 10 hosta.cliendomain.net.&lt;BR /&gt;&amp;gt; update add blue.cliendomain.net. 3600 IN MX 10 hostb.cliendomain.net.&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;Even with a TTL of 0 in your last post - you still risk if hosta is down or doesn't respond - it will not go to hostb...&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Fri, 23 Dec 2005 08:57:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696903#M21106</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-23T08:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696904#M21107</link>
      <description>Remember that nsupdate is only for Dynamic DNS.&lt;BR /&gt;&lt;BR /&gt;Now, what do you really want to do? You can get a better load balancing system by using LVS.</description>
      <pubDate>Fri, 23 Dec 2005 09:13:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696904#M21107</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-12-23T09:13:15Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696905#M21108</link>
      <description>Hello Everyone!&lt;BR /&gt;   Happy new year 2006! May the success be round the corner! Hope that everyone has spent a good time at Xmas'eve and new year's eve!&lt;BR /&gt;&lt;BR /&gt;   Well, back to work! Does someone kown about a workaround of the DNS option 'multiple-cnames'. My customer is using that option to avoid DNS reply in round-robin fashion. By using multiple CNAMES, the answer sent from the DNS server is the same during the TTL time attached to the CNAME records thus no real round-robin, if you see what I mean.&lt;BR /&gt;&lt;BR /&gt;   Many thanks for your reply!&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;&lt;BR /&gt;\Viseth&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Jan 2006 09:01:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696905#M21108</guid>
      <dc:creator>viseth</dc:creator>
      <dc:date>2006-01-02T09:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a workaround to the DNS option 'multiple-cnames'?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696906#M21109</link>
      <description>Bind will rotate the order on each request.&lt;BR /&gt;Try querying one of the authorative servers.&lt;BR /&gt;Downstream servers may not rotate the IP&lt;BR /&gt;address.  &lt;BR /&gt;Bind9 allows you to sey cyclic or random&lt;BR /&gt;ordering. &lt;BR /&gt;Non-rotation is likely a problem with one or&lt;BR /&gt;more intermediate DNS servers.</description>
      <pubDate>Wed, 04 Jan 2006 12:28:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/is-there-a-workaround-to-the-dns-option-multiple-cnames/m-p/3696906#M21109</guid>
      <dc:creator>Bill Thorsteinson</dc:creator>
      <dc:date>2006-01-04T12:28:13Z</dc:date>
    </item>
  </channel>
</rss>

