Simple bind9 zone file

bindzones

I'm setting a network in a virtual enviroinment. I have two networks, one internal (corp.net) and one external (with one name server and one client), connected by a firewall. I want that client can resolve names as www.corp.net, using the external nameserver. This is my zone.net.corp zone file:

$TTL 2d
$ORIGIN corp.net.
@ IN SOA server1. root.corp.net. (200405191 8H 4H 4W 1D)
    IN NS server1.

www CNAME gateway1

gateway1.corp.net. IN A 192.168.200.2
server1. IN A 192.168.200.70

But if i check the zonefile

root@server1:/etc/bind# named-checkzone zone.net zone.net.corp
zone.net.corp:6: ignoring out-of-zone data (corp.net)
zone.net.corp:9: ignoring out-of-zone data (www.corp.net)
zone.net.corp:18: ignoring out-of-zone data (gateway1.corp.net)
zone.net.corp:19: ignoring out-of-zone data (server1)
zone zone.net/IN: has 0 SOA records
zone zone.net/IN: has no NS records

NOTE: server1 is an external nameserver, not in the network corp.net. The hostname server1 is only specified in /etc/hostname. I want that an external machine that use as nameserver 192.168.200.70, can resolve www.corp.net.

Best Answer

The first argument to named-checkzone is the zone name, not the filename. You cannot have names like "corp.net" inside "zone.net" no matter how hard you try.

Also, your "server1" server is rooted at ., which is probably not what you want.

Related Solutions

Debian – Setting up a DNS name server for a mass virtual host with Bind9

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

Bind9 DNS Ubuntu names pingible on server, but not on Windows Machines

I'm wondering if the issue is how suffix appending is working on the windows machines. To test this, try running nslookup on a full name on one of the windows machines, i.e. nslookup ns.leerdomain.local. If that works it means your windows machines are not appending the leerdomain.local suffix to your queries. You can check that in tcp/ip properties->advanced on one of the windows machines.

Look at /etc/resolv.conf on the ubuntu box, the search directive there will tell you how that machine is appending domains. Look at the output of ipconfig /all on one of the windows machines, in particular check the output of primary dns suffix. ipconfig /displaydns may also give you some useful info about how the machine is configured to use DNS.

Related Topic