Re: Resolving issue on specific domain

[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 @localhost domainname.


On 15.07.16 09:56, Chris Buxton wrote:

You should not rely on the order of entries in resolv.conf. Servers will
not always be queried in the listed order.  This is
implementation-specific.


got more info? looks liker some implementations don't support
preferred/fallback mechanism.


If you have two servers that will answer differently to the same query,
then you shouldn't have those two servers in resolv.conf.  Aim for a
consistent (and consistently useful) result.


yes, why to have fallback when you may not have it...

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
BSE = Mad Cow Desease ... BSA = Mad Software Producents Desease
___
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: Resolving issue on specific domain

[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 dig @localhost domainname.

You should not rely on the order of entries in resolv.conf. Servers will not 
always be queried in the listed order. This is implementation-specific.

If you have two servers that will answer differently to the same query, then 
you shouldn't have those two servers in resolv.conf. Aim for a consistent (and 
consistently useful) result.

Regards,
Chris
___
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: Resolving issue on specific domain

[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 domainame localhost -> Resolving properly


and, please remove the parts that are not important, don't sent useless crap
to mailing list.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
How does cat play with mouse? cat /dev/mouse
___
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: Resolving issue on specific domain

[Daniel Dawalibi]

Yes

Dig domainname -> Server failed
Dig domainname ServerIP -> Server failed
Dig domainame localhost -> Resolving properly

-Original Message-
From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of
Matus UHLAR - fantomas
Sent: 15 July, 2016 1:02 PM
To: bind-users@lists.isc.org
Subject: Re: Resolving issue on specific domain

On 15.07.16 12:05, Daniel Dawalibi wrote:
>To: 'Matus UHLAR - fantomas' <uh...@fantomas.sk>, 
>bind-users@lists.isc.org

please avoid personal replies. use list-reply whenever possible.

>I already did it as per below output of resolv.conf but problem persists.

do you want to say, even if you run "dig domainname" without @localhost, the
dig sends query to  194.126.10.18 ?

>/etc/resolv.conf
># Generated by NetworkManager
>nameserver 127.0.0.1
>nameserver 194.126.10.18

>-Original Message-
>From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of 
>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 public IP address.
>>
>>If you try to resolve the domain using either dig or nslookup you will 
>>not get any result whereas if you specify @localhost you will get the 
>>answer
>[...]
>
>>#dig @localhost soa domainname
>[...]
>
>>#dig soa domainname
>>;; SERVER: 194.126.10.18#53(194.126.10.18)
>
>as you can see, in the latter example it's not the localhost 
>(127.0.0.1) but
>194.126.10.18 that gives you answer. That means, 194.126.10.18 does not 
>know the "domainname"
>
>you must add localhost to resolv.conf as first nameserver to get 
>answers from it by default.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Fucking windows! Bring Bill Gates! (Southpark the movie)
___
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

___
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: Resolving issue on specific domain

[Matus UHLAR - fantomas]

On 15.07.16 12:05, Daniel Dawalibi wrote:

To: 'Matus UHLAR - fantomas' <uh...@fantomas.sk>, bind-users@lists.isc.org


please avoid personal replies. use list-reply whenever possible.


I already did it as per below output of resolv.conf but problem persists.


do you want to say, even if you run "dig domainname" without @localhost, the
dig sends query to  194.126.10.18 ?


/etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1
nameserver 194.126.10.18



-Original Message-
From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of
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 public IP address.

If you try to resolve the domain using either dig or nslookup you will
not get any result whereas if you specify @localhost you will get the
answer

[...]


#dig @localhost soa domainname

[...]


#dig soa domainname
;; SERVER: 194.126.10.18#53(194.126.10.18)


as you can see, in the latter example it's not the localhost (127.0.0.1) but
194.126.10.18 that gives you answer. That means, 194.126.10.18 does not know
the "domainname"

you must add localhost to resolv.conf as first nameserver to get answers
from it by default.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Fucking windows! Bring Bill Gates! (Southpark the movie)
___
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: Resolving issue on specific domain

[Daniel Dawalibi]

Hello

I already did it as per below output of resolv.conf but problem persists.


/etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1
nameserver 194.126.10.18


Regards
Daniel

-Original Message-
From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of
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 public IP address.
>
>If you try to resolve the domain using either dig or nslookup you will 
>not get any result whereas if you specify @localhost you will get the 
>answer
[...]

>#dig @localhost soa domainname
[...]

>#dig soa domainname
>;; SERVER: 194.126.10.18#53(194.126.10.18)

as you can see, in the latter example it's not the localhost (127.0.0.1) but
194.126.10.18 that gives you answer. That means, 194.126.10.18 does not know
the "domainname"

you must add localhost to resolv.conf as first nameserver to get answers
from it by default.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Emacs is a complicated operating system without good text editor.
___
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

___
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: Resolving issue on specific domain

[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 result whereas if you specify @localhost you will get the answer

[...]


#dig @localhost soa domainname

[...]


#dig soa domainname
;; SERVER: 194.126.10.18#53(194.126.10.18)


as you can see, in the latter example it's not the localhost (127.0.0.1) but
194.126.10.18 that gives you answer. That means, 194.126.10.18 does not know
the "domainname"

you must add localhost to resolv.conf as first nameserver to get answers
from it by default.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Emacs is a complicated operating system without good text editor.
___
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: Resolving issue on specific domain

[Barry Margolin]

In article <mailman.63.1468332823.15653.bind-us...@lists.isc.org>,
 Daniel Dawalibi <daniel.dawal...@idm.net.lb> 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 you will not
> get any result whereas if you specify @localhost you will get the answer
> 
> Do you have any explanation about this behavior and what should be done to
> fix this issue?

This suggests that the problem is that the domain isn't delegated to 
your server. If you don't use @localhost, the query goes to your normal 
resolver, which follows the delegations from the root, and they don't 
lead to your server.

-- 
Barry Margolin
Arlington, MA
___
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: Resolving issue on specific domain

[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-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Resolving issue on specific domain

[Daniel Dawalibi]

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 you will not
get any result whereas if you specify @localhost you will get the answer

Do you have any explanation about this behavior and what should be done to
fix this issue?

Examples:

 

#dig @localhost soa domainname

 

; <<>> DiG 9.9.4-P1 <<>> @localhost soa domainname

; (2 servers found)

;; global options: +cmd

;; Got answer:

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

;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; WARNING: recursion requested but not available

 

;; OPT PSEUDOSECTION:

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

;; QUESTION SECTION:

;domainname.IN  SOA

 

;; ANSWER SECTION:

domainname. 86400   IN  SOA xx.idm.net.lb. y.domainname.
1468329403 10800 3600 604800 10800

 

;; AUTHORITY SECTION:

domainname. 86400   IN  NS  xx.idm.net.lb.

domainname. 86400   IN  NS  yy.idm.net.lb.

 

 

 

#dig soa domainname

 

 

; <<>> DiG 9.9.4-P1 <<>> soa domainname

;; global options: +cmd

;; Got answer:

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

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

 

;; OPT PSEUDOSECTION:

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

;; QUESTION SECTION:

;domainname.IN  SOA

 

;; Query time: 0 msec

;; SERVER: 194.126.10.18#53(194.126.10.18)

;; WHEN: Tue Jul 12 17:09:23 EEST 2016

 

 

 

Regards

Daniel

___
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