Ok, I commented out the allow_query line and it seems to have fixed it. Is that directive optional and only used if I want to restrict who can query the name server? Also, can you try www.helpingyouth.ca form you end....you should get a test page with the text "Helping Youth Home Page" if everything resolved and loaded properly.

Hopefully not too many more questions, but where can I find some docs on making the name server a complete name server and not just for the domains I host? Or is this even an appropriate question? Right now I am using it as a caching name server locally with the following options:

listen-on { 127.0.0.1; 192.168.1.2; };
// allow-query { 127.0.0.1; 192.168.1.0/24; 207.216.240.22; };
forward first;
forwarders { 192.168.1.1; 154.11.128.59; 154.11.128.187; 216.220.40.243; 205.210.42.19; };

Hehehe...Actually, you should be removing that line altogether, if you want everyone to be able to ask questions of your name server. queries are different from recursive lookups (which you probably do want to restrict). A query is when someone asks your nameserver, "hey, do you know who this is?" You want it to answer "yes, it's 207.216.240.22, thanks for asking", rather than "go away!"

;-)

There's quite a bit of documentation about BIND in the Webmin documentation wiki, here:

http://doxfer.com/Webmin/BINDDNSServer

And here:

http://doxfer.com/Webmin/CachingNameserver

And here:

http://doxfer.com/Webmin/ResolutionForVirtualHosts

And here:

http://doxfer.com/Webmin/BINDTroubleshootingTools

Of course, in your case, being a recursive name server is BIND's native habitat, so enabling it is breezy. There's a single option in the BIND module in the Miscellaneous section called "Do full recursive lookups for clients?" that turns it on. But forwarders, plus allowing direct lookups if the forwarders fail, is probably the right thing to do in your case. It'll probably be faster, and it'll certainly be easier on the root name servers.