Re: I can dig a domain but named won't resolve it.

Niall, Thanks very much for linking me to that article. It turns out extremehosting.ca blocks incoming connections on port 53 which also originate on 53. I've disabled the outgoing source port restrictions and all is well again. Also, securing against a cache poisoning vulnerability is a nic

Re: I can dig a domain but named won't resolve it.

On 22/09/11 17:34, Keith Burgoyne wrote: > Here's the named.conf file from my name server. The meat of your configuration seems to be in the (hidden) included files. Forcing the source of your outgoing queries always to be port 53 is a well-documented bad idea. Yo

Re: I can dig a domain but named won't resolve it.

Here's the named.conf file from my name server. It's pretty basic, and creates a view for internal use, and external. It hosts internal DNS for local machines that's used on two internal networks, and external DNS for our hosted domains, recursive lookups from our public IP block, etc. // {{{

Re: I can dig a domain but named won't resolve it.

On 22/09/11 01:02, Keith Burgoyne wrote: > Any advice would be massively appreciated. The +trace operation which you say is failing for you works from my network -- at home, where I have to use NAT. It looks as if either your network or the nameserver you're using

I can dig a domain but named won't resolve it.

Hi there, I have a potentially BIND related problem and I'm positively stuck. I've posted this question on Server Fault (http://serverfault.com/questions/306997/cant-seem-to-resolve-domain-but-can-dig-it) with little exposure. The jist of it is: My name server (24.222.7.12) refuses to resolv