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