Open Stack

On 10/05/2016 20:48, Chris Friesen wrote:
> On 05/10/2016 12:10 PM, Hayes, Graham wrote:
>
>> The way this component works makes it quite difficult to make any major
>> improvement.
>>
>> MiniDNS (the component) takes data and sends a zone transfer every time
>> a recordset gets updated. That is a full (AXFR) zone transfer, so every
>> record in the zone gets sent to each of the DNS servers that end users
>> can hit.
>>
>> This can be quite a large number - ns[1-6].example.com. may well be
>> tens or hundreds of servers behind anycast IPs and load balancers.
>>
>> In many cases, internal zones (or even external zones) can be quite
>> large - I have seen zones that are 200-300Mb. If a zone is high traffic
>> (like say cloud.example.com. where a record is added / removed for
>> each boot / destroy, or the reverse DNS zones for a cloud), there can
>> be a lot of data sent out from this component.
>>
>> We are a small development team, and after looking at our options, and
>> judging the amount of developer hours we had available, a different
>> language was the route we decided on. I was going to go implement a few
>> POCs and see what was most suitable.
>
>
> I know nothing about what you're doing beyond what you've mentioned above, but
> it seems really odd to transmit all that data any time something changes.
>
> Is there no way to send an incremental change?

In short, yes there is a DNS standard for a incremental change, but it
is quite complex to implement, and can often end up reverting to a full 
zone transfer when there is problems.

We have discussed IXFR (incremental zone transfers) previously but we
have not found a good solution to it.

> Chris
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>