I configured master and slave dns server. but slave zone file not transferred.

This is my zone file

zone "iftibd.com" IN {
type slave;
file "slaves/seobd.fz";
masters { 52.37.252.202;};
};

zone "228.34.52.in-addr.arpa" IN {
type slave;
file "slaves/seobd.rz";
masters { 52.37.252.202;};
};

In /var/named/slaves file created but no zone is created.

kindly help

You have been here for FIVE YEARS now...read the "Question Guidelines" link about providing details when asking a question. You don't tell us ANYTHING that you've looked at so far, give any info from log files, tell us how you've configured this, or give any hints. What do you think anyone will be able to tell you??? You posted one piece of one config file (and did not use CODE tags doing it), and told us nothing else.

Also, you say you're using RHEL 7, have you contacted Red Hat support for help??? You are PAYING FOR RHEL, RIGHT???? As such, this problem has been covered on their knowledgebase, with a verified solution:
https://access.redhat.com/solutions/59753

1 members found this post helpful.

I am using amazon free tier with RHEL 7.
In slave server, /etc/named.conf file:

options {
listen-on port 53 { 127.0.0.1; 52.34.228.106; 0.0.0.0/0; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
allow-query { localhost; 0.0.0.0/0; };
/*
- If you are building an AUTHORITATIVE DNS server, do NOT enable recurs ion.
- If you are building a RECURSIVE (caching) DNS server, you need to ena ble
recursion.
- If your recursive DNS server has a public IP address, you MUST enable access
control to limit queries to your legitimate users. Failing to do so w ill
cause your server to become part of large scale DNS amplification
attacks. Implementing BCP38 within your network would greatly
reduce such attack surface
*/
#options{
recursion yes;
# allow-recursion { trusted;};
#};

dnssec-enable yes;
dnssec-validation yes;

/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";

managed-keys-directory "/var/named/dynamic";

pid-file "/run/named/named.pid";
session-keyfile "/run/named/session.key";
};

logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};

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

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";


and /etc/rfc1912.zones file:


zone "iftibd.com" IN {
type slave;
file "slaves/seobd.fz";
masters { 52.37.252.202;};
allow-notify {52.37.252.202; };
};

zone "228.34.52.in-addr.arpa" IN {
type slave;
file "slaves/seobd.rz";
masters { 52.37.252.202;};
allow-notify {52.37.252.202;};
};

[root@ip-172-31-17-202 slaves]# nslookup iftibd.com
Server: 52.34.228.106
Address: 52.34.228.106#53

Name: iftibd.com
Address: 52.37.252.202
Name: iftibd.com
Address: 52.34.228.106

[root@ip-172-31-17-202 slaves]# nslookup 52.34.228.106
Server: 52.34.228.106
Address: 52.34.228.106#53

** server can't find 106.228.34.52.in-addr.arpa: SERVFAIL

I found only seobd.fz created but not created reverse zone.

AGAIN, you need to use CODE TAGS, as you were asked before...and again, after FIVE YEARS here, this shouldn't be a surprise. And re-stating the problem still tells us nothing...you have not answered any of the questions asked of you in the first reply, and ignored the request to use CODE tags.

AGAIN, have you done any research on this? What guides did you follow to set this up? What's in the logs? What have you done/tried on your own???