Can not ping linux host via named (BIND) server

General support questions
Post Reply
mashkoorqadir
Posts: 70
Joined: 2012/06/27 07:55:01

Can not ping linux host via named (BIND) server

Post by mashkoorqadir » 2017/10/23 05:26:07

Hi guys,

I am facing a strange behavior by Bind9. I am working in mixed environment (windows and linux cleint and server machines). I have recently configured a Bind9 as a private/internal DNS server. It's working fine with windows clients but unable to ping the linux machines. However, nslookup does resolve the linux hosts. Following is the configuration files.


$ sudo cat /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";

$ sudo cat /etc/bind/named.options

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;
// };

//========================================================================
// If BIND logs error messages about the root key being expired,
// you will need to update your keys. See https://www.isc.org/bind-keys
//========================================================================
allow-query { localhost; 10.0.0.0/24; };
allow-transfer { localhost; 10.0.0.0/24; };
allow-recursion { localhost; 10.0.0.0/24; };
dnssec-validation auto;

auth-nxdomain no; # conform to RFC1035
listen-on-v6 { none; };
};


$ sudo cat /etc/bind/named.conf.local

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "test.local" {
type master;
file "/etc/bind/db.test.local";
};

zone "0.0.10.in-addr.arpa" {
type master;
file "/etc/bind/db.10";
};

Zone files details.

//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";

$ sudo cat /etc/bind/db.test.local

; BIND reverse data file for empty rfc1918 zone
;
; DO NOT EDIT THIS FILE - it is used for multiple zones.
; Instead, copy it, edit named.conf, and use that copy.
;
$TTL 86400

@ IN SOA ns1.test.local. root.test.local. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
86400 ) ; Negative Cache TTL
;
IN NS ns1.test.local
IN A 10.0.0.88
;A Records
ns1 IN A 10.0.0.88

;Linux host A record.
host1 IN A 10.0.0.80

;Windows host A record.
host2 IN A 10.0.0.81

$ sudo cat /etc/bind/db.10
; BIND reverse data file for empty rfc1918 zone
;
; DO NOT EDIT THIS FILE - it is used for multiple zones.
; Instead, copy it, edit named.conf, and use that copy.
;
$TTL 86400

@ IN SOA ns1.test.local. root.test.local. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
86400 ) ; Negative Cache TTL
;
IN NS ns1.test.local.
IN A 255.255.255.0
88 IN PTR test.local
80 IN PTR host1.
81 IN PTR host2.

Windows clients are communicating 100% perfect nslookup and ping both are fine but when I use to ping a linux client machine the message I get is

"C:\Users\userq>ping host1
Ping request could not find host host1. Please check the name and try again."

However nslookup resolve the name.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Can not ping linux host via named (BIND) server

Post by TrevorH » 2017/10/23 09:52:07

What's in /etc/resolv.conf?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

mashkoorqadir
Posts: 70
Joined: 2012/06/27 07:55:01

Re: Can not ping linux host via named (BIND) server

Post by mashkoorqadir » 2017/10/23 10:46:08

Thanks TrevorH,
In the windows just IP 10.0.0.88 (the IP address of the DNS server) and below two entries on linux clients.

$cat /etc/resolve.conf
# Generated by NetworkManager
search test.local
nameserver 10.0.0.88

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Can not ping linux host via named (BIND) server

Post by TrevorH » 2017/10/23 11:15:05

If the file you have is really called /etc/resolve.conf then it's named wrong and should be /etc/resolv.conf.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

mashkoorqadir
Posts: 70
Joined: 2012/06/27 07:55:01

Re: Can not ping linux host via named (BIND) server

Post by mashkoorqadir » 2017/10/23 11:49:36

My bad. It's a typo mistake. :shock:
TrevorH I have to reinstalled and reconfigured the bind now it's working but a new thing appeared. I can ping the hosts with fully qualified names eg. host1.test.local but can not ping host1. however windows machines I can ping like winpc1.

mashkoorqadir
Posts: 70
Joined: 2012/06/27 07:55:01

Re: Can not ping linux host via named (BIND) server

Post by mashkoorqadir » 2017/10/25 08:42:14

Thanks TrevorH,

Finally I have solved it. adding suffix in Network settings ====>Network Adapter properties=====> TCP/IPv 4 properties====> advance option in the bottom ====> DNS setting ====>select the option "Select these DNS suffixes (in Order)" and click add type the domain suffix in my case it is "test.local" apply and ok.

this is what I have done on my windows machines and the problem has gone away. :)

Post Reply