Forward zone not working

MegaBrutal megabrutal at
Mon May 16 21:35:00 UTC 2016

2016-05-16 19:45 GMT+02:00 Alan Clegg <alan at>:
> On 5/16/16, 1:30 PM, "MegaBrutal" <bind-users-bounces at on
> behalf of megabrutal at> wrote:
>>I want to have valid reverse & forward hostnames set up
>>for this /64 subnet.
> This is silly.  Don't do this.


Most ISPs set up reverse & forward domain names for pool addresses.
OK, I'm not an ISP, but it really seems to be a widely accepted and
endorsed policy, to the point that addresses not having a reverse DNS
often treated as suspicious.

2016-05-16 22:50 GMT+02:00 Mark Andrews <marka at>:
> If you want to delegate space to another server DELEGATE it.  Add
> NS records for the other server.  Forward "zones" are NOT designed
> to do this.  Doing actual delegations is *not* hard and works with
> every server in the world.

What is the acceptable use case for forward zones, then?

See, ideally the zone should be served by my BIND server, it should be
authoritative for the zone. Why I can't use it as the authoritative
server for the zone is that BIND does not have a feature that the
other DNS server has (on-the-fly generation of IPv6 reverse & forward
records, without the need to store 2 * 2 ^ 64 records in zone files).

More information about the bind-users mailing list