On Sun, Feb 11, 2007 at 12:47:27PM +0000, Matthias Scheler wrote:
> On Sat, Feb 10, 2007 at 11:41:21PM -0500, Steven M. Bellovin wrote:
> > > I am unsure where it originates from, however I tried to look it up
> > > on one of those reverse look-up site and the site was un-able to
> > > resolve it . I guess this means that it is the IP address of the
> > > router. Is this the case. Sorry to have to be spoon-fed here but my
> > > knowledge of the workings of networking is very small.
> > > 
> > That's a private, non-routable network, and is almost certainly the
> > router itself.
> 
> Yes, indeed. And I bet that the router's internal DNS cache server
> causes the problems.
> 
> Alasdair:
> What does the output of "ifconfig -a" on your NetBSD system look like?
> 
> A work-arround would to be to run a local caching nameserver:
> 1.) Add "named=YES" and "named_chrootdir="/var/chroot/named" to
>     "/etc/rc.conf".
> 2.) Start the nameserver with "/etc/rc.d/named start".
> 3.) Change the nameserver in "/etc/resolv.conf" to 127.0.0.1.
> 4.) Try whether the various applications work better now (after
>     restarting them).
> 
> 	Kind regards
> 
> -- 
> Matthias Scheler                                  http://zhadum.org.uk/

Hi Matthias,

Here is the results of ifconfig -a

$ ifconfig -a
rtk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
      address: 00:0a:cd:10:d4:f1
      media: Ethernet autoselect (100baseTX full-duplex)
      status: active
      inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
      inet6 fe80::20a:cdff:fe10:d4f1%rtk0 prefixlen 64 scopeid 0x1
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33192
	inet 127.0.0.1 netmask 0xff000000
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

	I tried your workaround and the result was this error message when trying to send mail in mutt:
	smtp: cannot locate host smtp.iprimus.com.au: No address associated with       
 +hostname 
I tried Gary Duzan's addition to your suggestion "Since you are using dhclient, you will want to put the following in
                                                                                your /etc/dhclient.conf:

																				prepend domain-name-servers 127.0.0.1;

																														   You can do this instead of step 3 above, since dhclient will replace
																																								      your resolv.conf with whatever it gets from the DHCP server (probably
																																																			 your router)."
I didn't have the file /etc/dhclient.conf present so I created it with the suggested line 
 and this seemed to work in so far as I was able to send an email without first using the telnet -4 trick. However on rebooting I noticed the following lines in the start-up messages

 
										local host named [255]:none:0:open:/etc/named.conf file not found
local host named [255]loading config file : file not found
local host named [255] exiting due to fatal error



regards,

Alasdair