5 msgadd chinese domaine ton bind ?
1 msg[Fwd: view function of Bind 9]
2 msgLISA '07 Call For Papers
1 msgBind and ipfilter
5 msgF5 and DNS
2 msgSlave refresh error on zone segmented configura...
4 msgDNSSEC support in libbind
23 msgVirtual Hosts don't work with 'www'
19 msgPublic DNS - recursion no - Access to the Internet
2 msgSyncing Multiple (like, 10) Views using TSIG.. ...
3 msgDNS request timed out
1 msgRe: bind performance guideline
2 msgRe: ISC Bulletin #1
2 msgexpected view behavior
5 msgWeird problem.

logging of desination ip-address ?
\ Danny Thomas (11 Feb 2007)
. \ Barry Margolin (12 Feb 2007)

7 msgZone file x'fer between two masters
1 msgobtaining query source IP from an sdb driver?
4 msgSerious bind issue
3 msgBIND Log Analyzer
Subject:logging of desination ip-address ?
Group:Bind-users
From:Danny Thomas
Date:11 Feb 2007


 
While bind9 allows fine-grained control of ip-address usage
listen-on
query-source
transfer-source
and so forth, the destination address is not logged.

For example I recently wanted to find out whether
cisco boomerang dns
spurious ./NS (mainly from China)
spurious A.ROOT-SERVERS.NET/A (from China & Japan)
queries were arriving at the resolving or authoritative ip-address
of our name-servers, and I ended up using tcpdump. Luckily there
was at least one well-known source address for each of these types.

I think it could be useful to have a compile-time option enabling
whether query/update logging included destination ip/port.

Danny

--
d.thomas Danny Thomas,
+61-7-3365-8221 Software Infrastructure,
http://www.its.uq.edu.au ITS, The University of Queensland




© 2004-2008 readlist.com