hosts.allow does not resolve names

hosts.allow does not work with network names.
Would some kind soul tell me why it does not work?

/etc/hosts.allow fails with
ALL: .home.invalid
but ALL: 192.168.1.0/255.255.255.0 works.


$ hostname --domain
home.invalid

$ grep hosts: /etc/nsswitch.conf
hosts: files dns

$ cat /etc/host.conf
order hosts,bind
multi on
nospoof on
spoofalert on

$ head -4 /etc/hosts
127.0.0.1 localhost
192.168.1.213 m2008.home.invalid m2008
192.168.1.11 fw.home.invalid fw
192.168.1.130 wb.home.invalid wb

Running Mandriva Linux release 2008.0

Not running named/bind, NIS, YP. avahi*, tmdns

Tried tcpdchk but Mandirva runs xinetd instead of inetd so it fails.
.

Relevant Pages

  • Re: hostname doesnt stick
    ... GUI, then running "service network restart", or even rebooting, fails ... no change in the hostname. ...
    (Fedora)
  • Re: weird issues with "at" command
    ... the permissions are simply 644 and at.cmd ... "env" on both systems and compared and except for hostname and ... Is all blank in SMIT for abcprod but for abctest (the one that fails) ...
    (comp.unix.aix)
  • Re: OT: DNS Records
    ... > mulitple A records for a particular hostname so that it fails over ... > automatically without needing to set a short TTL (which has its own ...
    (uk.net.web.authoring)
  • Re: OT: regexp help needed
    ... this fails for two reasons. ... It only ignores comment lines if the very first character on the ... It expects *ZERO* or more blanks following the hostname. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: hostname doesnt stick
    ... then running "service network restart", or even rebooting, fails to effect ... no change in the hostname. ...
    (Fedora)