Re: Resolving issue on specific domain

2016-07-16 Thread Matus UHLAR - fantomas
On 15.07.16 14:05, Daniel Dawalibi wrote: Dig domainname -> Server failed On Jul 15, 2016, at 8:48 AM, Matus UHLAR - fantomas wrote: please show us output of it. when 127.0.0.1 is first in /etc/resolv.conf, dig should contact localhost first, and the result should be the same as dig @localho

Re: Resolving issue on specific domain

2016-07-15 Thread Chris Buxton
On Jul 15, 2016, at 8:48 AM, Matus UHLAR - fantomas wrote: > > On 15.07.16 14:05, Daniel Dawalibi wrote: >> Dig domainname -> Server failed > > please show us output of it. > when 127.0.0.1 is first in /etc/resolv.conf, dig should contact localhost > first, and the result should be the same as d

Re: Resolving issue on specific domain

2016-07-15 Thread Matus UHLAR - fantomas
On 15.07.16 14:05, Daniel Dawalibi wrote: Dig domainname -> Server failed please show us output of it. when 127.0.0.1 is first in /etc/resolv.conf, dig should contact localhost first, and the result should be the same as dig @localhost domainname. Dig domainname ServerIP -> Server failed Dig

RE: Resolving issue on specific domain

2016-07-15 Thread Daniel Dawalibi
ind-users@lists.isc.org Subject: Re: Resolving issue on specific domain On 15.07.16 12:05, Daniel Dawalibi wrote: >To: 'Matus UHLAR - fantomas' , >bind-users@lists.isc.org please avoid personal replies. use list-reply whenever possible. >I already did it as per below output of reso

Re: Resolving issue on specific domain

2016-07-15 Thread Matus UHLAR - fantomas
Sent: 15 July, 2016 11:58 AM To: bind-users@lists.isc.org Subject: Re: Resolving issue on specific domain On 12.07.16 17:13, Daniel Dawalibi wrote: We are facing a weird issue while resolving a specific domain name from our authoritative DNS server running on BIND 9.10.4-P1 Server has only one pu

RE: Resolving issue on specific domain

2016-07-15 Thread Daniel Dawalibi
UHLAR - fantomas Sent: 15 July, 2016 11:58 AM To: bind-users@lists.isc.org Subject: Re: Resolving issue on specific domain On 12.07.16 17:13, Daniel Dawalibi wrote: >We are facing a weird issue while resolving a specific domain name from >our authoritative DNS server running on BIND 9.1

Re: Resolving issue on specific domain

2016-07-15 Thread Matus UHLAR - fantomas
On 12.07.16 17:13, Daniel Dawalibi wrote: We are facing a weird issue while resolving a specific domain name from our authoritative DNS server running on BIND 9.10.4-P1 Server has only one public IP address. If you try to resolve the domain using either dig or nslookup you will not get any resu

Re: Resolving issue on specific domain

2016-07-12 Thread Barry Margolin
In article , Daniel Dawalibi wrote: > Hello > > > > We are facing a weird issue while resolving a specific domain name from our > authoritative DNS server running on BIND 9.10.4-P1 > > Server has only one public IP address. > > If you try to resolve the domain using either dig or nslookup

Re: Resolving issue on specific domain

2016-07-12 Thread Phil Mayers
On 12/07/16 15:13, Daniel Dawalibi wrote: #dig @localhost soa domainname Don't hide the domain. It makes it impossible for people to help you. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-use