I'm having an issue getting an Internal DNS server working on a Fedora 10.

The client machine is a windows 2003 server that has the DNS Server IP set as 192.168.0.2. I can ping the IP, but not the hostname.

When I do a nslookup on the hostname I get:
Can't find server name for address 192.168.0.2: No Server Response

I have the firewall shutoff.
I used the Fed 10 Live disk and I thought that I installed everything I needed using YUM. The named is installed and running so I assume it downloaded all the dependencies. Is there something else I missed?

In named.conf:

server 192.168.0.2{
};
options {
allow-query {localhost; 192.168.0.0/24; };
listen-on port 53 { };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/name/data/cache_dump.db";
statistics-file "/var/name/data/named_stats.txt";
memstatistics-file "/var/name/data/named_mem_stats.txt";
recursion yes;
};

zone "MyMachine" IN {
type master;
allow-query { any; };
allow-update { none; };
file "MyMachine.zone";
};


In MyMachine.zone

$TTL 1D
@ IN SOA @ rname.invalid. (
1
1D
1H
1W
3H )
NS @
IN 1D A 0.0.0.0
MyMachine A 192.168.0.2
AAAA ::1


----------
I also can't do the nslookup on the server. However I can ping the hostname.

I made this change to the /etc/named.conf
listen-on port 53 { any; };

When I do a nslookup on the hostname from the client I get:
Can't find server name for address 192.168.0.2: Timed Out

I added this to the /etc/named.rfc1912.zones file.
zone "2.0.168.192.in-addr.arpa" IN {
type master;
file "MyMachine.zone";
allow-update { none; };
};

Now I get this on the client when doing the nslookup:
Can't find server name for address 192.168.0.2: No Information
2.0.168.192.in-addr.arpa
...
...
...
DNS request timed out.
timeout was 2 seconds.

Does anyone know what I'm doing wrong?

You should be able to remove this.

You need to make up a domain name, it doesn't have to exist for real (in fact, it shouldn't exist unless you bought it, because otherwise you're making it a "black hole"). It should look something like this:

Should look like:

192.168.0.reverse:

Thanks chort.

On the server when I do an nslookup I was able to do it on the MyMachine name.

Now I have to do the nslookup using ns1.MyMachine.com. This is working fine on the server.

Unfortunately I'm still having issues on the client side when doing the nslookup.
Error:
DNS request timed out

I'm doing a nslookup -d2 ns1.MyMachine.com. It looks like it is appending on an additional domain name.
Results before error:

QUESTIONS:
ns1.MyMachine.com.xxx.yy.otherDomainThatIsPublicForTheFirstNICard.com, type = A class = IN

DNS request timed out.
timeout was 2 seconds.

There is no "ANSWER:" portion for this one.

Any idea of what I should do about picking up the other domains that are for the work public network?

Or is this alright? I can ping the ns1.MyMachine.com from the client side. Is it possible that I'll have some unknown issue with the DNS? Normally if I can ping I think I'm alright.