Kory Krofft <[EMAIL PROTECTED]> [2003:12:26:21:47:40-0500] scribed: <snip />
> using the host command, I can get the dmz host to resolve other names > and reverse lookup other ips but not it's own. I altered the > /etc/tinydns-private/root/data file to read: > > =localhost:127.0.0.1 > localhost:127.0.0.1:a > 1.0.0.127.in-addr.arpa:127.0.0.1:a > kroffts.home:127.0.0.1:a > 1.168.192.in-addr.arpa:127.0.0.1:a > =markii.kroffts.home:192.168.1.254 > =coventry.kroffts.home:192.168.1.1 > =mail.kroffts.dmz:192.168.10.1 > @kroffts.dmz:192.168.10.1:mail.kroffts.dmz > @10.168.192.in-addr.arpa::mail.kroffts.dmz <snip /> > I think qmail is working OK now. Which takes us back to the dns > issues. I have done my best to configure the dns entries thae way I > think the documentation says but I still have a good 1 to 1.5 minute > delay in the response of the mail server to a local mail client. I ran > another set of tcpdump data for grins but it looks pretty much the > same as last time to me. <snip /> > 21:25:30.591328 192.168.10.1.64715 > 192.168.1.254.53: 61116+ PTR? > 1.10.168.192.in-addr.arpa. (43) (DF) > 0x0000 4500 0047 f612 4000 4011 b743 c0a8 0a01 [EMAIL > PROTECTED]@..C.... > 0x0010 c0a8 01fe fccb 0035 0033 398e eebc 0100 .......5.39..... > 0x0020 0001 0000 0000 0000 0131 0231 3003 3136 .........1.10.16 > 0x0030 3803 3139 3207 696e 2d61 6464 7204 6172 8.192.in-addr.ar > 0x0040 7061 0000 0c00 01 pa..... > 21:25:33.622390 192.168.10.1.59258 > 192.168.10.254.53: 28701+ PTR? > 1.10.168.192.in-addr.arpa. (43) (DF) > 0x0000 4500 0047 e557 4000 4011 befe c0a8 0a01 [EMAIL > PROTECTED]@....... > 0x0010 c0a8 0afe e77a 0035 0033 c47e 701d 0100 .....z.5.3.~p... > 0x0020 0001 0000 0000 0000 0131 0231 3003 3136 .........1.10.16 > 0x0030 3803 3139 3207 696e 2d61 6464 7204 6172 8.192.in-addr.ar > 0x0040 7061 0000 0c00 01 pa..... > 21:25:33.622624 192.168.10.254 > 192.168.10.1: icmp: 192.168.10.254 udp port 53 > unreachable [tos 0xc0] > 0x0000 45c0 0063 dc44 0000 4001 0746 c0a8 0afe [EMAIL PROTECTED] > 0x0010 c0a8 0a01 0303 9391 0000 0000 4500 0047 ............E..G > 0x0020 e557 4000 4011 befe c0a8 0a01 c0a8 0afe [EMAIL > PROTECTED]@........... > 0x0030 e77a 0035 0033 c47e 701d 0100 0001 0000 .z.5.3.~p....... > 0x0040 0000 0000 0131 0231 3003 3136 3803 3139 .....1.10.168.19 > 0x0050 3207 696e 2d61 6464 7204 6172 7061 0000 2.in-addr.arpa.. > 0x0060 0c00 01 ... <snip /> Clearly, 192.168.10/24 is not resolvable via dns. As Lynn points out, dnscache on your router may function best at 127.0.0.0, and tinydns at 192.168.1.254 _and_ 192.168.10.254. However, as you undoubtedly know, tinydns can bind to only one (1) interface. Therefore, you will need to run a _second_ instance of tinydns, one authoritative for 192.168.1/24 and the other authoritative for 192.168.10/24. hth -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --
pgp00000.pgp
Description: PGP signature
