How to configure a reverse zone as forwarder type?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How to configure a reverse zone as forwarder type?
Hi All,
I have configured a linux DNS server. All the forward and reverse name resolutions seems to work fine. The forwarders are also mentioned for machines in remote locations and the forward configuration works fine there as well.... Can any of you please let me know if i can create a seperate reverse zone for the ip addresses in remote locations and then make it to forward the requests to the remote dns server? My named.conf file is attached below:-
//
// named.conf for Red Hat caching-nameserver
//
options {
directory "/var/named";
forwarders {10.171.8.4;10.171.8.5;};
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "srnblr.nsn-rdnet.net" IN {
type master;
file "srnblr.for.db";
allow-update { none; };
};
zone "srnblr.net" IN {
type master;
file "srnblr.db";
};
zone "mnc99.mcc404.gprs" IN {
type master;
file "mnc99.mcc404.gprs.db";
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN {
type master;
file "named.ip6.local";
allow-update { none; };
};
zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};
zone "116.58.10.in-addr.arpa" IN {
type master;
file "srnblr.rev_116.db";
allow-update { none; };
};
zone "4.71.10.in-addr.arpa" IN {
type master;
file "srnblr.rev.db";
allow-update { none; };
};
zone "8.10.in-addr.arpa" {
type slave;
file "slave.10_8";
masters {10.8.195.6; 10.8.195.7; };
};
zone "9.10.in-addr.arpa" {
type slave;
file "slave.10.9";
masters {10.8.195.6; 10.8.195.7; };
};
include "/etc/rndc.key";
In the above file i have configured zones 8.10.in-addr.arpa and 9.10.in-addr.arpa as slaves. Please let me know what changes i have to do if i have to make their type as forwarder?
Can any of you please let me know if i can create a seperate reverse zone for the ip addresses in remote locations and then make it to forward the requests to the remote dns server?
You can do that but why don't you do it on the remote DNS instead. The remote DNS is the one that correlates the number with the name. So why do it twice?
You can do that but why don't you do it on the remote DNS instead. The remote DNS is the one that correlates the number with the name. So why do it twice?
We don't have any access to this remote DNS server. But we want to do reverse name resolutions for the servers which are a part of that remote DNS server. We already have forward name resolution working fine between these two servers. What can be done for the same. Please let me know if you need any further information.
I think in order for that to work you'll have to become the SOA for that remote domain by creating a new zone for that remote domain in your DNS servers. Only your internal clients will be able to query that remote domain using your default DNS servers. Then you can also create a reverse zone for the ip addresses that pertain to that remote domain and point the addresses to whatever remote name you need. However, only the clients in your network, which use your DNS servers resolve these changes.
I think in order for that to work you'll have to become the SOA for that remote domain by creating a new zone for that remote domain in your DNS servers. Only your internal clients will be able to query that remote domain using your default DNS servers. Then you can also create a reverse zone for the ip addresses that pertain to that remote domain and point the addresses to whatever remote name you need. However, only the clients in your network, which use your DNS servers resolve these changes.
Will this need any configuration to be done on the remote server? Please share me some examples if you have..
sharu99 all DNS does is resolve ip numbers to names. Humans have a very difficult time remembering numbers so that is why DNS was invented. For example, what is easier for you to remember 69.147.76.15 or yahoo.com?
Explain to me which ip numbers do you want to resolv with which name?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.