That does not seems to be the problem
This is the output of tcpdump
11:52:11.322230 IP 192.168.1.1.1076 > 198.9.200.226.53: 31195+ A?
www.yahoo.com. (31)
0x0000: 0016 3e7a 99db 0019 aac2 acae 0800 4500 ..>z..........E.
0x0010: 003b c2d1 0000 7d11 2a4b c0a8 0101 c609 .;....}.*K......
0x0020: c8e2 0434 0035 0027 69b5 79db 0100 0001 ...4.5.'i.y.....
0x0030: 0000 0000 0000 0377 7777 0579 6168 6f6f .......www.yahoo
0x0040: 0363 6f6d 0000 0100 01 .com.....
11:52:16.563891 IP 192.168.1.1.4702 > 198.9.200.226.53: 54746+ A?
au.download.windowsupdate.com. (47)
0x0000: 0016 3e7a 99db 0019 aac2 acae 0800 4500 ..>z..........E.
0x0010: 004b c333 0000 7d11 29d9 c0a8 0101 c609 .K.3..}.).......
0x0020: c8e2 125e 0035 0037 8e90 d5da 0100 0001 ...^.5.7........
0x0030: 0000 0000 0000 0261 7508 646f 776e 6c6f .......au.downlo
0x0040: 6164 0d77 696e 646f 7773 7570 6461 7465 ad.windowsupdate
0x0050: 0363 6f6d 0000 0100 01 .com.....
I would have expected 198.9.200.249 > 198.9.200.226.53 but got
192.168.1.1.1076 > 198.9.200.226.53
-----Oorspronkelijk bericht-----
Van: Jeff King [mailto:peff@peff.net]
Verzonden: vrijdag 11 mei 2007 11:36
Aan: joeri Belis
Onderwerp: Re: can't use dnscache behinde a router
On Fri, May 11, 2007 at 11:31:09AM +0200, joeri Belis wrote:
> I have no /service/dnscache/root/servers/198.9.200.249 file on the
dnscache
> setup. Is this an empty file? And what is the effect on the NAT?
The presence of that file (which can be empty) tells dnscache that the
IP address 198.9.200.249 is allowed to make queries.
When the machines are on the same segment, the client IP address appears
(from dnscache's perspective) to be 192.168.1.1. However, when it is
_outside_ the NAT, the client's IP appears to be the public side of the
router (198.9.200.249). You can confirm this by doing a tcpdump on the
Linux box.
The problem is that you have presumably have not told dnscache about the
router's public IP.
-Peff
|