/etc/inetd.conf ???

Hello

You answered:

>On 10 Jul 2006, in the Usenet newsgroup comp.os.linux.networking, in article
>
><1152563399.101092.240...@75g2000cwc.googlegroups .com>, michanux wrote:
>>The answer of 'nslookup michael.zuhause.de' is:
>
>working OK
>
>>Neither 'ping' nor 'ftp michael.zuhause.de' find the address but 'ping
>>192.168.1.12' and
>>'ftp 192.168.1.12' are successfull.
>
>Three possible causes:
>
>[compton ~]$ cat /etc/host.conf
>order hosts,bind
>multi on
>[compton ~]$ grep host /etc/nsswitch.conf
>hosts: files nis dns
>[compton ~]$
>
>(Explanation: DNS tools like '
>
>dig' 'dnsquery', 'host' and 'nslookup' ignore
>those two files. /etc/host.conf is the older file, used by libc based
>applications. /etc/nsswitch.conf is the more modern file, used by glibc2.)
>
>It's also possible though far less likely, that there is an entry for that
>hostname either in /etc/hosts, or (in the above example) in the NIS database
>if you are running yp - that lists the hostname but no address, or lists some
>non-accurate address.
>
> Old guy

All the files are the way you figure out. Meanwhile I got an new
suspicion.
'named' started at The beginning of the session by '/etc/rc.local'. But
should I
open a special port for an additional daemon in '/etc/inetd.conf'

Michael

On 15 Jul 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, michanux wrote:


] On 11 Jul 2006, in the Usenet newsgroup comp.os.linux.networking, in article
] <(E-Mail Removed)>, I wrote:

>>On 10 Jul 2006, in the Usenet newsgroup comp.os.linux.networking, in article
>><1152563399.101092.240...@75g2000cwc.googlegroup s.com>, michanux wrote:

>>>The answer of 'nslookup michael.zuhause.de' is:
>>
>>working OK

>>>Neither 'ping' nor 'ftp michael.zuhause.de' find the address but 'ping
>>192.168.1.12' and 'ftp 192.168.1.12' are successfull.

>>(Explanation: DNS tools like 'dig' 'dnsquery', 'host' and 'nslookup' ignore

/etc/host.conf and /etc/nsswitch.conf, but gethostbyname(3) checks those
when making a lookup.

>All the files are the way you figure out. Meanwhile I got an new
>suspicion.
>'named' started at The beginning of the session by '/etc/rc.local'. But
>should I open a special port for an additional daemon in '/etc/inetd.conf'

No - you can only run the daemon out of one place (the normal would be a
a runlevel script, such as /etc/rc.d/rc3.d/S55named - lacking that,
then running it out of rc.local is OK). Trying to run it out of inetd.conf
is _most_ unusual (I don't think I've ever seen it done by any regular
distribution), and will cause grief because the same port can not be
accessed by two or more daemons at the same time.

Try using 'strace' to see where things are barfing. Try

strace -eopen ping michael.zuhause.de

which _might_ give clues about the failure.

Old guy