restarting bind fixes some resolution issues

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

restarting bind fixes some resolution issues

Dario Corti
Hi, I occasionally have issues updating some packages, with the package
manager saying that it cannot resolve deb.nodesource.com. I'm using
1:9.9.5.dfsg-9+deb8u11 and I verified that a bind restart fixes the
problem every time (even if technically the domain CAN be resolved also
before the restart).

I issued a dig before and after the restart and it does report something
different, but I'm unable to understand it, so I wonder if anyone can
suggest a possible reason for this.

Before: https://pastebin.com/7qZUmPKA
After: https://pastebin.com/U0DUhE20

--

[hidden email]
[hidden email]
OpenPGP Key: 752A92A1

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: restarting bind fixes some resolution issues

Matus UHLAR - fantomas
On 09.07.17 14:36, Dario Corti wrote:
>Hi, I occasionally have issues updating some packages, with the
>package manager saying that it cannot resolve deb.nodesource.com. I'm
>using 1:9.9.5.dfsg-9+deb8u11 and I verified that a bind restart fixes
>the problem every time (even if technically the domain CAN be
>resolved also before the restart).

https://mxtoolbox.com/SuperTool.aspx?action=dns%3adeb.nodesource.com&run=toolpage
http://dnscheck.pingdom.com/?domain=deb.nodesource.com

both checkers report errors...

>I issued a dig before and after the restart and it does report
>something different, but I'm unable to understand it, so I wonder if
>anyone can suggest a possible reason for this.
>
>Before: https://pastebin.com/7qZUmPKA
>After: https://pastebin.com/U0DUhE20

i don't see any difference here, both cases report deb.nodesource.com to be
a CNAME to d2buw04m05mirl.cloudfront.net - maybe you should look up that one
next time problem appears.

--
Matus UHLAR - fantomas, [hidden email] ; 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.
I intend to live forever - so far so good.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: restarting bind fixes some resolution issues

Sten Carlsen

> On 9 Jul 2017, at 17:04, Matus UHLAR - fantomas <[hidden email]> wrote:
>
> On 09.07.17 14:36, Dario Corti wrote:
>> Hi, I occasionally have issues updating some packages, with the package manager saying that it cannot resolve deb.nodesource.com. I'm using 1:9.9.5.dfsg-9+deb8u11 and I verified that a bind restart fixes the problem every time (even if technically the domain CAN be resolved also before the restart).
>
> https://mxtoolbox.com/SuperTool.aspx?action=dns%3adeb.nodesource.com&run=toolpage
> http://dnscheck.pingdom.com/?domain=deb.nodesource.com
>
> both checkers report errors...
>
>> I issued a dig before and after the restart and it does report something different, but I'm unable to understand it, so I wonder if anyone can suggest a possible reason for this.
>>
>> Before: https://pastebin.com/7qZUmPKA
>> After: https://pastebin.com/U0DUhE20
>
> i don't see any difference here, both cases report deb.nodesource.com to be
> a CNAME to d2buw04m05mirl.cloudfront.net - maybe you should look up that one
> next time problem appears.
The sequence of answers is different, this is not a difference as such, DNS does not normally use a specific sequence in the answers.

You should compare the answers so you verify that all the same records are present, sequence is of no meaning.

>
> --
> Matus UHLAR - fantomas, [hidden email] ; 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.
> I intend to live forever - so far so good. _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
>
> bind-users mailing list
> [hidden email]
> 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
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: restarting bind fixes some resolution issues

Sam Wilson
In reply to this post by Dario Corti
On 2017-07-09 15:04:53 +0000, Matus UHLAR - fantomas said:

> On 09.07.17 14:36, Dario Corti wrote:
>> Hi, I occasionally have issues updating some packages, with the package
>> manager saying that it cannot resolve deb.nodesource.com. I'm using
>> 1:9.9.5.dfsg-9+deb8u11 and I verified that a bind restart fixes the
>> problem every time (even if technically the domain CAN be resolved also
>> before the restart).
>
> https://mxtoolbox.com/SuperTool.aspx?action=dns%3adeb.nodesource.com&run=toolpage 
>
> http://dnscheck.pingdom.com/?domain=deb.nodesource.com
>
> both checkers report errors...
>
>> I issued a dig before and after the restart and it does report
>> something different, but I'm unable to understand it, so I wonder if
>> anyone can suggest a possible reason for this.
>>
>> Before: https://pastebin.com/7qZUmPKA
>> After: https://pastebin.com/U0DUhE20
>
> i don't see any difference here, both cases report deb.nodesource.com to be
> a CNAME to d2buw04m05mirl.cloudfront.net - maybe you should look up that one
> next time problem appears.

What's different is the authority section.  In neither case does it
provide the expected NS records for nodesource.com or cloudfront.net,
or even NS records for d2buw04m05mirl.cloudfront.net, which my servers
have cached.  There is something odd about the configuration.

Sam

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Loading...