Hello,
Strange problem resolving probsd.net.
Strange because it only happens with one of my networks.
Strange because it happens with unbound or dnscache (djbdns).
Strange because named (bind) can resolve it.
Log excerpt:
Not that strange - bind cannot resolve it from this one network
either. I didn;t realize my named.conf was set to forward first. When
I disable forwarding bind failed to resolve it as well.
I can successfully ping the name servers but just don't get DNS
replies from them. I'm suspecting some sort of IP blacklisting is in
effect.
Chris
It works fine on nssec.xelerance.com, which uses unbound plus all the
hardening settings, 0x20 and all:
host probsd.net 193.110.157.136
Using domain server:
Name: 193.110.157.136
Address: 193.110.157.136#53
Aliases:
probsd.net has address 66.93.16.108
probsd.net mail is handled by 20 zorak.probsd.net.
probsd.net mail is handled by 10 viisaus.probsd.net.
Paul
And it works fine on all of "my" other networks. But not my own 
I am on a cable network here and am now wondering if they're refusing
to answer queries to dynamic IP addresses (even though they reply to
pings).
Thanks,
Chris
Seems they were using a very old bogons (IANA unassigned IP blocks)
list that blocked replies from their DNS servers. All set now. Sorry
for the noise.
Chris