QUERY What could be going wrong here?
A couple of things are conspiring against you. :-(
The file /etc/resolv.conf could be a problem; its domain line gets set to an inappropriate
value when I reboot.
How is your /etc/resolv.conf being created/populated?
My guess is that your IP address is being assigned by a DHCP server. As part of the IP address assignment, your DHCP client is rewriting /etc/resolv.conf with the domain and nameserver assigned by the DHCP server. Hence, the "inappropriate" value after you reboot.
NSLOOKUP OUTPUT nslookup gives the SERVER address of the default name server, but says
"can't find workshop: NX domain."
This is because your default DNS server is not your local DNS server -- it is one of the DNS servers assigned to you by the DHCP server. This "other" DNS server does not know about your domain.
But nslookup still doesn't work after I edit the line to "domain example.net" and restart
bind9.
That's because you need to add your local DNS server to the list of nameservers in /etc/resolv.conf. Immediately before any other nameserver entry, add ...
nameserver 127.0.0.1
Now, when you use nslookup, your local DNS server should be your default DNS server. nslookup should now be able to resolve "workshop".
UPDATE Here is the output of dig: Command: dig A @workshop workshop.example.net
This confirms that you have your domain correctly configured on your local bind DNS server.
As you've already experienced, your changes to /etc/resolv.conf will be overwritten the next time you reboot. You have two options:
Reconfigure your machine to use a static IP. /etc/resolv.conf won't be overwritten anymore, so your changes will persist after a reboot.
Reconfigure your DHCP client so that it does not overwrite /etc/resolv.conf. This thread should point you in the right direction.
Looking at the IP addresses in your resolv.conf I get the feeling that your BIND server is on 192.168.1.52. As far as I can tell, you can't specify in resolv.conf something like "for these domains, use this name server". Basically, your BIND server will never be queried. As you can see in your dig lookup (which is incorrect, it is asking for a reverse DNS entry), it tries 80.58.0.33, which I assume is your provider's DNS server.
You already set up BIND as caching nameserver by using the 'forwarders' option, so what you need to do is have only 192.168.1.52 in the client PCs as nameserver.
To see if your BIND is configured correctly, try this:
dig example.test @192.168.1.52
Best Answer
In your dnsmasq conf file add these lines to forward specific domains to different IPs.
And this line to forward to your 'campus nameserver'
If you don't have these two things working yet (forward domain, and forward all else), troubleshoot until you get this piece working.
Once that works, start testing the search domains after that.