Invalid hostnames logging problem

[chrism at sea.checkpoint.com]

Bob,

One thing you can do in this case is add the line 'check-names ignore'
within the zone statement for that slave.  That will ignore the invalid
names for *that zone only* and still log warnings for other zones.  It
would look something like this:

zone "italy.ibm.com" {
  type slave ;
  masters { 10.20.30.40 ; } ;   # whatever the real IP is
  file "italy.ibm.com.db.bak" ;
  check-names ignore ;          # <--- this is the line to add
} ;

Hope this helps!

- Chris

--
         Chris Moore  --  chrism at sea.checkpoint.com
Check Point Software Technologies, Inc.  --   The Meta IP Group
     http://www.checkpoint.com/products/metaip/index.html

On Tue, 30 Oct 2001 05:20:16 R. Alexander wrote:
- 
- I have setup a non official secondary DNS in my office (non official 
- means amongst other things that I cannot complain to my upstream DNSs
- 8->).
- 
- One of the zones I am replicating is quite full of invalid hostnames 
- (underscores etc.).
- 
- Can I use the logging directive in my named.conf file to abolish such 
- warnings ???
- 
- Thank you very much. Bob alexander
- 
- My syslog fills up with records such as:
- 
- syslog.0:Oct 30 01:35:53 lori-renato named[182]: owner name 
- "pca136_2.italy.ibm.com" IN (secondary) is invalid - proceeding anyway
- 
- and
- 
- /var/log/daemon.log:Oct 22 02:02:17 lori-renato named[186]: host name 
- "out_ixd.italy.ibm.com" (owner "76.58.87.9.in-addr.arpa") IN
- (secondary) 
- is invalid - proceeding anyway
- 
-