PDA

View Full Version : [all variants] nslookup resolves, but I can't ping it (route working)



azzamite
July 9th, 2009, 07:50 PM
Hi all.

Yesterday some weird configuration was made so that we didn't need to have
the static (public) IP address of the servers in our hosts file.

In our windows boxes, we just executed
ipconfig /flushdns
and now we can acces the servers just like that.

But I haven't been able to acces the servers from our GNU/linux boxes,
one is Ubuntu 9 and the other is Debian 5.

Forums subjest to restart nscd, neither box had it installed, so I
installed and restarted it; bun nothing, still can't ping.

If I do
nslookup ourserver
I get it's IP, and I can ping that IP and even acces to it from the
explorer. But if I do
ping ourserver
I get a
ping: unknown host ourserver

superprash2003
July 9th, 2009, 08:07 PM
you could find out what DNS servers the windows machines are using and applying them to the ubuntu machines manually

azzamite
July 9th, 2009, 08:29 PM
you could find out what DNS servers the windows machines are using and applying them to the ubuntu machines manually

Both boxes connect using DHCP.

I cheked the route, IP, Gateway, mask and DNS Everything the same,
averything works, actually I'm writhing this from the Debian box.

But the fact is that even thougth nslookup gives me the IP and I can ping that IP I can't acces the server using it's name, neither from Ubuntu or Debian.



nslookup something.local
Server: 192.168.0.3
Address: 192.168.0.3#53

Name: something.local
Address: 192.168.0.6

ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=1 ttl=126 time=59.3 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=126 time=70.1 ms
^C
--- 192.168.0.3 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1006ms
rtt min/avg/max/mdev = 59.388/64.755/70.122/5.367 ms

ping 192.168.0.6
PING 192.168.0.6 (192.168.0.6) 56(84) bytes of data.
64 bytes from 192.168.0.6: icmp_seq=1 ttl=62 time=67.7 ms
64 bytes from 192.168.0.6: icmp_seq=2 ttl=62 time=69.1 ms
64 bytes from 192.168.0.6: icmp_seq=3 ttl=62 time=51.7 ms
^C
--- 192.168.0.6 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2008ms
rtt min/avg/max/mdev = 51.702/62.856/69.122/7.907 ms


ping something.local
ping: unknown host something.local


Some more (mabe) useless info


My IP 192.168.3.66 Bcast:192.168.3.255

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.3.0 * 255.255.255.0 U 0 0 0 wlan0
default 192.168.3.5 0.0.0.0 UG 0 0 0 wlan0

cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.3
nameserver 192.168.3.5


The GW is connected to the VLan and does the routing to 192.168.x.x.

superprash2003
July 10th, 2009, 11:42 AM
well could it be a firewall blocking , cause if your able to resolve it means the DNS is doing its job..