<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
I'm encountering a very strange behavior with our dns server since we
moved to an other data center with <b>reverse request only.</b><br>
<br>
Before, we had authority on a subnet xxx.yyy.zzz.0/24 but now our
authority is only for the network 94.103.140.0/28... our provider has
updated its upstream to delegate this subnet and the translation is
working fine (x.140.103.94.in-addr.arpa translate to
x.0-28.140.103.94.in-addr.arpa) and I think I've made the good changes
on our DNS server but our dns is responding "no answer" when trying to
dig an existing entry and "nxdomain" when there is no entry (which is
correct)...<br>
<br>
<i><b>zone definition :</b></i><br>
<small>zone "0-28.140.103.94.in-addr.arpa" {<br>
type master;<br>
allow-query { any; };<br>
allow-transfer { xxxxxxxxxxxxxxxxxxxxxxx }; <br>
file "/etc/bind/zones/reverse.conf";<br>
};<br>
<br>
</small><i><b>/etc/bind/zones/reverse.conf :</b></i><br>
<small>$ORIGIN .<br>
$TTL 86400<br>
0-28.140.103.94.in-addr.arpa IN SOA
ns1.fimasys.com. support.fimasys.com. (<br>
2009011503<br>
86400<br>
3600<br>
604800<br>
86400<br>
)<br>
$ORIGIN 0-28.140.103.94.in-addr.arpa.<br>
@ IN NS ns1.fimasys.com.<br>
@ IN NS ns2.fimasys.com.<br>
@ IN NS ns3.fimasys.com.<br>
@ IN NS ns4.fimasys.com.<br>
4 IN PTR athena.fimasys.com.</small><br>
[there is other entries of course, but athena is the ns1 and
94.103.140.6 has no PTR record]<br>
<br>
<i><b>Dig result with our provider dns :</b></i><br>
<small>dig 4.140.103.94.in-addr.arpa. @ns1.mit-datacenter.net<br>
<br>
; <<>> DiG 9.3.4-P1.1 <<>>
4.140.103.94.in-addr.arpa. @ns1.mit-datacenter.net<br>
; (1 server found)<br>
;; global options: printcmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35202<br>
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2<br>
<br>
;; QUESTION SECTION:<br>
;4.140.103.94.in-addr.arpa. IN A<br>
<br>
;; ANSWER SECTION:<br>
4.140.103.94.in-addr.arpa. 86400 IN CNAME
4.0-28.140.103.94.in-addr.arpa.<br>
<br>
;; AUTHORITY SECTION:<br>
140.103.94.in-addr.arpa. 259200 IN NS ns1.mit-datacenter.net.<br>
140.103.94.in-addr.arpa. 259200 IN NS ns2.mit-datacenter.net.<br>
<br>
;; ADDITIONAL SECTION:<br>
ns1.mit-datacenter.net. 3600 IN A 94.103.128.65<br>
ns2.mit-datacenter.net. 3600 IN A 88.191.203.15<br>
<br>
;; Query time: 24 msec<br>
;; SERVER: 94.103.128.65#53(94.103.128.65)<br>
;; WHEN: Fri Jan 16 12:11:25 2009<br>
;; MSG SIZE rcvd: 150<br>
</small><br>
<i><b>Dig result with our DNS on an existing entry :</b></i><br>
<small>dig 4.0-28.140.103.94.in-addr.arpa. @ns1.fimasys.com<br>
<br>
; <<>> DiG 9.3.4-P1.1 <<>>
4.0-28.140.103.94.in-addr.arpa. @ns1.fimasys.com<br>
; (1 server found)<br>
;; global options: printcmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34891<br>
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0<br>
<br>
;; QUESTION SECTION:<br>
;4.0-28.140.103.94.in-addr.arpa. IN A<br>
<br>
;; AUTHORITY SECTION:<br>
0-28.140.103.94.in-addr.arpa. 86400 IN SOA ns1.fimasys.com.
support.fimasys.com. 2009011503 86400 3600 604800 86400<br>
<br>
;; Query time: 23 msec<br>
;; SERVER: 94.103.140.4#53(94.103.140.4)<br>
;; WHEN: Fri Jan 16 12:17:33 2009<br>
;; MSG SIZE rcvd: 107<br>
<br>
</small><i><b>Dig result with our DNS on an unused entry :</b></i><br>
<small>dig 6.0-28.140.103.94.in-addr.arpa. @ns1.fimasys.com<br>
<br>
; <<>> DiG 9.3.4-P1.1 <<>>
6.0-28.140.103.94.in-addr.arpa. @ns1.fimasys.com<br>
; (1 server found)<br>
;; global options: printcmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27692<br>
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0<br>
<br>
;; QUESTION SECTION:<br>
;6.0-28.140.103.94.in-addr.arpa. IN A<br>
<br>
;; AUTHORITY SECTION:<br>
0-28.140.103.94.in-addr.arpa. 86400 IN SOA ns1.fimasys.com.
support.fimasys.com. 2009011503 86400 3600 604800 86400<br>
<br>
;; Query time: 24 msec<br>
;; SERVER: 94.103.140.4#53(94.103.140.4)<br>
;; WHEN: Fri Jan 16 12:25:31 2009<br>
;; MSG SIZE rcvd: 107</small><br>
<br>
All other zones are working just fine... only the reverse is wrong. The
version of bind is 9.2.4, running on debian.<br>
<br>
Regards,<br>
Jeremie Grauer<br>
Sysadmin<br>
</body>
</html>