Date: Fri, 1 Oct 1999 16:06:30 +0100 From: "Richard Morte" <richard@sinclairassoc.force9.co.uk> To: <FreeBSD-questions@FreeBSD.ORG> Subject: DNS Slave seeks DNS Master - please be gentle Message-ID: <LOBBKEGHCNEHPLGFIAKPEENKCAAA.richard@sinclairassoc.force9.co.uk>
next in thread | raw e-mail | index | archive | help
Hi, Can anyone help me untangle the DNS/PPP mess I'm in? I have a local DNS configured and it appears to work OK. I can resolve addresses to names and names to addresses - but only for hosts on the local network (192.168.120). Anything in the outside world times out. SAMBA also works OK and I can share files across the Win network. I have user-ppp configured. It used to dial out (often, if anything, without obvious provocation) in -auto -alias mode, but now it seems resolutely to want to remain quiet. I can force a dial out in 'interactive' mode OK; it's just the auto mode that doesn't want to play ball. I have the dawning conviction that the unprompted dial outs were due to DNS updating from the root servers. Ditto when Netscape starts up, tho' what it is looking up, I never found out. Now in my hacking at DNS/PPP I seem to have unlinked what was formerly linked -permanently. I suspect the problem is the default gateway. (Single FreeBSD box connected to multiple Win machines). I noticed during the boot up sequence the following msgs: Doing initial network setup: hostname pn0: flags=8843<UP,BROADCAST,...etc... <snip> => ifconfig: ioctl (SIOCAIFADDR): Destination address required tun0: flags=80105<POINTOPOINT,MULTICAST> mtu 1500 ...etc => add net default: gateway sparky.at.home ...etc The first highlighted entry is clearly up the creek (I have no idea how it got in there); the gateway entry is probably OK. A tcpdump reveals the following: # tcpdump Oct 1 15:30:06 sparky /kernel: pn0: promiscuous mode enabled tcpdump: listening on pn0 15:18:00.011052 sparky.at.home.iad3 > 192.36.148.17.domain: 9618 (42) 15:18:00.011505 sparky.at.home.iad3 > 192.5.5.241.domain: 9621 (43) 15:18:00.245881 sparky.at.home.iad3 > 202.12.27.33.domain: 9622 (44) 15:18:01.011087 sparky.at.home.iad3 > 128.8.10.90.domain: 9619 (42) 15:18:01.011545 sparky.at.home.iad3 > 192.112.36.4.domain: 9616 (43) 15:18:03.011092 sparky.at.home.iad3 > 202.12.27.33.domain: 9617 (43) 15:18:03.011545 sparky.at.home.iad3 > 193.0.14.129.domain: 9610 NS? . (17) ^C # So I guess that DNS *IS* doing it's stuff and trying to update the cache after a reboot, only that the packets get to the Ethernet interface pn0, but never to tun0. This helps explain why nslookup times out for www domains. But I haven't a clue as to what's causing it. Here's the output of netstat -rn after a reboot: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.120.1 UGSc 13 0 pn0 10.0.0.2 10.0.0.1 UH 0 0 tun0 127.0.0.1 127.0.0.1 UH 0 24 lo0 192.168.120 link#1 UC 0 0 pn0 192.168.120.1 0:a0:cc:54:1d:7 UHLW 14 0 lo0 As they say in Yorkshire, "Summat's up". Can anyone tell me what's broken? Many thanks ric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LOBBKEGHCNEHPLGFIAKPEENKCAAA.richard>