GR> How come if I disable recursive lookups I cannot browse
GR> outside sites?
Because your DNS server does not have the entire contents of the public DNS
database to hand locally. To look up information in the distributed public
DNS database, it needs to send back-end queries to the servers that publish
the relevant portions of the database. Sending back-end queries to other
DNS servers is, of course, the definition of recursion.
GR> DNSstuff dings me if I leave recursive on. Any ideas?
Use separate DNS servers for your content and proxy DNS services.
<URL:
http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-server-roles.html>
GR> Can I prevent access to the DNS server by IP address in
GR> the DNS manager
Not effectively.
GR> is it usually done at the firewall?
No. It's *usually* done by using RFC 1918 private addresses.
<URL:
http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-server-roles.html#ProxyIP>
For a DNS server that needs to be accessible through a firewall in the
first place, IP address restriction is usually completely inappropriate
anyway.
<URL:
http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-shaped-firewall-holes.html>
GR> is there anyway to setup a template for adding domains?
Not in Microsoft's DNS server, no. Other DNS server softwares have
mechanisms for simply generating the data for "zones" from templates.
Microsoft's does not. (However, one can use server-side aliasing in
Microsoft's DNS server to make two "zones" server-side aliases of each
other, as long as one doesn't use Active Directory integrated "zones",
by having them use the same database source file.)