Quick follow up. I changed the forwarders that I was using in the named.conf
file and domain names seem to be resolving OK now. But I'm still not getting
an answer for my local domain pinging from the XP workstation. How do I get
the linux box to first look at its own DNS? If I ping www.mydomain.com
<http://www.mydomain.com/>  from the workstation I just get 'could not find
host'. If I ping from Linux box then I get the ip address back for the real
registered domain. The zone is correctly entered in named.conf and the zone
file is correctly set up. I've checked them both over twenty times at least.
There is obviously some other setting I've missed. Any help?

(ipconfig on XP shows 192.168.0.1 as DNS Server and Gateway)

 

  _____  

From: tclug-list-bounces at mn-linux.org
[mailto:tclug-list-bounces at mn-linux.org] On Behalf Of John Sanborn
Sent: Tuesday, October 24, 2006 3:28 PM
To: tclug-list at mn-linux.org
Subject: [tclug-list] BIND 9

 

Hi All,

 

I just reinstalled Fedora 5 (no GUI, and did a 206 MB yum update) on a box I
use with two NICs for my home network gateway and firewall. The eth0 NIC is
connected to a DSL modem and the eth1 NIC goes to a switch for the LAN. DHCP
is running the FC5 box for the LAN and seems to be working fine. I use
iptables for the firewall and I copied the same set of rules from the Fedora
3 Bible except for the TCP rules for allowing access to web and ftp stuff.
(I don't have anything running that needs to be accessed from outside.) 

 

DNS, however, is not being very friendly. I can ping ip addresses but not
domains from a command line on an XP box inside the LAN. Email seems to be
coming and going somewhat OK. But websites won't come up in the browser. I'm
fairly certain the problem is my DNS setup. nslookup on the XP box returns
"can't find server name for address 192.168.0.1" I can't get the zone file
updates from the W2K3 domain controller which was working just fine before.
I sure I set up the named.conf and created the zone file for my domain just
like before. (I reinstalled in the first place because the linux box locked
up and wouldn't reboot for anything. Hardware problem, I expect.) I also had
the linux box looking first at its own DNS before going out to the web so I
could browse sites on my development server on the LAN. My LANs domain name
is not a registered name but exists just for me inside my LAN.

 

Can anyone offer some typical gotchas or often overlooked setup details that
I probably missed that would likely cause these symptoms? I've been reading
HOW-TOs for a week and I'm just burnt out it.           -- THANKS, John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20061025/0214444d/attachment.htm