hosts.allow

[Dan Nelson]

In the last episode (Feb 23), kalin mintchev said:
> i have some crap in my log like:
> 
> Feb 23 16:56:45 bigdaddy named[85641]: client 218.19.160.163#63869: update 'bigdaddy.com/IN' denied
> Feb 23 16:56:46 bigdaddy named[85641]: client 218.19.160.163#62855: update 'bigdaddy.com/IN' denied
> Feb 23 17:02:10 bigdaddy named[85641]: client 218.19.160.163#63999: update 'bigdaddy.com/IN' denied
> Feb 23 17:16:20 bigdaddy named[85641]: client 218.19.160.163#62723: update 'bigdaddy.com/IN' denied
> Feb 23 17:16:59 bigdaddy named[85641]: client 218.19.160.163#63975: update 'bigdaddy.com/IN' denied
> Feb 23 17:20:38 bigdaddy named[85641]: client 218.19.160.163#63873: update 'bigdaddy.com/IN' denied
> Feb 23 17:21:05 bigdaddy named[85641]: client 218.19.160.163#64057: update 'bigdaddy.com/IN' denied
> 
> so i put:
> 
> ALL : 218.19.160.163 : deny
> 
> in my hosts.allow but i still get that log piling up....

Named isn't built with tcpwrapper support; it would probably cause too
much overhead.  Chances are the machine at 218.19.160.163 is a windows
XP machine at your location, with Dynamic DNS updating enabled.  Just
go into the TCP/IP prefs and disable it.
 
-- 
	Dan Nelson
	dnelson at allantgroup.com