Re: name resolution problem

On Sat, Jan 3, 2009 at 2:28 PM, Stefaan A Eeckels <[email protected]>wrote:

> On Thu, 01 Jan 2009 21:14:23 +0100
> Lou Hevly <[email protected]> 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?
>
> It could be that the router is to blame, e.g. it might consider the
> repeated queries to be an attack of sorts.
>

His nat/pat is broken; it's incrementing the source port on the way out.

pde@Braeburn:[~]$ dig @ns2.petonets.com petonets.com ns

; <<>> DiG 9.4.2-P2 <<>> @ns2.petonets.com petonets.com ns
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20937
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;petonets.com.                  IN      NS

;; ANSWER SECTION:
petonets.com.           259200  IN      NS      ns1.petonets.com.
petonets.com.           259200  IN      NS      ns2.petonets.com.

;; ADDITIONAL SECTION:
ns1.petonets.com.       86400   IN      A       84.78.232.127
ns2.petonets.com.       86400   IN      A       84.78.232.127

;; Query time: 209 msec
;; SERVER: 84.78.232.127#53(84.78.232.127)
;; WHEN: Sat Jan  3 17:08:18 2009
;; MSG SIZE  rcvd: 98


pde@Braeburn:[~]$ dig @ns2.petonets.com petonets.com ns
;; reply from unexpected source: 84.78.232.127#54, expected 84.78.232.127#53
;; reply from unexpected source: 84.78.232.127#54, expected 84.78.232.127#53
;; reply from unexpected source: 84.78.232.127#54, expected 84.78.232.127#53

; <<>> DiG 9.4.2-P2 <<>> @ns2.petonets.com petonets.com ns
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached


pde@Braeburn:[~]$ dig @ns2.petonets.com petonets.com ns
;; reply from unexpected source: 84.78.232.127#55, expected 84.78.232.127#53
;; reply from unexpected source: 84.78.232.127#55, expected 84.78.232.127#53
;; reply from unexpected source: 84.78.232.127#55, expected 84.78.232.127#53

; <<>> DiG 9.4.2-P2 <<>> @ns2.petonets.com petonets.com ns
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached

pde@Braeburn:[~]$ dig @ns2.petonets.com petonets.com ns
;; reply from unexpected source: 84.78.232.127#56, expected 84.78.232.127#53
;; reply from unexpected source: 84.78.232.127#56, expected 84.78.232.127#53
;; reply from unexpected source: 84.78.232.127#56, expected 84.78.232.127#53

; <<>> DiG 9.4.2-P2 <<>> @ns2.petonets.com petonets.com ns
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached