Miscellaneous BIND notesMiscellaneous BIND notes


BIND tracing
The BIND trace file is named named.run and is located in /var/named by default.

Enabling:
ndc trace (BIND 8.x)
rndc trace (BIND 9.x)
kill -USR1 named_PID (either version)

Disabling:
ndc notrace (BIND 8.x)
rndc notrace (BIND 9.x)
kill -USR2 named_PID (either version)



Caveat about using forwarders
If a name server is authoritative for a zone, it will not follow subdomain 
delegations if using a forwarder (unless it is also authoritative for the 
subdomain). 

Example: a name server is authoritative for local.zone. local.zone contains an 
NS record for subdomain.local.zone. This name server receives an A record query 
for host.subdomain.local.zone. The name server will send the query to the 
forwarder; the name server will answer requests for local.zone data, but it will 
not follow the subdomain delegation and return the A record for 
host.subdomain.local.zone.

If the forwarder is unable to gather information about subdomain.local.zone, the 
name server will exceed MAXQUERIES and will return a SERVFAIL message.

MAXQUERIES exceeded, possible data loop in resolving (host.subdomain.local.zone)

Back to brandonhutchinson.com.

Last modified: 12/01/2003

    Source: geocities.com/hackermuda/exploits/bind

               ( geocities.com/hackermuda/exploits)                   ( geocities.com/hackermuda)