[Pdns-users] Using BIND Backend and '@'

[Roy S. Rapoport]

Platform is RHEL 4; PDNS is 2.9.19.

I'm trying to use pdns currently to serve some enum zones internally for
testing.  This is my first exposure to it, and while I did read through the
manual (not thoroughly, I have to admit), and searched for the answer, I
seem to be missing it -- I'd appreciate a specific RTFM for this.

My pdns.conf has:
---
launch=bind
bind-example-zones
bind-config=/u3/rsr-tests/named.conf
---

(as an unrelated issue, I can't query for www.example.com, even though the
manual suggests I should be able to, given my use of bind-example-zones
above).  

the named.conf simply has a bunch of:
---
zone "1.0.0.0.0.0.1.e164.arpa." {
    type master;
    file "/u3/rsr-tests/1M-1N.init/zonefile";
};

zone "2.0.0.0.0.0.1.e164.arpa." {
    type master;
    file "/u3/rsr-tests/1M-1N.init/zonefile";
};

zone "3.0.0.0.0.0.1.e164.arpa." {
    type master;
    file "/u3/rsr-tests/1M-1N.init/zonefile";
};

---

As you can see, the zonefile for each of these zones is exactly the same;
its content is
---
@ SOA localhost. root.localhost. (5 10800 1800 604800 1800);
@ NS  localhost.
0.0.0.1 NAPTR 10 100 "u" "E2U+npd:tel" "!^.*$!tel:+1-416-358-7883;rn=+1-347-548-5551;npdi!" .
---

Now, this works with BIND w/o a problem, because BIND substitutes the zone
name for '@'.  When starting pdns in monitor mode, however, I get:
---
Nov 26 02:35:24 [bindbackend] error at Sat Nov 26 02:35:24 2005 parsing '1.0.0.0.0.0.1.e164.arpa' from file '/u3/rsr-tests/1M-1N.init/zonefile': Unable to parse 1.0.0.0.0.0.1.e164.arpa time specification 'NS' at line 1
---

Which suggests to me that pdns looks at '@' quite differently.

I could, I suspect, simply replace the '@' with the zone name, but we
_like_ that we can do this particular thing with only one zone file, so I'd
rather not.

Is there a way to make pdns Do The Bind Thing with '@'? If not, is there
another way I could use one zonefile for many zones, using the BIND
back-end?

-roy