Lines Matching refs:dnsextd

53 dnsextd
55 dnsextd has been modified to behave much like a DNS firewall. The "real"
57 interface. dnsextd then listens on the standard DNS ports (TCP/UDP port
61 information back to the caller. If the packet is allowed access, dnsextd
68 to pursue this direction, so instead dnsextd does all TSIG processing
71 there are two configuration files (named.conf or dnsextd.conf) that have
73 and moving all TSIG processing for both queries and updates into dnsextd
90 It was necessary to relax one of the checks that dnsextd performs during
91 processing of an LLQ refresh. Prior to these changes, dnsextd would
102 unencrypted UDP), dnsextd uses the port number of the client's TCP
126 Currently, dnsextd is buggy on multi-homed hosts. If it receives a
130 dnsextd doesn't fully process all of its option parameters.
147 because dnsextd doesn't ever return them, but this should be fixed so
262 Sample dnsextd.conf: