Problem with named reverse forwarding zone

SUSE Linux Enterprise Server SLES Networking
1

Hi all,

I’m very puzzled by this, I try to set up a zone in bind on Sles12.1 using yast to forward reverse lookup to a other server

I have set up like this in sles 12 named.conf
zone “10.in-addr.arpa” in {
forwarders { 10.1.1.13; 10.1.1.4; };
type forward;
};

the 10.1.1.13 and 10.1.1.4 has the zone 10.in-addr.arpa zone setup

If I do dig @10.1.1.13 -x 10.1.1.4

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;4.1.1.10.in-addr.arpa. IN PTR

;; ANSWER SECTION:
4.1.1.10.in-addr.arpa. 86400 IN PTR server1.domain.

;; AUTHORITY SECTION:
10.in-addr.arpa. 86400 IN NS server1.domain.
10.in-addr.arpa. 86400 IN NS server2.domain.
10.in-addr.arpa. 86400 IN NS server3.domain.
10.in-addr.arpa. 86400 IN NS server4.domainse.

but if I do dig -x 10.1.1.4 I get this back
;; QUESTION SECTION:
;4.1.1.10.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
10.IN-ADDR.ARPA. 86400 IN SOA 10.IN-ADDR.ARPA. . 0 28800 7200 604800 86400

And if I do nslookup 10.1.1.4
I get this back

Server: 127.0.0.1
Address: 127.0.0.1#53

** server can’t find 4.1.1.10.in-addr.arpa: NXDOMAIN

This should be fairly simple but I can’t figure it out

/Lennart

2

lelle,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot…

Good luck!

Your SUSE Forums Team
http://forums.suse.com

3

Hi Lennart,

sorry for the late reply, I somehow missed this question.

[QUOTE=lelle;38325]Hi all,

I’m very puzzled by this, I try to set up a zone in bind on Sles12.1 using yast to forward reverse lookup to a other server

I have set up like this in sles 12 named.conf
zone “10.in-addr.arpa” in {
forwarders { 10.1.1.13; 10.1.1.4; };
type forward;
};

the 10.1.1.13 and 10.1.1.4 has the zone 10.in-addr.arpa zone setup

If I do dig @10.1.1.13 -x 10.1.1.4

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;4.1.1.10.in-addr.arpa. IN PTR

;; ANSWER SECTION:
4.1.1.10.in-addr.arpa. 86400 IN PTR server1.domain.

;; AUTHORITY SECTION:
10.in-addr.arpa. 86400 IN NS server1.domain.
10.in-addr.arpa. 86400 IN NS server2.domain.
10.in-addr.arpa. 86400 IN NS server3.domain.
10.in-addr.arpa. 86400 IN NS server4.domainse.

but if I do dig -x 10.1.1.4 I get this back
;; QUESTION SECTION:
;4.1.1.10.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
10.IN-ADDR.ARPA. 86400 IN SOA 10.IN-ADDR.ARPA. . 0 28800 7200 604800 86400

And if I do nslookup 10.1.1.4
I get this back

Server: 127.0.0.1
Address: 127.0.0.1#53

** server can’t find 4.1.1.10.in-addr.arpa: NXDOMAIN

This should be fairly simple but I can’t figure it out

/Lennart[/QUOTE]

the SOA reply may hint at a different, local zone declaration, making the local named believe that it’s authoritative, though that nslookup NX (“no such domain”) response counters that. What’s in the logs when you start the named process and have you already tried to turn on named debug?

Regards,
Jens