Nssync (split by section):   Section:   Chapter:FastBack: Top   Up: Top   FastForward: Overview   Contents: Table of ContentsIndex: Concept Index

1 Introduction

BIND, the most frequently used DNS server, normally keeps its zone data in zone files. This approach becomes inconvenient when the number of zones grows beyond a certain limit. When this happens, the obvious solution is to move all data to a database and make named read it from there. Recent versions of BIND include dynamically loadable zones (DLZ) feature1, which makes it possible to use such databases directly. However, DLZ has problems of its own, one of them being that it is unable to propagate glue records2.

The nssync utility provides an alternative solution, which makes it possible to keep your zone data in an SQL3 database without using DLZ and with glue records working.

It does so by periodically polling the database to determine which data have changed recently and converting the database into BIND zone files.

Footnotes

(1)

See http://bind-dlz.sourceforge.net/.

(2)

See: http://permalink.gmane.org/gmane.network.dns.bind9.dlz/2078, http://blog.gmane.org/gmane.network.dns.bind9.dlz/month=20110101.

(3)

As of version 1.1.91 only MySQL is supported.

Nssync (split by section):   Section:   Chapter:FastBack: Top   Up: Top   FastForward: Overview   Contents: Table of ContentsIndex: Concept Index