On 24 Sep 2002, 23:42:10, Frans Pop wrote: > I have checked everything again with your suggestions, but when I do > "sudo -u mail exim -q" (to emulate crontab) I still get the following in > querylog on my nameserver: > XX+/10.19.66.21/galadriel.fjphome.nl/AAAA/IN > XX+/10.19.66.21/galadriel/AAAA/IN > > I also get the second line when I do "dig galadriel -t AAAA". Could it be > Exim does not request "galadriel" but looks explicitly for "galadriel."? > I get nothing in querylog when I do "ping galadriel". So it may also be that > ping gets resolved locally (through files), but dig and exim go directly to > DNS and "forget" to look up in files (which I can understand for dig, but > not for exim).
Achhh . . . I'm gonna plow through the BIND lists/usenet groups and see what's going on. The AAAA Resource Record type is for IPv6 Address records. That's why, when you force telnet to use IPv4 addressing, you don't get it . . . I don't know why the stub resolver is issuing resolution requests for IPv6 addressing . . . . Well, at least we know what it is. Now how to stop it. madmac > > Could this have anything to do with the thread "Local address lookup" started > by Jan Willem Stumpel last week? Problem is this was about a setup without a > nameserver and most people suggested it could be solved by using one. > <snip from his last contribution> > The version of telnet which comes with woody apparently does *not* > do a straightforward gethostbyname(). What it *does* do, I do not > know because I haven't looked at the source. But I did make a > small test program with gethostbyname() and that does not call the > outside DNS for local addresses. > > However it *is* possible to avoid DNS lookup with telnet if you > use the option -4, which forces IPv4 address resolution. So now I > made telnet -4 an alias for telnet. Maybe this will lead to > problems later on, but so far it works fine. In particular, there > is no delay in telnetting to a local box when the Internet > connection is down. > <snip end> > > Could it have anything to do with IPv6? Could it be a bug in Woody after all? > Any further suggestions? > By the way, I think putting all my boxes in root.hints is taking things a bit > far to solve this. > > Below are the files you named from galadriel, just to be sure. > My kernel is 2.4.18 (self compiled from kernel-source package). > > /etc/nsswitch.conf > passwd: compat > group: compat > shadow: compat > hosts: files dns > networks: files > protocols: db files > services: db files > ethers: db files > rpc: db files > netgroup: nis > > /etc/hostname > galadriel > > /etc/hosts > 127.0.0.1 localhost > 10.19.66.21 galadriel.fjphome.nl galadriel > # The following lines are desirable for IPv6 capable hosts > # (added automatically by netbase upgrade) > ::1 ip6-localhost ip6-loopback > fe00::0 ip6-localnet > ff00::0 ip6-mcastprefix > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > ff02::3 ip6-allhosts > > /etc/resolv.conf > domain fjphome.nl > nameserver 10.19.66.1 > > (Sorry this got so long, but I think most is relevant.) > > On Tuesday 24 September 2002 01:24, you wrote: > > Frans, > > > > A couple of things to check - > > > > in /etc/nsswitch, do you have: > > hosts: files dns > > > > and then in /etc/hostname do you have: > > galadriel > > > > and then in /etc/hosts do you have: > > 1.2.3.4 galadriel.fjphome.nl galadriel > > > > Also, in /etc/resolv.conf: > > domain fjphome.nl > > > > and make sure that you don't have a SEARCH line for fjphome.nl > > > > That should do it . . . > > > > madmac > > > > On 23 Sep 2002, 19:39:46, Frans Pop wrote: > > > I'm having an annoying problem with exim every time "exim -q" is run by > > > cron. Exim then causes two DNS query's to my local nameserver, namely > > > for: - galadriel.fjphome.nl (the correct fully quallified name) > > > - galadriel (unqualified!) > > > > > > The first query gets solved by my DNS, but the second does not and so > > > sometimes this query gets forwarded to the internet which causes a > > > dial-out (which I don't want as my phone bill is high enough as it is;-). > > > > > > The box causing the problem is Woody with IPv6 enabled and a default exim > > > setup for "Local delivery only" (option 4 in eximconfig). > > > My nameserver is bind on a Potato box (not yet upgraded). > > > > > > Questions > > > - Why does Exim request the unqualified name after the fully qualified > > > name has been resolved? > > Exim is requesting the unqualified name. > > > > The stub resolver built into the IP stack is issuing two resolution requests > > simultaneously, on for the unqualified name, and, based upon the default > > domain configured in /etc/resolv.conf, for the fully-qualified one. > > > > > - Can I stop Exim from making the unqualified request? > > Not for the interal mail domain, but if you have the name properly defined > > in the /etc/hostname and /etc/hosts file, and set /etc/nsswitch.conf to use > > files before DNS for host: resolution, you should be able to get a > > resolution locally, without having to query your local DNS server. > > > > > - Can I make my nameserver resolve the unqualified request? > > Yep - in the root.hints file, where all the root-servers for the . domain > > are listed, add an A record for galadriel: > > > > galadriel IN A 1.2.3.4> > > > > TIA > -- Doug MacFarlane [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
