Results 1 to 3 of 3

Thread: Problem with named reverse forwarding zone

Hybrid View

  1. #1

    Problem with named reverse forwarding zone

    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. #2

    Re: Problem with named reverse forwarding zone

    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:

    - Visit http://www.suse.com/support and search the knowledgebase and/or check all
    the other support options available.
    - Open a service request: https://www.suse.com/support
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.suse.com)

    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. Re: Problem with named reverse forwarding zone

    Hi Lennart,

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

    Quote Originally Posted by lelle View Post
    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
    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
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •