Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Zone transfers - Reverse zone won't transfer, forward is fine

Status
Not open for further replies.

tjobrien21

IS-IT--Management
Dec 10, 2007
2
US
Hello,

I have a pair of DNS servers, one primary and one secondary. The main server resolves names fine, both forward and reverse. The secondary can only do forward, reverse doesn't work. Logs show success on forward zone, reverse shows this:
Code:
Dec 10 13:27:51 exmdnssec named[11623]: zone 26.3.in-addr-arpa/IN: refresh: non-authoritative answer from master 3.26.51.193#53 (source 0.0.0.0#0)
Here are relevant clips from what I believe to be the relevant files. Any assistance would be greatly appreciated - I can't seem to figure this one out. :-/

---------------------------------

Code:
forward zone file "example.com"


; Authoritative Info on example.com

$TTL 1h
example.com. 1D IN SOA exmdnspri admin.mail.example.com. (
        20071217 ; serial
        3600 ; refresh in seconds
        1800 ; retry in seconds
        604800 ; expire in seconds
        3600 ; minimum TTL in seconds
)

                        IN MX           10 einstein
                        IN NS           exmdnspri
                        IN NS           exmdnssec
localhost               IN A            127.0.0.1
exmaccess01             IN A            3.26.48.1
exmaccess02             IN A            3.26.48.2
exmdefaultroute         IN A            3.26.48.3
exampleavenger          IN A            3.26.48.4
examplephantom          IN A            3.26.48.5
examplefalcon           IN A            3.26.48.6
exmpigeon               IN A            3.26.48.7
exmstiletto             IN A            3.26.48.8


Reverse zone file "example-reverse"
Code:
; Authoritative Info on example.com

$TTL 1h
26.3.in-addr.arpa. 1D IN SOA exmdnspri.example.com. admin.mail.example.com. (
        20071217 ; serial
        3600 ; refresh in seconds
        1800 ; retry in seconds
        604800 ; expire in seconds
        3600 ; minimum TTL in seconds
)

                        IN NS           exmdnspri.example.com.
                        IN NS           exmdnssec.example.com.
1.48                    IN PTR          exmaccess01.example.com.
2.48                    IN PTR          exmaccess02.example.com.
3.48                    IN PTR          exmdefaultroute.example.com.
4.48                    IN PTR          exampleavenger.example.com.
5.48                    IN PTR          examplephantom.example.com.
6.48                    IN PTR          examplefalcon.example.com.
7.48                    IN PTR          exmpigeon.example.com.
8.48                    IN PTR          exmstiletto.example.com.

named.conf file on master server

Code:
options {
    directory "/var/named";
    dump-file "/var/named/data/cache_dump.db";
    statistics-file "/var/named/data/named_stats.txt";
    forwarders {
        3.37.24.70 ;
    } ;
    query-source address * port 53 ;

};

zone "." {
        type hint ;
        file "named.ca";
} ;

zone "localhost" {
        type master ;
        file "/var/named/localhost.zone";
} ;

zone "0.0.127.in-addr.arpa" {
        type master ;
        file "/var/named/named.zero" ;
} ;

zone "example.com" IN {
        type master ;
        file "/var/named/example.com" ;
        allow-transfer {any;};
} ;

zone "26.3.in-addr.arpa" IN {
        type master ;
        file "/var/named/example-reverse" ;
        allow-transfer {any;};
} ;


Named.conf on slave server:

Code:
options {
        directory "/var/named" ;
        dump-file "/var/named/data/cache_dump.db" ;
        statistics-file "/var/named/data/named_stats.txt" ;
        forwarders {
                3.37.24.70 ;
        } ;
        query-source address * port 53 ;
} ;

zone "." {
        type hint ;
        file "named.ca" ;
} ;

zone "localhost" {
        type master ;
        file "/var/named/localhost.zone" ;
} ;

zone "0.0.127.in-addr-arpa" {
        type master ;
        file "/var/named/named.zero" ;
} ;

zone "example.com" IN {
        type slave ;
        file "/var/named/example.com" ;
        masters {
        3.26.51.193;
        };
} ;

zone "26.3.in-addr-arpa" IN {
        type slave ;
        file "/var/named/example-reverse" ;
        masters {
        3.26.51.193;
        };
} ;



---------------------


Again, any help would be greatly appreciated!

Tim
 
I suppose it seems silly to answer one's own question on the forum, but the problem has been solved and I'd rather nobody else waste time on it.

Answer: It's a simple typo in named.conf.

in-addr.arpa -vs- in-addr-arpa.

They don't match, so it didn't work.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top