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 windows
2> Dig can't resolve host by IP

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

Thanks in Advance

It sounds like everything is working on Linux clients, but not working on the Windows clients. Is that correct?

If that is correct, then the problem is probably not with the server, because obviously all the necessary traffic is getting through to it from the Linux clients.

Are the Windows boxen on the same subnet? are they connected to a router or a managed switch that differs from what is connecting the Linux clients?

Or am I mis-understanding the diagnosis?

Only Ping not working on the Windows clients.

yes, All the clients+server are on the same subnet and also the same switch.

Problem is not the route, clinets and server can ping to each other successfully.

Can anyone have the different approach for the same?

Unless I'm missing something, it sounds like a Windows ping issue, not a Linux server or client issue.

When you say ping doesn't work, what are you trying to ping and from where? Are you on a windows machine pinging out? If so, by ip or hostname?

I am trying to ping Hostname for the DNS server from the windows client. Unless nslookup is working the same on windows clients.

you are trying to ping with hostname from windows client to resolve it to its ip address like for example

ping www.linuxquestions.org
Reply from 75.126.162.205: bytes=32 time=197ms TTL=45

make sure the DNS server IP is the first dns for the windows clients if it is, while pinging from windows client, in linux server tcpdump the traffic from windows client to see if you receive any DNS query packets.

From an administrator command prompt you can try running ipconfig /flushdns and then retrying ping. I've had to do this occasionally on my W7 workstation for some unknown reason.

Not working the same.

Caveat: I know nothing about windows, and this is a Linux forum. BUT...is there some kind of software firewall on Windows that might be getting in the way (although any firewall blocking DNS is kind of hard to imagine)... ?

1) first ping by ip address: does it work? If yes, then move on. If no, then you cannot ping to that ip address for whatever networking related reason (or maybe destination server has firewall, or your client has firewall - for whatever reason ping is not getting responded to)

2) next do your nslookup on the hostname you want to ping: "nslookup [hostname]". Make sure the ip it returns is what you expect.

3) then ping hostname
You should see the ip address it is trying to ping. That IP should be what is returned in step 2. If it is, then ping should respond back. If it isn't, then there is some DNS issue or for whatever reason the application using "ping" is not using your local server's DNS config.

That should be a good start, if not point you to the problem.

Criminy:
edit C:\Windows\System32\drivers\etc\hosts and add an entry for the remote host.
ping remote_host.

Problem solved.

I am looking ping by DNS server.

I hate to be blunt, but you're bringing a knife to a gunfight.

and
ping is unreliable as a test since ICMP requests to a host may not be allowed.
nslookup and ping aren't the same thing.

Can you ping the host by IP from Windows?

yes, I can ping the host by Ip from windows client.