Nslookup working but ping not working at windows client

Hi Team

we have created a DNS server at RHEL6.2 environment in 10.20.203.x/24 network.
Everything is going well on linux client as nslookup, ping by host etc in entire subnet. We are getting problem in windows client as nslookup working as well but not ping. all the firewall is disabled and alos port is opened for DNS server.

Here the /etc/named.conf

//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//

options {
        listen-on port 53 { 127.0.0.1; 10.20.203.4; };
        listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        allow-query     { localhost; 10.20.203.4; };
        recursion yes;
        dnssec-enable yes;
        dnssec-validation yes;
        dnssec-lookaside auto;

        /* Path to ISC DLV key */
        bindkeys-file "/etc/named.iscdlv.key";
};

logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

zone "." IN {
        type hint;
        file "named.ca";
};

zone "example.com" IN {
       type  master;
       file "example.com.fwd";
       allow-transfer { 10.20.203.0/24; };
};

zone "203.20.10.in-addr.arpa" IN {
        type master;
        file "example.com.rev";
        allow-update { 10.20.203.0/24; };
};

include "/etc/named.rfc1912.zones";

Here the forward Zone

$TTL    86400
@                SOA         example.com.      root (
                                        42              ; serial (d. adams)
                                        3H              ; refresh
                                        15M             ; retry
                                        1W              ; expiry
                                        1D )            ; minimum

                NS              server.example.com.
  
server          A               10.20.203.4

Reverse Zone file

$TTL    86400
@             SOA     example.com. root.server.example.com.  (
                                      1997022700 ; Serial
                                      28800      ; Refresh
                                      14400      ; Retry
                                      3600000    ; Expire
                                      86400 )    ; Minimum

          IN     NS      server.example.com.
4      IN     PTR     server.example.com.

One more problem in Dig as it can't resolve the host by IP but by hostname as well.

Can anyone explain 1> why ping not working with windos
2> Dig can't resolve host by IP

I would be appreciate if someone trace out the issue here.

Thanks in Advance

Last time i got the same issue with cannot ping hostname from windows client. After troubleshooting for a while, i try to reboot those windows server since it was on test environment. After reboot, ping and nslookup both working on windows server. Still not sure though reboot can solve yours or not.

If DNS is correctly configured and working, what output do you get for your ping?

Does it say something like:-

C:\>ping myserver.my.domain.com

Pinging myserver.my.domain.com [111.222.333.444] with 32 bytes of data:

Timed out
Timed out
Timed out
Timed out

Ping statistics for 111.222.333.444:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>

If you see the IP address in the ping output, then you can be happy with DNS.

This could be a routing problem though. Can you publish the output from ifconfig -a and netstat -nr on your server? It may be that your ping gets to the server, but the server does not have a route to respond.

Thanks,
Robin

Reboot didn't help here.
Ping is working here and resolving the same.
output for netstat:

[root@server ~]# netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.20.203.0    0.0.0.0         255.255.255.0   U         0 0          0 em1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 em1
0.0.0.0         10.20.203.1    0.0.0.0         UG        0 0          0 em1
[root@server ~]# ifconfig -a
em1       Link encap:Ethernet  HWaddr D4:BE:D9:9A:3C:72
          inet addr:10.20.203.4  Bcast:10.20.203.255  Mask:255.255.255.0
          inet6 addr: fe80::d6be:d9ff:fe9a:3c72/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:222447433 errors:0 dropped:0 overruns:0 frame:0
          TX packets:55475961 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1487414468 (1.3 GiB)  TX bytes:3800055060 (3.5 GiB)
          Interrupt:20 Memory:e1a00000-e1a20000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3527 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3527 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:316488 (309.0 KiB)  TX bytes:316488 (309.0 KiB)

I have done all the troubleshooting with windows client like flush DNS cache etc.

Any other way for this?

Please put your output in CODE tags. It makes it far easier to read. You might need to write the :D in :D tags to avoid it putting in the big grin as part of a MAC address.

You haven't given us the output of a ping. It would be good to know if you can ping 10.20.203.1 too.

Thanks,
Robin

C:\Users\Desktop>ping 10.20.203.1

Pinging 10.20.203.1 with 32 bytes of data:
Reply from 10.20.203.1: bytes=32 time<1ms TTL=254
Reply from 10.20.203.1: bytes=32 time<1ms TTL=254
Reply from 10.20.203.1: bytes=32 time<1ms TTL=254
Reply from 10.20.203.1: bytes=32 time<1ms TTL=254

Ping statistics for 10.20.203.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms