Bind and Windows XP problem

[Kevin Darcy]

The nslookup failure implies that a reverse-resolution of the address
10.0.0.8 is not working from the client. The failure to ping via
FQDN from the client implies that forward resolution of
thorgal.wauters-mannaert.be is not working from the client. The most
obvious commonality is the nameserver itself, but local queries work, so
that, in turn, points the finger of blame at some form of network
(dis)connectivity.

Enable query logging to see if the queries are actually getting to the
server from the client.

If they aren't, then, optionally, start sniffing packets to see if
they're actually arriving.

If not, then check the settings on your "router" (I suspect you're not
actually *routing* between 10.0.0.10 and 10.0.0.8, but merely using the
router's built-in switch ports). Maybe you're accidentally blocking or
dropping UDP.


- Kevin

WIWA wrote:

> Hi all,
>
> I don't know if this is the right place to post my question. It
> concerns a mixture of Bind, Redhat8 and Windows XP.
>
> On a Redhat Linux machine I have installed Bind 9. This machine is
> called thorgal.wauters-mannaert.be (on 10.0.0.8 in my local network).
> On this machine, everything is working. That means when I do nslookup,
> I get back the IP address for this device as well as for all the
> connected clients. I get
>
> [root at localhost root]# nslookup
> Note:  nslookup is deprecated and may be removed from future releases.
> Consider using the `dig' or `host' programs instead.  Run nslookup
> with
> the `-sil[ent]' option to prevent this message from appearing.
> > server 10.0.0.8
> Default server: 10.0.0.8
> Address: 10.0.0.8#53
> > thorgal.wauters-mannaert.be
> Server:         10.0.0.8
> Address:        10.0.0.8#53
>
> Name:   thorgal.wauters-mannaert.be
> Address: 10.0.0.8
>
> > ogotai.wauters-mannaert.be
> Server:         10.0.0.8
> Address:        10.0.0.8#53
>
> Name:   ogotai.wauters-mannaert.be
> Address: 10.0.0.10
> > exit
>
> [root at localhost root]# ping ogotai.wauters-mannaert.be
> PING ogotai.wauters-mannaert.be (10.0.0.10) from 10.0.0.8 : 56(84)
> bytes of data.
> 64 bytes from ogotai.wauters-mannaert.be (10.0.0.10): icmp_seq=1
> ttl=128 time=0.460 ms
> 64 bytes from ogotai.wauters-mannaert.be (10.0.0.10): icmp_seq=2
> ttl=128 time=0.250 ms
> 64 bytes from ogotai.wauters-mannaert.be (10.0.0.10): icmp_seq=3
> ttl=128 time=0.274 ms
>
> --- ogotai.wauters-mannaert.be ping statistics ---
> 3 packets transmitted, 3 received, 0% loss, time 2003ms
> rtt min/avg/max/mdev = 0.250/0.328/0.460/0.093 ms
> [root at localhost root]#
>
> However, when I go to my client, which is called
> ogotai.wauters-mannaert.be, it does not work. When I go to nslookup
> and type ogotai.wauters-mannaert.be, it gives: "Cannot find server
> name for 10.0.0.8: no response from server". I can ping from this
> machine to Thorgal using the IP-address, but not using the FQDN, which
> is strange, since it is resolving correctly on the DNS server. I
> configured my Windows XP client to look at 10.0.0.8 which is my Linux
> DNS server.
>
> Also, both Linux PC and Windows XP machine are connected to a router
> and can ping one another using IP addresses.
>
> 1) Does anyone know why I cannot ping from my Windows XP machine to
> the Linux machine using the FQDN?
> 2) Why is nslookup not working at the Windows client PC?
>
> If anyone know an answer it wioll be greatly appreciated. If this is
> not the correct group, please forward me to another group/
>
> Thanks in advance,
>
> Wim