in-addr.arpa subdomain problem
lancer81 at cablespeed.com
lancer81 at cablespeed.com
Thu Aug 5 15:52:46 UTC 2004
Using that syntax I receive a different error. I have
included configuration for class C that does work. When
moving from 8.1.2 to 9.2.1 I had to change format in
named.conf from 128/25... to 128-255... in order to get
named to start so I assumed syntax was correct.
-----------
[user at ns1]# dig @ns1 PTR 129.12.12.12.in-addr.arpa
; <<>> DiG 9.2.1 <<>> @ns1 PTR 129.12.12.12.in-addr.arpa
;; global options: printcmd
;; connection timed out; no servers could be reached
----------
zone "13.13.13.in-addr.arpa" in {
type master;
file "13.13.13.reverse.db";
allow-update { none; };
};
----------
;13.13.13.reverse.db
;
$TTL 3h
@ IN SOA ns1.domain.com. hostmaster.domain.com. (
2004080401 ; serial
3h ; refresh
1h ; retry
15d ; expire
1h ) ; neg cache ttl
@ IN NS ns1.domain.com.
@ IN NS ns2.domain.com.
13 IN PTR ns1.domain.com.
14 IN PTR ns1.domain.com.
----------
[user at ns1]# dig @ns1 PTR 13.13.13.13.in-addr.arpa
; <<>> DiG 9.2.1 <<>> @ns1 PTR 13.13.13.13.in-addr.arpa
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56262
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2,
ADDITIONAL: 2
;; QUESTION SECTION:
;13.13.13.13.in-addr.arpa. IN PTR
;; ANSWER SECTION:
13.13.13.13.in-addr.arpa. 10800 IN PTR
ns1.domain.com.
;; AUTHORITY SECTION:
13.13.13.in-addr.arpa. 10800 IN NS
ns2.domain.com.
13.13.13.in-addr.arpa. 10800 IN NS
ns1.domain.com.
;; ADDITIONAL SECTION:
ns1.domain.com. 10800 IN A 13.13.13.13
ns2.domain.com. 10800 IN A 13.13.13.14
;; Query time: 1 msec
;; SERVER: 13.13.13.13#53(ns1)
;; WHEN: Thu Aug 5 11:45:39 2004
;; MSG SIZE rcvd: 148
----------
On Thu, 5 Aug 2004 17:31:41 +0200
"Jens Rosenthal" <mailings at edv-rosenthal.de> wrote:
>Hi,
>
>First of all your dig syntax isn't correct...
>
>Your query should look like:
>
>dig @ns1 PTR 129.12.12.12.in-addr.arpa
>
>If this fails, then there might also be something wrong
>with your config,
>but since your dig does a forward query you'll certainly
>get no reverse
>answer...
>
>Greetings from munich,
>
>Jens
>
>
>
>-----Original Message-----
>From: bind-users-bounce at isc.org
>[mailto:bind-users-bounce at isc.org] On Behalf
>Of lancer81 at cablespeed.com
>Sent: Thursday, August 05, 2004 5:13 PM
>To: bind-users at isc.org
>Subject: in-addr.arpa subdomain problem
>
>I am setting up a new server running bind 9.2.1 to
>replace
>a bind 8.1.2 server. In testing this I am able to do
>reverse lookups on class C subnets but not subdomains
>(e.g. /25). If I am reading dig output properly the
>server
>is directing request to root servers rather than handling
>it locally.
>
>------------
>
>zone "128-255.12.12.12.in-addr.arpa" in {
> type master;
> file "12.12.12.128.reverse.db";
> allow-update { none; };
>};
>
>------------
>
>;12.12.12.128.reverse.db
>;
>$TTL 3h
>@ IN SOA ns1.domain.com. hostmaster.domain.com. (
> 2004080501 ; serial
> 3h ; refresh
> 1h ; retry
> 15d ; expire
> 1h ) ; neg cache ttl
>
>@ IN NS ns1.domain.com.
>@ IN NS ns2.domain.com.
>
>129 IN PTR host1.domain.com.
>130 IN PTR host2.domain.com.
>
>------------
>
>[user at ns1]# dig @ns1 12.12.12.129
>
>; <<>> DiG 9.2.1 <<>> @ns1 12.12.12.129
>;; global options: printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id:
>29600
>;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
>ADDITIONAL: 0
>
>;; QUESTION SECTION:
>;12.12.12.129. IN A
>
>;; AUTHORITY SECTION:
>. 10800 IN SOA
> A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM.
>2004080401
>1800 900 604800 86400
>
>;; Query time: 16 msec
>;; SERVER: 13.13.13.13#53(ns1)
>;; WHEN: Thu Aug 5 10:51:12 2004
>;; MSG SIZE rcvd: 106
>
>
>
More information about the bind-users
mailing list