bind9 : reverse lookup and PTR value

[bcostacurta]

Hello,
I have the following bind9 configuration, and I'm trying to resolve reverse lookup IP address to name.

$ttl 38400
mydomain.org. IN SOA myhosting.com. (
1243281304
10800
3600
604800
38400 )
mydomain.org. IN NS xxx.myhosting.com.
mydomain.org. IN A 1.2.3.4
mail.mydomain.org. IN MX 10 mail.mydomain.org.
www IN CNAME mydomain.org.
ftp IN CNAME mydomain.org.
1.2.3.4 IN PTR mydomain.org.


I had the PTR value for reverse lookup

nslookup - localhost

> 1.2.3.4
Server: localhost
Address: 127.0.0.1#53

** server can't find 1.2.3.4.in-addr.arpa: NXDOMAIN

Is my PTR wrong, or what do I need to have the reverse lookup working ?

Note: I replace real IP by 1.2.3.4, same for my domain name.

Bye,
Bruno

[Lazydog]

** server can't find 1.2.3.4.in-addr.arpa: NXDOMAIN

You nee to create a reverse zone and place your reverse lookup in there.

[bcostacurta]

I created the reverse zone. Now it works but for the master only.

nslookup - localhost
> 1.2.3.4
Server: localhost
Address: 127.0.0.1#53

4.3.2.1.in-addr.arpa name = costacurta.org.

But now to notify the slave server ?
I tried the following but it doesn't seems to work :

zone "3.2.1.in-addr.arpa" IN {
type master;
file "/etc/bind/rev.3.2.1.in-addr.arpa";
also-notify {
1.2.3.99;
};
notify yes;
};

I used same syntax for the non-reverse and it works fine.
May the syntax be different for reverse-zone ?
Or other reason like serial value, or delays for slave to being updated ?
I have no access to the slave DNS hosted by my provider.

Thanks for your experience and clarification.

Bye,
Bruno

[Lazydog]

Who is hosting your slave server? If it's your ISP then they most likely already have a reverse zone for the address in question. I would contact them and ask if they do. If they do not you could then ask them why you cannot push your reverse zone to them.

[bcostacurta]

Hummm...indeed this might be the reason.
I contacted my ISP and wait for his feedback about this reverse lookup problem.

Bye,
Bruno