Date: Fri, 28 Nov 1997 18:26:45 +1030 From: Greg Lehey <grog@lemis.com> To: Kwoody <kwoody@citytel.net> Cc: freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: win95 and DNS Message-ID: <19971128182645.23980@lemis.com> In-Reply-To: <Pine.BSF.3.91.971127233546.5858A-100000@mybsd.net>; from Kwoody on Thu, Nov 27, 1997 at 11:40:23PM -0800 References: <Pine.BSF.3.91.971127233546.5858A-100000@mybsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 27, 1997 at 11:40:23PM -0800, Kwoody wrote:
>
> Ok now, I shut down netscape, and am for sure running bovine offline. I
> had been running ppp with -alias to act as a gateway for my 95 and sun box.
> and my win95 box after about 10 mins asks for a DNS lookup from my ISP's
> box and I dont know why!!
>
> So I figure ok do it without alias option and that would fix it. Nope,
> after about 10-12 mins, again I get 192.167.0.1:137 via UDP -->
> 204.244.99.66:53.
>
> Why/what is this 95 box doing?
Sorry, I don't understand Microsoft. But you might be able to find
out with tcpdump, assuming this is going via your FreeBSD box.
> Might I have to run named?
It's a good idea, but it won't completely solve this problem.
> Hope not, not really into figureing out something else right now.
It's simple! Read all about it:
Name server on a standalone system
If you only have a single machine connected to the network via a PPP link, and
your own machine is part of the ISP's zone, you can use the resolv.conf method
as well. But it's not a good idea. Every lookup goes over the link, which is
relatively slow. Since the results of the lookup aren't stored anywhere
locally, you can end up performing the same lookup again and again. The answer
is obvious: save the information locally. You can do this with a caching-only
name server. As the name suggests, the caching-only name server doesn't have
any information of its own, but it stores the results of any queries it makes
to other systems, so if a program makes the same request again--which happens
very frequently--it presents the results much more quickly on subsequent
requests.
o Either rename or remove /etc/resolv.conf, and create a new one with the
following contents:
nameserver 127.0.0.1 local name server
nameserver 139.130.237.3 ISP's first name server
nameserver 139.130.237.17 ISP's second name server
/etc/resolv.conf isn't necessary, but if you have one like in the example,
lookups will still succeed (but a little more slowly) if your name server
should fail for any reason.
o Change /etc/rc.conf:
named_enable="YES" # Run named, the DNS server (or NO).
named_flags="-b /etc/namedb/named.boot" # Flags to named (if enabled).
o Create a file /etc/namedb/localhost.rev containing:
@ IN SOA @host@. root.@host@. (
@date@ ; Serial
3600 ; Refresh
300 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS @host@.
1 IN PTR localhost.@domain@.
To create the file, you can start with the file /etc/namedb/PROTO.local-
host.rev, which contains a template for this file. Replace @host@ with the
FQDN of your host (freebie.example.org in this example), @date@ with the date
in the form yyyymmddxx, and @domain@ with example.org.. Make sure that the
FQDNs end with a trailing period. Alternatively, you can run the script
/etc/namedb/make-localhost.
o Create a file /etc/namedb/named.boot containing:
directory /etc/namedb
primary 0.0.127.in-addr.arpa localhost.rev
forwarders 139.130.237.3 139.130.237.17
/etc/namedb/named.boot should already be present on your system as well. You
just need to add the last line. The address 139.130.237.3 is the ISP's name
server address. That's all there is to it. The forwarders line contains up
to ten name server addresses. In this case, we're assuming that an
additional name server exists with the address 139.130.237.17.
o Start named:
# named -b /etc/namedb/named.boot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971128182645.23980>