Discussion about Daniel Bernstein's DNS

soc | 4 Jan 2009 12:27

Re: name resolution problem

At 21:28 03/01/09 +0100, Stefaan A Eeckels wrote:
>On Thu, 01 Jan 2009 21:14:23 +0100
>Lou Hevly <xyz <at> visca.com> wrote:
>
> > After 3 or 4 minutes, it responds correctly again.
>
>When you run the dnsq query against the LAN address (192.168.2.103),
>i.e.
>
>$ dnsq a petonets.com 192.168.2.103 | grep answer
>
>do you get the same time-out problems?

No.

>It could be that the router is to blame, e.g. it might consider the
>repeated queries to be an attack of sorts.

I think this is it.  After reading Pete Ehlke's response I googled 
"reply from unexpected source" and eventually found a user with the 
same ISP as me (ya.com in Spain) who found that after the first query, 
the router would respond on successively higher port numbers.

Since typing the above, I have read Pete Ehlke's post which confirms 
this is precisely what is happening. Would this be a router problem or 
something ya.com, my ISP, was doing?

Thanks to both you and Pete for your input.

--

--

(Continue reading)

headers

Daryl Tester | 4 Jan 2009 14:36

Re: name resolution problem

soc <at> visca.com wrote:

> Since typing the above, I have read Pete Ehlke's post which confirms 
> this is precisely what is happening. Would this be a router problem or 
> something ya.com, my ISP, was doing?

Could be either.  Short of opening a support ticket with your ISP, one
method that comes to mind would be to put your router into bridged mode
(if possible) so that you know the packets are leaving your part of the
network "unmolested".  This would at least give you the ability to sniff
the packets as they left your network.

--

-- 
Regards,
  Daryl Tester

"Oh Christmas tree, oh Christmas tree!  From hell's heart I stab at thee."
  -- A very Kaaahn! Christmas