dhcpd.conf ddns config question

[Alex Sharaz]

Chaps,
I've just started looking at configuring ddns here and while I've got
things working o.k. for a Class C address space , I'm having a wee
problem when it comes to networks with netmasks <24 bits.

1). This works just fine where I'm specifying a /24 net. The
corresponding named.conf entries are shown below 

--dhcpd.conf

subnet 150.237.74.0 netmask 255.255.255.0 {
option broadcast-address 150.237.74.255;
option routers 150.237.74.1;
option domain-name-servers  150.237.47.200,150.237.128.27;
default-lease-time 604800;
max-lease-time 2592000;
ignore client-updates;
ddns-updates on;
ddns-domainname "testnet.hull.ac.uk.";
ddns-rev-domainname "in-addr.arpa.";
option domain-name "testnet.hull.ac.uk";
ddns-hostname = concat ("dhcp-", binary-to-ascii (10, 8, "-",
leased-address));
option host-name = config-option server.ddns-hostname;
zone testnet.hull.ac.uk { primary 127.0.0.1; key "isc-dhcp-omapi"; }
zone 74.237.150.in-addr.arpa { primary 127.0.0.1; key "isc-dhcp-omapi";
}
allow unknown-clients;
range dynamic-bootp 150.237.74.10 150.237.74.20;
}

--named.conf

zone "testnet.hull.ac.uk" {
        type master;
        file "zone.testnet";
        allow-update {
        ourhome;
        };
};

zone "74.237.150.IN-ADDR.ARPA" {
        type master;
        file "zone.74";
        allow-update {
        ourhome;
        };
};
2). 

We are about to roll out a wireless network which will use 8 class C
nets in a contiguous block

The host address range is 150.237.216.1 - 150.237.223.254
Broadcast address is 150.237.223.255 
Name.conf has

zone "wireless.hull.ac.uk" {
        type master;
        file "zone.wireless";
        allow-update {
        ourhome;
        };
};

And 
zone "0/21.216.237.150.IN-ADDR.ARPA" {
        type master;
        file "zone.216";
        allow-update {
        ourhome;
        };
};

For the reverse zone. Running named-checkconf doesn't flag any errors at
this point.

The prog I've written that generates our dhcpd.conf file therefore
generates the following dhcpd.conf snippet for this subnet

subnet 150.237.216.0 netmask 255.255.248.0 {
option broadcast-address 150.237.223.255;
option routers 150.237.216.1;
option domain-name-servers  150.237.47.200,150.237.128.27;
default-lease-time 604800;
max-lease-time 2592000;
ignore client-updates;
ddns-updates on;
ddns-domainname "wireless.hull.ac.uk.";
ddns-rev-domainname "in-addr.arpa.";
option domain-name "wireless.hull.ac.uk.";
ddns-hostname = concat ("dhcp-", binary-to-ascii (10, 8, "-",
leased-address));
option host-name = config-option server.ddns-hostname;
zone wireless.hull.ac.uk. { primary 127.0.0.1; key "isc-dhcp-omapi"; }
zone 0/21.216.237.150.in-addr.arpa. { primary 127.0.0.1; key
"isc-dhcp-omapi"; }
allow unknown-clients;
range dynamic-bootp 150.237.216.2 150.237.223.100;
}

.... which causes the dhcpd to fail because of the zone 0/21.... entry


Commenting out the offending line causes our wireless users (me) to get
a forwardly (?)  generated dns entry

Suppose the question is how do I "escape" the "/" character in the zone
statement to get dhcpd to treat 0/21.216.237.150.in-addr.arpa as a valid

Zone name

Alex