Re: dnscache problems

  Hi,

Might not even be a dnscache related problem. Have you checked whether 
you can reach the other server on network level? Sometimes an old router 
with unpatched ECN bug or similar problems prevent you from accessing 
something from one place while it works from everywhere else.

For example:

# nmap -sU -P0 name.deloitte.com.au. -p 53

Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-22 10:52 CEST
Nmap scan report for name.deloitte.com.au. (134.159.157.13)
Host is up (0.38s latency).
rDNS record for 134.159.157.13: name.deloitte.com.au
PORT   STATE SERVICE
53/udp open  domain

Nmap done: 1 IP address (1 host up) scanned in 0.75 seconds

Regards
Bgs


On 09/22/2010 09:55 AM, richard lucassen wrote:
> hello list,
>
> I get more and more problems using dnscache. I've already started a
> thread a few months ago about this issue, and until now I entered the
> missing queries to an instance of tinydns, but it seems that this
> problem is growing:
>
> dnsqr mx newcastle.edu.au
> 15 newcastle.edu.au:
> timed out
>
> dnsqr mx deloitte.com.au
> 15 deloitte.com.au:
> timed out
>
> While other nameservers give me an answer:
>
> host -t mx deloitte.com.au ns2.kpn.net
> Using domain server:
> Name: ns2.kpn.net
> Address: 194.151.228.58#53
> Aliases:
>
> deloitte.com.au mail is handled by 200 deloitte.com.au.s7a2.psmtp.com.
> deloitte.com.au mail is handled by 300 deloitte.com.au.s7b1.psmtp.com.
> deloitte.com.au mail is handled by 400 deloitte.com.au.s7b2.psmtp.com.
> deloitte.com.au mail is handled by 100 deloitte.com.au.s7a1.psmtp.com.
>
> I know it's apparently not a dnscache fault, but the problem is rather
> annoying. Customers are complaining and they do not accept that they
> have to use gmail or other ways to contact these domains. I think I'm
> not the only one with this problem. How do others resolve this issue?
> (other options than installing PowerDNS or BIND)
>
> R.
>