В Sun, 02 Jun 2013 00:25:55 +0200 lynn <lynn@steve-ss.com> пишет:
On Sat, 2013-06-01 at 12:49 +0400, Andrey Borzenkov wrote:
В Sat, 01 Jun 2013 10:42:37 +0200 lynn <lynn@steve-ss.com> пишет:
12.3 bind with the BIND9_DLZ plugin Quick question, if there are any bind gurus around. What reverse zone should I add for a 192.168.x.y address? I've added: 168.192.in-addr.arpa to hold the PTR's but nada. . .
According to your example
x.192.168.in-addr.arpa
and "y" should be PTR record in this zone.
Hi In my example, that would make the PTR 22 yes? So the zone to add is: 1.192.168.in-addr.arpa? In that case, nsupdate would be sending from 168.192.1.22 ????
Sorry, this should of course have been x.168.192.in-addr.arpa and PTR 22 in zone 1.168.192.in-addr.arpa Zones are reverse representation of dotted IP address.
Anyway, still no go. . . What I can't understand is why named can't just store the reverse record in what I already have: 168.192.in-addr.arpa
When making reverse address resolution of 192.168.1.22, program just asks for PTR record for 22.1.168.192.in-addr.arpa. This means record 22 in zone 1.168.192.in-addr.arpa by definition.
Thanks, L x
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org