Date: Thu, 26 Feb 2004 01:18:40 +0100 From: Danny Pansters <danny@ricin.com> To: freebsd-questions@freebsd.org Subject: Re: Fetch unable to resolve. Message-ID: <200402260118.40105.danny@ricin.com> In-Reply-To: <403D39A4.9080704@x-istence.com> References: <403D39A4.9080704@x-istence.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 26 February 2004 01:11, X-Istence wrote: > Hello, > > > I am having problems with fetch and ftp, being unable to resolve any DNS > related matters. Like hostnames and stuff. > > However, nslookup, dig, and those tools still work just fine, i am > wondering what the problem could be. See output below. > > If you need any other info, please let me know, the owner is thinking of > having it reinstalled by the data center, but i would like to get to the > bottom of this. > > Sequence of event in the last 4 days: > > 1. tinydns installed, setup, and totally ready > 2. tinydns data copied to a new server, deamontools, tinydns and its > stuff uninstalled > 3. Nothing done for a day or two You also killed any tinydns/supervise processes? > 4. Login to setup a mail server, fetch is unable to retrieve ports > 5. Try to trouble shoot > 6. No means available to get it to work, and here i am. <SNIP> So, are you perhaps still using your localhost or your box' IP (former) host to resolve?, e.g. what's in /etc/resolv/conf? I reckon it should use some upstream (your other?) nameserver now. Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402260118.40105.danny>