Discussion:
need two Domain in Named.local, but not resolv
Maurizio Caloro via bind-users
2018-10-07 13:12:06 UTC
Permalink
Please i need a little help, about DNS Bind Server. i need to replace the
old one < 115 >

Here i'an on the new one <92 >



Version

BIND 9.10.3-P4-Debian <id:ebd72b3>



I try that my DNS server 192.168.201.92 = MasterDNS Server resposible for 2
Network Ranges

1 192.168.201.

2 192.168.202.





Thanks for your feedback.

Regards



--



***@srvcar012:/etc/bind# ping srvcar002

PING srvcar002.carag.local (192.168.201.118) 56(84) bytes of data.

64 bytes from srvcar002.201.168.192.in-addr.arpa (192.168.201.118):
icmp_seq=1 ttl=128 time=0.733 ms



***@srvcar012:/etc/bind# ping srvcar001.carag.local

ping: srvcar001.carag.local: Name or service not known





***@srvcar012:/etc/bind# nslookup srvcar001

;; Got SERVFAIL reply from 192.168.201.92, trying next server

Server: 192.168.201.115

Address: 192.168.201.115#53



Name: srvcar001.carag.local

Address: 192.168.201.117





***@srvcar012:/etc/bind# nslookup srvcar001

;; Got SERVFAIL reply from 192.168.201.92, trying next server

Server: 192.168.201.115

Address: 192.168.201.115#53



Name: srvcar001.carag.local

Address: 192.168.201.117



***@srvcar012:/etc/bind# nslookup srvcar001.carag.local

;; Got SERVFAIL reply from 192.168.201.92, trying next server

Server: 192.168.201.115

Address: 192.168.201.115#53



Name: srvcar001.carag.local

Address: 192.168.201.117









----



With the 202 side, this arnt working



***@srvcar012:/etc/bind# ping srvolh001

ping: srvolh001: Name or service not known



***@srvcar012:/etc/bind# ping srvolh001.olh.local

ping: srvolh001.olh.local: Name or service not known



***@srvcar012:/etc/bind# nslookup srvolh001

;; Got SERVFAIL reply from 192.168.201.92, trying next server

Server: 192.168.201.92

Address: 192.168.201.92#53



** server can't find srvolh001: NXDOMAIN



And here this are correct, DNS Server ?



***@srvcar012:/etc/bind# nslookup srvolh001.olh.local

Server: 192.168.201.92

Address: 192.168.201.92#53



Name: srvolh001.olh.local

Address: 192.168.202.14





***@srvcar012:/etc/bind# nslookup 192.168.168.202.14

Server: 192.168.201.92

Address: 192.168.201.92#53



** server can't find 192.168.168.202.14: NXDOMAIN





***@srvcar012:/etc/bind# cat /etc/resolv.conf

domain carag.local

search carag.local.

nameserver 192.168.201.92

nameserver 192.168.201.115





and here my named.conf.local



***@srvcar012:/etc/bind# cat 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 "carag.local" {

type master;

file "/etc/bind/db.carag.local";

};

zone "201.168.192.in-addr.arpa" {

type master;

file "/etc/bind/db.reverse.carag.local";

};

zone "olh.local" {

type master;

file "/etc/bind/db.olh.local";

};

zone "202.168.192.in-addr.arpa" {

type master;

file "/etc/bind/db.reverse.olh.local";

};
Kevin Darcy
2018-10-08 22:40:30 UTC
Permalink
Offhand, it looks like 192.168.201.92 is giving SERVFAIL for anything in
the carag.local zone, but is fine for the olh.local zone. Did the zone load
properly? Look in the logs at startup or reload time.

But, the tools you're using, and how you're using them, makes
troubleshooting very difficult and confusing. First of all, why mix "ping"
troubleshooting with nslookup troubleshooting, if you're sure it's a DNS
problem (i.e. no complications with hosts-file entries, nsswitch.conf or
other such factors)? If it's a DNS issue, stick with DNS
troubleshooting/diagnostic tools

Secondly, without any options, nslookup won't give you an accurate picture
of what's being looked up, behind the scenes. At least use the "-debug"
option to nslookup, or, even better, use a real lookup troubleshooting tool
like "dig".

I'd also suggest targeting *specific* nameservers with your queries, rather
than just querying generically and allowing failover to occur on errors,
which muddies the situation. Single out each nameserver and determine what
it can resolve and what it cannot.

Always use fully-qualified names when troubleshooting, unless the specific
thing you're trying to troubleshoot is suffixing/searchlisting behavior by
the resolver.

As for the failure of the reverse lookup, try it with a 4-octet IP address
instead of 5.

- Kevin

On Sun, Oct 7, 2018 at 9:12 AM Maurizio Caloro via bind-users <
Please i need a little help, about DNS Bind Server
 i need to replace the
old one « 115 »
Here i’an on the new one «92 »
Version
BIND 9.10.3-P4-Debian <id:ebd72b3>
I try that my DNS server 192.168.201.92 = MasterDNS Server resposible for
2 Network Ranges
1 192.168.201.
2 192.168.202.
Thanks for your feedback.
Regards
--
PING srvcar002.carag.local (192.168.201.118) 56(84) bytes of data.
icmp_seq=1 ttl=128 time=0.733 ms
ping: srvcar001.carag.local: Name or service not known
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.115
Address: 192.168.201.115#53
Name: srvcar001.carag.local
Address: 192.168.201.117
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.115
Address: 192.168.201.115#53
Name: srvcar001.carag.local
Address: 192.168.201.117
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.115
Address: 192.168.201.115#53
Name: srvcar001.carag.local
Address: 192.168.201.117
----
With the 202 side, this arnt working
ping: srvolh001: Name or service not known
ping: srvolh001.olh.local: Name or service not known
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.92
Address: 192.168.201.92#53
** server can't find srvolh001: NXDOMAIN
And here this are correct, DNS Server ?
Server: 192.168.201.92
Address: 192.168.201.92#53
Name: srvolh001.olh.local
Address: 192.168.202.14
Server: 192.168.201.92
Address: 192.168.201.92#53
** server can't find 192.168.168.202.14: NXDOMAIN
domain carag.local
search carag.local.
nameserver 192.168.201.92
nameserver 192.168.201.115
and here my 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 "carag.local" {
type master;
file "/etc/bind/db.carag.local";
};
zone "201.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.reverse.carag.local";
};
zone "olh.local" {
type master;
file "/etc/bind/db.olh.local";
};
zone "202.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.reverse.olh.local";
};
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
unsubscribe from this list
bind-users mailing list
https://lists.isc.org/mailman/listinfo/bind-users
Sten Carlsen
2018-10-09 01:57:01 UTC
Permalink
Also be aware that .local is reserved.
--
Best regards
Sten Carlsen


No improvements come from shouting:
"MALE BOVINE MANURE!!!"
Offhand, it looks like 192.168.201.92 is giving SERVFAIL for anything in the carag.local zone, but is fine for the olh.local zone. Did the zone load properly? Look in the logs at startup or reload time.
But, the tools you're using, and how you're using them, makes troubleshooting very difficult and confusing. First of all, why mix "ping" troubleshooting with nslookup troubleshooting, if you're sure it's a DNS problem (i.e. no complications with hosts-file entries, nsswitch.conf or other such factors)? If it's a DNS issue, stick with DNS troubleshooting/diagnostic tools
Secondly, without any options, nslookup won't give you an accurate picture of what's being looked up, behind the scenes. At least use the "-debug" option to nslookup, or, even better, use a real lookup troubleshooting tool like "dig".
I'd also suggest targeting *specific* nameservers with your queries, rather than just querying generically and allowing failover to occur on errors, which muddies the situation. Single out each nameserver and determine what it can resolve and what it cannot.
Always use fully-qualified names when troubleshooting, unless the specific thing you're trying to troubleshoot is suffixing/searchlisting behavior by the resolver.
As for the failure of the reverse lookup, try it with a 4-octet IP address instead of 5.
- Kevin
Please i need a little help, about DNS Bind Server
 i need to replace the old one « 115 »
Here i’an on the new one «92 »
Version
BIND 9.10.3-P4-Debian <id:ebd72b3>
I try that my DNS server 192.168.201.92 = MasterDNS Server resposible for 2 Network Ranges
1 192.168.201.
2 192.168.202.
Thanks for your feedback.
Regards
--
PING srvcar002.carag.local (192.168.201.118) 56(84) bytes of data.
64 bytes from srvcar002.201.168.192.in-addr.arpa (192.168.201.118): icmp_seq=1 ttl=128 time=0.733 ms
ping: srvcar001.carag.local: Name or service not known
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.115
Address: 192.168.201.115#53
Name: srvcar001.carag.local
Address: 192.168.201.117
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.115
Address: 192.168.201.115#53
Name: srvcar001.carag.local
Address: 192.168.201.117
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.115
Address: 192.168.201.115#53
Name: srvcar001.carag.local
Address: 192.168.201.117
----
With the 202 side, this arnt working
ping: srvolh001: Name or service not known
ping: srvolh001.olh.local: Name or service not known
;; Got SERVFAIL reply from 192.168.201.92, trying next server
Server: 192.168.201.92
Address: 192.168.201.92#53
** server can't find srvolh001: NXDOMAIN
And here this are correct, DNS Server ?
Server: 192.168.201.92
Address: 192.168.201.92#53
Name: srvolh001.olh.local
Address: 192.168.202.14
Server: 192.168.201.92
Address: 192.168.201.92#53
** server can't find 192.168.168.202.14: NXDOMAIN
domain carag.local
search carag.local.
nameserver 192.168.201.92
nameserver 192.168.201.115
and here my 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 "carag.local" {
type master;
file "/etc/bind/db.carag.local";
};
zone "201.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.reverse.carag.local";
};
zone "olh.local" {
type master;
file "/etc/bind/db.olh.local";
};
zone "202.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.reverse.olh.local";
};
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users <https://lists.isc.org/mailman/listinfo/bind-users> to unsubscribe from this list
bind-users mailing list
https://lists.isc.org/mailman/listinfo/bind-users <https://lists.isc.org/mailman/listinfo/bind-users>
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users <https://lists.isc.org/mailman/listinfo/bind-users> to unsubscribe from this list
bind-users mailing list
https://lists.isc.org/mailman/listinfo/bind-users <https://lists.isc.org/mailman/listinfo/bind-users>
Loading...