Dear All,
i have the following setup
CentOS 5 server running as a primary DNS server for a long time and is working perfectly fine
the server is on public IP and we have abt 5 zones apart from the reverse n local zone
now our sister company have recently setup their own DNS and we are supposed to use it. earlier our cleints were using a host file
now on my master dns server in /etc/named.conf i created a new zone with the following statement
zone "cse.net.kw" IN { type slave; masters { 172.31.1.240; }; file "cse.db"; allow-query { any; }; // the default allow-transfer { none; }; };
and when i reload the dns server the file cse.db is not created also in /var/log/messages i c the following
Jun 24 18:17:41 kmdns1 named[1771]: loading configuration from '/etc/named.conf' Jun 24 18:17:41 kmdns1 named[1771]: zone cse.net.kw/IN: refresh: non-authoritative answer from master 172.31.1.240#53 (source 0.0.0.0#0)
actually i would want all the cleints to query the 172.31.1.240 DNS server without adding this IP in their configurtion . all the cleint hav our master dns server in their own setup
so actually query 172.31.1.240 DNS server through our DNS
apprecite your help
or cd i have contitional forwarding something like when a client queries the 172.31.1.240 our master DNS jus forwards the queries to 172.31.1.240 instead of sending it out on the internet since 172.31.1.0 network is connected directly and is a part of out intranet
really wd apprecite your help and ideas with examples
regards
fabian
fabian dacunha wrote:
really wd apprecite your help and ideas with examples
add this to your bind options section
forwarders { 172.31.1.240; };
and restart named, your named will now forward all requests that it's not authoritative for to the above system.
nate
Dear Nate
Thnks a million really apprecite for ur immediate reply actually i was little confused
i had used the forwarder statment but it was at the start of the named.conf section and the when i reloaded named it was giving me error saying the statemnt not valid so then i created a zone and included the the forwader statement in the zone i created but was not workin and also i had created a slave zone for 172.1.1.240 but also it didnt work but moment i added forwarder statement in bind options section it worked beautifullly
i jus didnt try putting the forwarders in the right place
thnks a million
regards
fabian
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
fabian dacunha wrote:
Dear All,
i have the following setup
CentOS 5 server running as a primary DNS server for a long time and is working perfectly fine
the server is on public IP and we have abt 5 zones apart from the reverse n local zone
now our sister company have recently setup their own DNS and we are supposed to use it. earlier our cleints were using a host file
now on my master dns server in /etc/named.conf i created a new zone with the following statement
zone "cse.net.kw" IN { type slave; masters { 172.31.1.240; }; file "cse.db"; allow-query { any; }; // the default allow-transfer { none; }; };
and when i reload the dns server the file cse.db is not created also in /var/log/messages i c the following
Jun 24 18:17:41 kmdns1 named[1771]: loading configuration from '/etc/named.conf' Jun 24 18:17:41 kmdns1 named[1771]: zone cse.net.kw/IN: refresh: non-authoritative answer from master 172.31.1.240#53 (source 0.0.0.0#0)
actually i would want all the cleints to query the 172.31.1.240 DNS server without adding this IP in their configurtion . all the cleint hav our master dns server in their own setup
so actually query 172.31.1.240 DNS server through our DNS
apprecite your help
or cd i have contitional forwarding something like when a client queries the 172.31.1.240 our master DNS jus forwards the queries to 172.31.1.240 instead of sending it out on the internet since 172.31.1.0 network is connected directly and is a part of out intranet
really wd apprecite your help and ideas with examples
Well ... having you as a secondary server and having them setup a "notify" that will point to your server will allow your users to get updates and not have to look at that their server at all.
Your server could also then be a backup to their server and provide info if it dies ... until it comes back up.
-
fabian dacunha -
Johnny Hughes -
nate