bind9 DNS Ubuntu names pingible on server, but not on Windows Machines?
- by leeand00
I setup a DNS server today on Ubuntu, following this tutorial. My intent was to setup my network for dns-name resolving on the private LAN within a single zone (nothing fancy I just want name resolution).
I've tested the setup on the DNS server machine itself, and I can ping all the machines listed in the configuration file. I've also configured the Windows Machines on my network, and for some reason they are incapable of pinging by names as was possible on the DNS Server itself.
I've tried running nslookup on the Windows DNS clients and I receive and error mentioning the address of the DNS server.
DNS forwarding works fine, I'm not having any trouble accessing the internet, the problem only lies within accessing names within the private LAN.
Here are my configuration files:
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
// forwarders {
// 0.0.0.0;
// };
forwarders {
8.8.8.8;
8.8.8.4;
74.242.0.12;
//68.87.76.178;
};
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
};
/etc/bind/named.conf.options
zone "leerdomain.local" {
type master;
file "/etc/bind/zones/leerdomain.local.db";
notify no;
};
zone "2.168.192.in-addr.arpa" {
type master;
file "/etc/bind/zones/rev.2.168.192.in-addr.arpa";
notify no;
};
/etc/bind/named.conf.local
Lookup:
$TTL 3D
@ IN SOA ns.leerdomain.local. admin.leerdomain.local. (
2010011001
28800
3600
604800
38400
);
leerdomain.local. IN NS ns.leerdomain.local.
ns IN A 192.168.2.9
asus IN A 192.168.2.254
www IN CNAME asus
vaio IN A 192.168.2.253
iptouch IN A 192.168.2.252
toshiba IN A 192.168.2.251
gw IN A 192.168.2.1
TXT "Network Gateway"
/etc/bind/zones/leerdomain.local.db
(Validates fine with named-checkzone when validating zone leerdomain.local)
Reverse Lookup:
$TTL 3D
@ IN SOA ns.leerdomain.local. admin.leerdomain.local. (
201001101
28800
604800
604800
86400
)
IN NS ns.leerdomain.local.
1 IN PTR gw.leerdomain.local.
254 IN PTR asus.leerdomain.local.
253 IN PTR vaio.leerdomain.local.
252 IN PTR iptouch.leerdomain.local.
251 IN PTR toshiba.leerdomain.local.
/etc/bind/zones/rev.2.168.192.in-addr.arpa
*(Does not validate with named-checkzone when validating zone leerdomain.local gives an error of: zone leerdomain.local/IN: NS 'ns.leerdomain.local' has no address records (A or AAAA)
zone leerdomain.local/IN: not loaded due to errors. *
Despite not validating bind9 starts without errors in /var/log/syslog
I've also configured a few of the windows machines on my network to have the static ip as specified in the lookup and reverse lookup config files.
i.e.
Using nslookup yields the following results:
C:\Users\leeand00>nslookup ns
Server: UnKnown
Address: 192.168.2.9
*** UnKnown can't find ns: Non-existent domain
C:\Users\leeand00>nslookup gw
Server: UnKnown
Address: 192.168.2.9
Name: gw.
Additionally trying to ping by name also fails on machines that are not the DNS Server.
Is there something wrong with my configuration of either the nameserver or the Windows Boxes that is keeping me from accessing other machines using names?
