At 03:28 AM 2/27/03, L Lloyd wrote:
><looks at today's, V4 #51 and hrrs> Someone already used the subject I was
>using and someone else said it wasn't helpful to use such a subject, ok,
>fine, I am flexible. I'll repost my question and hope someone will help me.
>ATM I am using Verizon's DNS servers (on again and off again proposition,
>sometimes they work and sometimes they don't)
If those are Verizon's you need to tell them that they need to fix their
nameservers or you need to find another set.
> and with your help I got Bind
>9.2 rc1 working but the other day it just stopped responding to any sort of
>internal traffic.
>I run a Windows 2000 Pro box, updated to Service Pack 3, and with the
>automatic update program running it is up to date as reasonably possible.
I never trust automatic updates, you don't know what they're going to break.
>Two days ago it was running just fine then I shut down (which shuts down
>Bind 9) to boot back into Windows 98 to play a few DOS games. Upon
>rebooting into Windows 2000 I suddenly get DNS errors. Lets see...
>
>Control Panel | Network Settings | Local Network Connection | TCP IP |
>Primary DNS Server : 192.168.0.2
>Control Panel | Network Settings | Local Network Connection | TCP IP |
>Secondary DNS Server: 0.0.0.0
If you don't have a secondary it should be empty.
>Control Panel | Administration Tools | Services | ISC Bind: Started //
>Automatic // LocalSystem
>
>Netgear RP114
>
>Advance | LAN | Primary DNS Server : 192.168.0.2
>Advance | LAN | Secondary DNS Server: 0.0.0.0
>
>I go to "telnet 192.168.0.2 53" and it says after a pause "Connection to
>Host lost." , same thing if I telnet to "127.0.0.1 53" .
Don't use telnet. It's not a text protocol and it's mostly UDP anyway. telnet
uses TCP. You should be using dig to make queries of your nameservers.
It's in the kit.
> I remove the
>router from the circuit so the computer is attached right to the ADSL modem
>supplied by Verizon (and the reason I run Bind to begin with, Verizon's DNS
>servers are very flaky ) and IPConfig /release and IPConfig /renew so it
>will obtain an IP # from the modem and set itself up to use the modem and
>then use the IP# from the modem as the Secondary DNS Server IP# and vola,
>it works. So it seems Bind is working but something in the local system is
>not liking 192.168.0.2 even though in the Router's IP # assignment page it
>lists my computer as 192.168.0.2 and IPConfig lists this computer as
>192.168.0.2 . To get this working for *now* I added 4.2.2.1 as my Secondary
>DNS Server IP# which is Verizon's DNS Server IP# and it works. How do I get
>the Netgear RP114 and my local system to again accept DNS from the local
>system? Having not changed anything recently I am really in the dark as to
>why it suddenly stopped working. I could connect via pure IP# though the
>router just couldn't do any DNS lookups. Lets see, I am running Bind
>9.2.2rc1 and my configuration files are
If you can't get 127.0.0.1 then BIND itself is not responding. 127.0.0.1 is the
local loopback and does not involve any hardware to work. You didn't tell
us what you have in your application event log which you can get at via
the event viewer.
>
>NAMED.CONF
>
>
>zone "localhost" {
> type master;
> file "db.localhost";
>};
>zone "127.in-addr.arpa" {
> type master;
> file "db.127";
>};
You didn't include the complete named.conf.
Danny
>
>DB.127
>
>$TTL 604800
>@ IN SOA localhost. root.localhost. (
> 1 ; Serial
> 604800 ; Refresh
> 86400 ; Retry
> 2419200 ; Expire
> 604800 ) ; Negative Cache TTL
>;
>@ IN NS localhost.
>1.0.0 IN PTR localhost.
>
>
>DB.localhost
>
>$TTL 604800
>@ IN SOA localhost. root.localhost. (
> 1 ; Serial
> 604800 ; Refresh
> 86400 ; Retry
> 2419200 ; Expire
> 604800 ) ; Negative Cache TTL
>;
>@ IN NS localhost.
>@ IN A 127.0.0.1
>
>
>DB.ROOT
>
>; This file holds the information on root name servers needed to
>; initialize cache of Internet domain name servers
>; (e.g. reference this file in the "cache . <file>"
>; configuration file of BIND domain name servers).
>;
>; This file is made available by InterNIC registration services
>; under anonymous FTP as
>; file /domain/named.root
>; on server FTP.RS.INTERNIC.NET
>; -OR- under Gopher at RS.INTERNIC.NET
>; under menu InterNIC Registration Services (NSI)
>; submenu InterNIC Registration Archives
>; file named.root
>;
>; last update: Aug 22, 1997
>; related version of root zone: 1997082200
>;
>;
>; formerly NS.INTERNIC.NET
>;
>. 3600000 IN NS A.ROOT-SERVERS.NET.
>A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
>;
>; formerly NS1.ISI.EDU
>;
>. 3600000 NS B.ROOT-SERVERS.NET.
>B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
>;
>; formerly C.PSI.NET
>;
>. 3600000 NS C.ROOT-SERVERS.NET.
>C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
>;
>; formerly TERP.UMD.EDU
>;
>. 3600000 NS D.ROOT-SERVERS.NET.
>D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
>;
>; formerly NS.NASA.GOV
>;
>. 3600000 NS E.ROOT-SERVERS.NET.
>E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
>;
>; formerly NS.ISC.ORG
>;
>. 3600000 NS F.ROOT-SERVERS.NET.
>F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
>;
>; formerly NS.NIC.DDN.MIL
>;
>. 3600000 NS G.ROOT-SERVERS.NET.
>G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
>;
>; formerly AOS.ARL.ARMY.MIL
>;
>. 3600000 NS H.ROOT-SERVERS.NET.
>H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
>;
>; formerly NIC.NORDU.NET
>;
>. 3600000 NS I.ROOT-SERVERS.NET.
>I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
>;
>; temporarily housed at NSI (InterNIC)
>;
>. 3600000 NS J.ROOT-SERVERS.NET.
>J.ROOT-SERVERS.NET. 3600000 A 198.41.0.10
>;
>; housed in LINX, operated by RIPE NCC
>;
>. 3600000 NS K.ROOT-SERVERS.NET.
>K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
>;
>; temporarily housed at ISI (IANA)
>;
>. 3600000 NS L.ROOT-SERVERS.NET.
>L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12
>;
>; housed in Japan, operated by WIDE
>;
>. 3600000 NS M.ROOT-SERVERS.NET.
>M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
>; End of File
>
>
>
>NAMED.PID
>
>2168
>
>and the RNDC.key file
>
>
>Oh and FYI, I really don't understand most of this. You wonderful people
>helped me set this up and I followed instructions and it worked and all was
>good. Now it's broke and all is bad. :( I'd be really appreciative if you
>all could help me get this working. Thank you for your time.
>
>Lee
>
>
>-- Attached file included as plaintext by Ecartis --
>
>
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.456 / Virus Database: 256 - Release Date: 2/18/2003
>
|
