Providing local DNS service behind a cheap router/gateway

7 msg	reg named.conf configuration file in bind 9.3.4

Providing local DNS service behind a cheap rout...
\ Steven Stromer (27 Dec 2007)
. \ Chris Buxton (27 Dec 2007)
. . \ Steven Stromer (30 Dec 2007)
. . . \ Chris Buxton (30 Dec 2007)
. . . . \ Steven Stromer (2 Jan 2008)
. . . . . \ Chris Buxton (2 Jan 2008)
. . . . . . \ Steven Stromer (2 Jan 2008)
. . . . . . . \ Steven Stromer (3 Jan 2008)
. . . . . . . . \ Jonathan Horne (3 Jan 2008)
. . . . . . . . . \ Steven Stromer (3 Jan 2008)
. . . . . . . . \ Adam Tkac (3 Jan 2008)
. \ Danny Mayer (28 Dec 2007)

5 msg	how to get a list like 'domains using this as n...
2 msg	having DNS problems with sites hosted at ns1.el...
5 msg	DNS Server Host's Network DNS Settings
10 msg	loss of masters over ipsec hoses bind
21 msg	override ttl=0
2 msg	BIND8 was adding glue NS records to parent zones
2 msg	Slaves not picking up when master is offline
12 msg	Unable to get Zone transfer to work
3 msg	multiple answers from the same server
4 msg	Accents in Bind 9.3.1. (Extended ascii)
1 msg	RE: set up Reverse DNS zone
2 msg	OT: set up Reverse DNS zone
2 msg	BIND 9 utilities (dig, host, nslookup) error in...
6 msg	small sibling glue records help
2 msg	View Transfer
7 msg	tips on debugging DNS
3 msg	Trouble with reverse DNS
2 msg	Newbie: How to add PTR records

Subject:	Providing local DNS service behind a cheap router/gateway
Group:	Bind-users
From:	Steven Stromer
Date:	27 Dec 2007

Many of my smaller clients use high-end consumer or low-end
professional router/gateways. These router/gateways provide DHCP
services for the LAN, and are thus providing LAN hosts with DNS
information dynamically. The DNS servers that the LAN hosts are
pointed to are BIND servers running on the LAN. In these router/
gateways, there is no DHCP specific option for specifying the the IP
address to offer for DNS. The only solution is to assign the LAN
address of the BIND server in the router's WAN configuration.

The result that I believe is achieved is that the router/gateway
provides the LAN address of the local BIND host to the local clients
(this part I know to be correct). When needing name resolving
service, the local clients query the DNS service on the LAN, and the
BIND service uses full recursion to query authoritative name servers
on the internet, passing these queries, and all replies, through the
very router/gateway that provided the DHCP service.

This seems to function, but not perfectly; I notice that web pages
and similar services that depend on name resolution load more slowly
than I'd expect them to, but I'm not sure why. I am not certain
whether the router 'appreciates' having to look inward to the LAN for
name resolution, or having to pass the DNS responses on to the BIND
server on the LAN instead of handling them itself.

There exists an option in the router/gateway to toggle on or off
'Provide DNS proxy service', which I have turned off, so that the
router/gateway will not try to use its own DNS configuration (which,
as described earlier, points to the BIND server on the LAN) to
resolve the outgoing queries from the BIND server. This would
obviously cause a never-ending loop between the BIND service running
on the LAN and the router/gateway itself.

I have a feeling that the best solution would be to move the DHCP
service to one of the internal linux servers, and to be done with it
all, but it doesn't resolve my curiosity regarding this arrangement,
nor does it provide me the time to rearrange DHCP service, which is
really limited at the moment. Any insight on whether this convoluted
configuration could ever work would be really appreciated!

Thanks,
Steven Stromer