Forward First on Master Zone (bypass SOA)

[Ben-Eliezer, Tal (ITS)]

Hi Chris, this looks interesting, I'll do some testing and report back!

Thank you,
Tal

-----Original Message-----
From: Chris Buxton [mailto:clists at buxtonfamily.us] 
Sent: Thursday, March 28, 2013 5:02 PM
To: Ben-Eliezer, Tal (ITS)
Cc: bind-users at lists.isc.org
Subject: Re: Forward First on Master Zone (bypass SOA)

On Mar 28, 2013, at 12:28 PM, Ben-Eliezer, Tal (ITS) wrote:

> I've spent hours researching a way to accomplish this without any luck. Is there any way to accomplish what I'm trying to do?

No, not unless you want to monkey around with static zones and $INCLUDE directives -- something like this:

Internal zone file:

$INCLUDE internal.zone.apex
$INCLUDE example.com.common-records
$TTL 86400
some.internal.host	A	192.0.2.1
[...]

External zone file:

$INCLUDE external.zone.apex
$INCLUDE example.com.common-records
$TTL 86400
some.external.host	A	192.0.2.254
[...]

where the *.zone.apex files look something like this:

$TTL 86400
@	SOA	[... 7 data fields ...]
	NS	ns1.example.com.
	NS	ns2.example.com.
	MX	10 mx1.example.com.

This way, you mostly maintain 3 files of DNS records for the zone -- external, internal, and common. Note that this is not compatible with dynamic zones.

If you need to support dynamic zones (and who doesn't, these days?), you're out of luck.

Chris Buxton
BlueCat Networks