bind 8.3.3 and forwarding

Mark Benschop m.j.p.benschop at tpgpost.nl
Mon Mar 29 16:19:24 UTC 2004


Hi !

I have to phase out 3 of my 5 secondairy 8.3.3 bind servers in a closed 
(not internet connected) network.
Since I have no complete control over the configuration of the clients 
it is still possible that some machines will try to resolve stuff on the 
   "phased out" machines, I thought it would be a good idea to make make 
the old boxes forwarders to my primary/new secondairies and log the 
queries that are done to them in order to determine who is still using them.

The problem is that something goes wrong with the forwarding (i think).....
Whenever I try to resolv something using the forwarding server, I'm 
getting a "SERVFAIL" so nothing is found.
When I look on in the querylogging on the the server that the forwarder 
forwards to (i.e. my new secondairy) I see the following :

First a query direct to the new secondairy
17:57:45.590XX+/145.78.156.10/lr006b01.lr006.kpn-post.nl/A/IN

now a 'forwarded query'
17:58:30.972 XX+/145.78.156.10/./NS/IN
the ip-address in these lines is my workstation.

The questions are :
-Isn't the 'forwarder' supposed to contact the new seconairy instead of 
my workstation ?
-Why does my workstation seem to ask for an empty record ?
-Is there a better solution for what I want to achieve ? Phasing out by 
forwarding / logging queries ?


=========
named.conf on "forwarder"

options {
         directory "/etc/bind";
         //forwarders { 145.78.151.79; 145.78.124.229;};
         forward only;
         forwarders { 145.78.124.229; };
};

zone "." in {
         type hint;
         file "db.cache";
};

zone "0.0.127.in-addr.arpa" in {
         type master;
         file "db.127.0.0";
};

Thanks in advance for any comments on this matter,


-- 
Met vriendelijke groet / Kind Regards,

Mark Benschop
Product Specialist UNIX
IS-BS-UNIX
070-3344324
Kamer 1308
Waldorpstraat 1
2521 CA Den Haag



More information about the bind-users mailing list