Whats wrong with my BIND?
Well, here's my problem.
It's been quite some time since I've been trying to configure and run the BIND dns server on my machine as my nameserver.
When I just started, I just installed named and ran in on my machine and then edited the /etc/resolv.conf file as follows:
Next, I started BIND and it functioned properly. And I figured, that since I was using a slow internet connection, some of the hostnames could not be looked up in any number of tries (one such example was www.mitadmissions.org)
Step two; I wanted some servers that my machine could connect to more quickly than the servers specified beforehand in the file /var/lib/root.hint (in the file /var/lib/root.hint, the hint file for BIND; please note that I'm on SUSE 10.1), and hence added 3 additional dns servers provided by my isp. Finally my root.hint file looked like this:
. 3600000 NS DNSDEL.MANTRAONLINE.COM
DNSDEL.MANTRAONLINE.COM 3600000 A 184.108.40.206
; airtel dns Delhi
. 3600000 NS DNSBOM.MANTRAONLINE.COM
DNSBOM.MANTRAONLINE.COM 3600000 A 220.127.116.11
; airtel dns Bombay
. 3600000 NS DNSBLR.MANTRAONLINE.COM
DNSBLR.MANTRAONLINE.COM 3600000 A 18.104.22.168
; airtel dns Bangalore
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 22.214.171.124
; formerly NS1.ISI.EDU
. 3600000 NS B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET. 3600000 A 126.96.36.199
; formerly C.PSI.NET
. 3600000 NS C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET. 3600000 A 188.8.131.52
; formerly TERP.UMD.EDU
. 3600000 NS D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET. 3600000 A 184.108.40.206
; formerly NS.NASA.GOV
. 3600000 NS E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET. 3600000 A 220.127.116.11
; formerly NS.ISC.ORG
. 3600000 NS F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET. 3600000 A 18.104.22.168
; formerly NS.NIC.DDN.MIL
. 3600000 NS G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET. 3600000 A 22.214.171.124
; formerly AOS.ARL.ARMY.MIL
. 3600000 NS H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET. 3600000 A 126.96.36.199
; formerly NIC.NORDU.NET
. 3600000 NS I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET. 3600000 A 188.8.131.52
; operated by VeriSign, Inc.
. 3600000 NS J.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET. 3600000 A 184.108.40.206
; operated by RIPE NCC
. 3600000 NS K.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET. 3600000 A 220.127.116.11
; operated by ICANN
. 3600000 NS L.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET. 3600000 A 18.104.22.168
; operated by WIDE
. 3600000 NS M.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 3600000 A 22.214.171.124
; End of File
Now, there was certainly some performance improvement, i.e., some hostnames my dns couldn't lookup earlier could now be looked up, but there were still certain hostnames that didn't budge.
Then, I also added the 3 dns servers provided by my isp as the forwarders for BIND. This was a major improvement in performance, as now, most of the hostnames (eg. www.mitadmissions.org) could be looked up, and that too in much less time...
Anyways, I was faced with a strange problem now. I noticed that after 15-20 minutes of running, BIND stopped performing new lookups, and hostnames that would easily be looked up earlier, could not be looked up again. This problem vanished everytime I restarted the dns server, and then recurred 10-15 minutes after every such restart.
I've tried my best at it, and I've given up. Where do you guys think the problem is?
(Please note that I'm using a VERY slow GPRS connection, and I get a maximum of 15-20 kbps)
What should I do?
Thanks in advance... :-)
BTW, please don't mind the format of the root.hint file...:D
I promise that the root.hint file I have on my machine is much neater...
There we go again! Named has stopped performing new lookups again! I can't even open google.co.in now. :(
|All times are GMT -5. The time now is 07:36 PM.|