Date: Sat, 17 May 2003 01:08:13 +0530 From: Shantanu Mahajan <freebsd@dhumketu.cjb.net> To: george donnelly <list@zettai.net> Cc: george donnelly <george@zettai.net> Subject: Re: dns resolution problem Message-ID: <20030516193813.GA1200@dhumketu.homeunix.net> In-Reply-To: <BAEA99CD.2CE0D%list@zettai.net> References: <BAEA99CD.2CE0D%list@zettai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
+++ george donnelly [freebsd] [16-05-03 13:36 -0400]: | [Roman Neuhauser wrote (neuhauser@bellavista.cz) on 5/16/03 5:27 AM] | | > # george@zettai.net / 2003-05-15 19:48:30 -0400: | >> We recently made a IP changeover (we changed all IP's) and move to a VLAN | >> config and now cronjobs, pings etc can not reolve hostnames. host and dig | >> work fine. | >> | >> Does anyone have any idea why this could be? | >> | >> Running: | >> | >> FreeBSD 4.7 | >> Djbdns, tinydns, dnscache | >> dnscache runs on 127.0.0.1 | >> | >> resolv.conf looks like this: | >> | >> alpha# more /etc/resolv.conf | >> domain alpha.zettai.net | >> nameserver 127.0.0.1 | >> nameserver 216.93.187.185 | >> nameserver 216.93.178.185 | >> nameserver 216.93.160.16 | >> nameserver 216.93.170.17 | >> | >> 127.0.0.1 is dnscache, the resolver and cache | > | > ok. | > | >> the next two are ns1 and ns2, tinydns, authoritative | > | > this is quite probably (part of your) your problem. | > | >> the last 2 are the ISP's ns1 and ns2 | > | > not needed, remove them. | | | thanks for your suggestion. i removed them but the problem persists. i also | tried replacing resolv.conf with some values from another machine on the | network where i'm not having this problem and this still does not solve it. check out /etc/hosts Regards, Shantanu -- Madness has no purpose. Or reason. But it may have a goal.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030516193813.GA1200>