unable to resolve evisa.dgdi.ga FQDN

2018-10-08 Thread Kuo Loon Pang via bind-users
Recently, using caching DNS (named 9.9.4) unable to resolve any *.ga
domain. Able to resolve any domain without any issue. named.ca version
update is   September 11, 2018

Below is dig result using google DNS and own cache DNS.



[root@localhost ~]# dig evisa.dgdi.ga @8.8.8.8



; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> evisa.dgdi.ga @8.8.8.8

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56355

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1



;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;evisa.dgdi.ga. IN  A



;; ANSWER SECTION:

evisa.dgdi.ga.  17653   IN  A   129.35.173.151



;; Query time: 11 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Tue Oct 09 10:15:08 +08 2018

;; MSG SIZE  rcvd: 58



[root@localhost ~]# dig evisa.dgdi.ga @127.0.0.1

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> evisa.dgdi.ga @127.0.0.1

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 53018

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1



;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 4096

;; QUESTION SECTION:

;evisa.dgdi.ga. IN  A



;; Query time: 0 msec

;; SERVER: 127.0.0.1#53(127.0.0.1)

;; WHEN: Tue Oct 09 10:16:00 +08 2018

;; MSG SIZE  rcvd: 42



How to resolve domain *.ga? Kindly advise.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: need two Domain in Named.local, but not resolv

2018-10-08 Thread Sten Carlsen
Also be aware that .local is reserved.

-- 
Best regards 
Sten Carlsen 


No improvements come from shouting: 
"MALE BOVINE MANURE!!!" 

On 9 Oct 2018, at 00.40, Kevin Darcy mailto:kevin.da...@fcagroup.com>> wrote:

> 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 
> mailto:bind-users@lists.isc.org>> wrote:
> 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 
> 
>  
> 
> I try that my DNS server 192.168.201.92 = MasterDNS Server resposible for 2 
> Network Ranges
> 
> 1192.168.201.
> 
> 2192.168.202.
> 
>  
> 
>  
> 
> Thanks  for your feedback.
> 
> Regards
> 
>  
> 
> --
> 
>  
> 
> root@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
> 
>  
> 
> root@srvcar012:/etc/bind# ping srvcar001.carag.local
> 
> ping: srvcar001.carag.local: Name or service not known
> 
>  
> 
>  
> 
> root@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
> 
>  
> 
>  
> 
> root@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
> 
>  
> 
> root@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
> 
>  
> 
> root@srvcar012:/etc/bind# ping srvolh001
> 
> ping: srvolh001: Name or service not known
> 
>  
> 
> root@srvcar012:/etc/bind# ping srvolh001.olh.local
> 
> ping: srvolh001.olh.local: Name or service not known
> 
>  
> 
> root@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 ?
> 
>  
> 
> root@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
> 
>  
> 
>  
> 
> root@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
> 
>  
> 
>  
> 
> root@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
> 
>  
> 
> root@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" 

Re: need two Domain in Named.local, but not resolv

2018-10-08 Thread Kevin Darcy
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 <
bind-users@lists.isc.org> wrote:

> 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 
>
>
>
> I try that my DNS server 192.168.201.92 = MasterDNS Server resposible for
> 2 Network Ranges
>
> 1192.168.201.
>
> 2192.168.202.
>
>
>
>
>
> Thanks  for your feedback.
>
> Regards
>
>
>
> --
>
>
>
> root@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
>
>
>
> root@srvcar012:/etc/bind# ping srvcar001.carag.local
>
> ping: srvcar001.carag.local: Name or service not known
>
>
>
>
>
> root@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
>
>
>
>
>
> root@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
>
>
>
> root@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
>
>
>
> root@srvcar012:/etc/bind# ping srvolh001
>
> ping: srvolh001: Name or service not known
>
>
>
> root@srvcar012:/etc/bind# ping srvolh001.olh.local
>
> ping: srvolh001.olh.local: Name or service not known
>
>
>
> root@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 ?
>
>
>
> root@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
>
>
>
>
>
> root@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
>
>
>
>
>
> root@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
>
>
>
> root@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";
>
> };
>
>
>
>
> ___
>