This is a discussion on newbie: question about forwarders within the Bind Users forums, part of the DNS and Related Forums category; /me bows before all bind guru's. I have just started to explore bind and set up a local nameserver ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
/me bows before all bind guru's.
I have just started to explore bind and set up a local nameserver following the directions in the book DNS and BIND, 4th Edition. By Paul Albitz, Cricket Liu . It works.and I am about to explore further. but still I've got this question about forwarders. I put the ip adresses of the 2 nameservers of my isp as forwarders in named.conf but in /var/log/messages I now get the message: Aug 25 18:48:53 ns named[73]: Ready to answer queries. Aug 25 18:48:53 ns named[73]: non-recursive forwarder: [194.109.9.100].53 Aug 25 18:48:53 ns named[73]: non-recursive forwarder: [194.109.6.67].53 I googled this quite a bit but I cant find answers to the following questions: 1) am I wrong in my thinking the nameservers of my isp would make great forwarders?. I think they could answer a lot of my queries from cache? 2) Why on earth would my isp make the nameservers non-recursive? What's the point, whats in it for them? Thanx for helping a newbie.. for config files see below >------------------------------------------------------------------< $ cat named.conf ddesk.nl.db db.192.168.1 db.127.0.0 -> named.conf <- // $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.7 2003/02/13 13:16:51 keramida Exp $ // options { directory "/etc/namedb"; forwarders { 194.109.6.67; 194.109.9.100; }; }; /* logging { channel my_syslog { syslog daemon; severity dynamic; print-category yes; print-severity yes; }; channel my_file { file "log.msgs"; severity dynamic; print-category yes; print-severity yes; }; category default {my_syslog;my_file;}; category statistics {my_syslog;my_file;}; category queries {my_syslog;my_file;}; }; */ zone "ddesk.nl" in { type master; file "ddesk.nl.db"; }; zone "1.168.192.in-addr.arpa" { type master; file "db.192.168.1"; }; zone "0.0.127.in-addr.arpa" in { type master; file "db.127.0.0"; }; zone "." { type hint; file "db.cache"; }; -> ddesk.nl.db <- $TTL 3h ddesk.nl. IN SOA ns.ddesk.nl. hostmaster.domain.com. ( 2004081712 ;serial number 3h ;refresh after 3 hours 1h ;retry after 1 hour 1w ;expire after 1 week 1h ) ;negative caching TTL of 1hour ; ;Nameserver ddesk.nl. IN NS ns.ddesk.nl. ; ;Addresses ns IN A 192.168.1.101 laptop IN A 192.168.1.201 wp2 IN A 192.168.1.202 wp3 IN A 192.168.1.203 -> db.192.168.1 <- $TTL 3h 1.168.192.in-addr.arpa. IN SOA ns.ddesk.nl. hostmaster.ddesk.nl. ( 2004081712 ;serial 3h ;refresh rate (3 hours) 1h ;retry (1 hour) 1w ;expire (1 week) 1h ) ;negative caching TTL (1 hour) ; ; Name server 1.168.192.in-addr.arpa. IN NS ns.ddesk.nl. ; ;Adresses 101 IN PTR ns.ddesk.nl. 201 IN PTR laptop.ddesk.nl. 202 IN PTR wp2.ddesk.nl. 203 IN PTR wp3.ddesk.nl. -> db.127.0.0 <- $TTL 3h 0.0.127.in-addr.arpa. IN SOA ns.ddesk.nl. hostmaster.ddesk.nl. ( 2004081001 ; serial 3h ; refresh after 3 hours 1h ; retry after 1 hour 1w ; expire after 1 week 1h ) ; negative caching TTL of 1 hour 0.0.127.in-addr.arpa. IN NS ns.ddesk.nl. 1.0.0.127.in-addr.arpa. IN PTR localhost. EOF |
![]() |
| Thread Tools | |
| Display Modes | |
|
|