I'm playing around with ISPConfig and DNS (Bind9) on my testing machine - an Ubuntu laptop - before I try to make anything work in production. I've created a DNS zone in ISPConfig - just something random for testing, so it's for "fish.com" - then I've gone to the command line and tried "nslookup fish.com", and it's giving me the IP address of the "fish.com" website that does actually exist on the Internet (though it is saying that the name server is 127.0.1.1, so it is passing through my local DNS server). But I'd set up the dhcp config file for this laptop to have "prepend 127.0.1.1" in it, making the localhost DNS server the primary DNS and then in Bind's configuration, I've added the ISP's name servers as forwarders. What I want and was expecting is that the "nslookup" would query the localhost DNS server at 127.0.1.1 and ask it for "fish.com". As I've created a DNS zone in ISPConfig for it, then I wanted and expected this to be returned. Only if the localhost DNS cannot answer the query should it then be forwarded onto my ISP's name servers (as I would still like to retain general Internet access on the laptop and, even in production, I'd still want to be able to access update servers and the like, of course). I did also try "supersede 127.0.1.1" in the "dhclient.conf", so that only the local DNS server would be queried (but it would forward on any queries it can't answer to my ISP). But there's no response at all when I do this. It just times out. How would I set this up, on my Ubuntu laptop, so that my own DNS server will be authoritative about its own DNS zones - both locally and if it was queried externally - and then forwards onto the ISP name servers for everything else? So that a query for "fish.com" would actually be answered by my own local DNS zone, even though there is a "fish.com" on the Internet. This is both for testing purposes - to ensure that my DNS server is providing the answers and not some other DNS server in the chain - but it'd also be useful to retain this ability anyway for the purposes of creating "fake" DNS zones, websites and emails locally to get things up and running, before actually pointing a real registered domain name at it all and making it public.