BIND
acronymnetworking
Stands for: Berkeley Internet Name Domain
The most widely deployed DNS server software.
Berkeley Internet Name Domain is the reference DNS server from ISC. On BIG-IP DNS, a 'fall through to BIND' action hands a query to the local BIND instance when no wide IP or other object answers it.
BIND is the reference DNS server, the one the protocol's behaviour was effectively defined by, and it still runs a substantial share of the internet's authoritative and recursive infrastructure. Its longevity means both mature capability and accumulated complexity, and its configuration syntax is the closest thing DNS has to a lingua franca.
Its history is also a security lesson. BIND has had a long list of serious vulnerabilities, which is partly the price of being the largest target and partly the consequence of a codebase carrying decades of features. That history drove real architectural improvements, including privilege separation and the split between authoritative and recursive roles that is now standard practice rather than a refinement.
The advice that matters most is separation. A server that answers authoritatively for your zones should not also be an open recursive resolver, because a resolver that answers anyone is a reflection amplifier waiting to be used against a third party, and combining the roles makes both harder to reason about. Running the two functions separately, with recursion restricted to your own clients, resolves a whole class of problems at the cost of one more configuration file.
Also known as: bind