Can you think of any other configuration info that might cause this kind ofIt just sounds like a weird routing or firewall issue or something -
problem? I have covered everything that I can think of. Short of going in
and rebuilding Bind, which has the resolver libraries.
It doesn't seem likely that rebuilding bind will fix it since the bind that red hat ships has been working fine for all the redhat servers I know of, so there's most likely something else going on here.
Joe
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
