Hi Pere Casas! On 2012.08.13 at 11:18:16 +0200, Pere Casas wrote next:
> [root@intern ~]# ping priona.net > ping: unknown host priona.net > > > [root@intern ~]# nslookup priona.net > Server: 8.8.8.8 > Address: 8.8.8.8#53 > Non-authoritative answer: > Name: priona.net > Address: 146.255.96.119 Unlike host, dig and nslookup, which are part of BIND suite and use BIND resolver, ping uses system-wide resolver provided by glibc (libresolv). They can behave differently. First thing worth checking if you are running nscd - and if you are, its configuration on domain name caching. Check output of "pgrep nscd" - if you see number (pid), you are running nscd. If you are, check if advices from http://www.eyrie.org/~eagle/notes/solaris/dns-cache.html will help. If you are not, well, such situation can happen, but I can't remember any more possible reasons. At very least, you should check if your glibc isn't broken ("rpm -qV glibc" will do for a check) and if "strace ping priona.net" writes anything suspicious. -- Vladimir
