Merging dynamic DNS data with existing authoritative static data

[Kevin Darcy]

Wouldn't it have been better to just hack named-xfer to strip out the
WINS crap, so that the BIND server could be a regular slave to the NT box?

You really need to think about upgrading your BIND; 4.9.x is ancient and
subject to exploits. And isn't Microsoft even steering people away from
WINS these days?


- Kevin
Greg Bailey wrote:

> I'm sure others have faced this problem, but we have BIND 4.9.X on Unix
> serving external DNS data, and WinNT 4.X DNS serving our internal
> network, as it contains DHCP/WINS stuff that the outside doesn't need
> nor want to see.
>
> The problem occurs with the duplication of data for hosts that both the
> outside world and our internal people want access to.  I have a
> work-around for the reverse mapping by using a bunch of NS records for
> each node that points to the internal DNS server.  In that way,
> DHCP-assigned addresses can be resolved.
>
> The problem is with the forward lookups.  An obvious solution would be
> to create a subdomain for the dynamically assigned hosts, but that
> breaks too many things here to be feasible.  Instead, I've created a
> zone file that uses a wildcard with a NS record to the internal name
> server.  This worked until the BIND nameserver tried to store the
> retrieved data in its cache and wouldn't because it doesn't allow
> updates to its authoritative domain.
>
> My "solution" was to hack the db_update.c code to allow the cache update
> to happen, so now I can hold the bulk of the data on the BIND
> nameserver, with only the dynamic data on the WinNT DNS server.  My
> question is:  if this is really a common problem, surely someone's
> figured out how to either:  1) do WINS lookups from a UNIX-based host;
> and/or 2)  use a different configuration than what I've described above.
>
> If anyone's interested in the patch (only a couple of lines), I'd be
> happy to e-mail them.  I'd also welcome any comments on the setup
> described above.
>
> Thanks,
> Greg Bailey
> gbailey at i-link.net