It can also help to use the host <my.host.com> command instead of
nslookup or dig. It'll go through all the resolve.conf resolvers first
instead of just going straight to the DNS server for an answer. I've
gotten burned by using dig instead of the host command a few times and
it can be a real bummer.
~Caribe
On 02/10/2017 12:16 PM, Dimitri Maziuk wrote:
> On 02/10/2017 11:55 AM, Dan Langille wrote:
>
>> I suspect it's more likely to be an issue on one of the Bacula nodes
> in question (SD or FD) where there is a local DNS issue.
>
> I'm sure you checked already, but is there ns caching going on? It used
> to be a real pita on irix and is back again on osx. Once it gets into
> its little brain that host doesn't resolve, you get all sorts of fun
> behaviours with ssh failing (irix) while nslookup says all's peachy, or
> safari not connecting while ping works in terminal.
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
--
*Caribe Schreiber*
*Auction Harmony*
Phone: (612) 605-7301 x 105
Fax: (612) 605-7302
www.AuctionHarmony.com <http://www.auctionharmony.com>
Join Us! Like us on Facebook
<http://www.facebook.com/pages/Auction-Harmony/182442178467863> Follow
us on Twitter <http://www.twitter.com/auctionharmony>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
