Michael, I think you have confused the issue for John. There is nothing
magic about the last two pieces of a domain name; a DNS server can assert
it is authoritative for a domain name that has 3 or 4 or 5 pieces.
(Examples are fairly common in TLDs that end in country codes; for example,
here
Ray Olszewski wrote (on Thu, Jun 06, 2002 at 11:38:09PM -0700):
| One low-tech solution that should work, BTW, is to add the hostname/IP
| address pair to the hosts file on each workatation (/etc/hosts for Linux
| workstations; I don't know the WinXX analog, though I do know there is
| one).
At 12:07 AM 6/6/02 -0500, guitarlynn wrote:
On Wednesday 05 June 2002 21:54, John Mullan wrote:
I have tried that as well. It allows the LEAF box to resolve
mullan.dns2go.com to 192.168.1.128 (by using PING on the LEAF box)
but nobody else on the network. They still get the external IP as
Hi
At 09:33 06.06.2002, you wrote:
Message: 9
From: John Mullan [EMAIL PROTECTED]
To: 'Lee Kimber' [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: RE: [leaf-user] Using HOSTS file
Date: Wed, 5 Jun 2002 22:54:53 -0400
At 08:38 PM 6/5/2002 -0400, you wrote:
I use DNS2GO to handle my
On Thu, 06 Jun 2002 00:09:38 PDT Ray Olszewski wrote:
Jeff's response is the right one here -- the router (or some other host on
the LAN) needs to run a DNS server that resolves FQNs of hosts on the LAN
to their private addresses and forwards all other requests to a real
nameserver. The
On Thursday 06 June 2002 02:09, Ray Olszewski wrote:
At 12:07 AM 6/6/02 -0500, guitarlynn wrote:
By chance have any of you attempted to declare files before dns
in /etc/nsswitch.conf???
By doing this, any host/network listed in nsswitch.conf should
resolve according to the order listed in
: [leaf-user] Using HOSTS file
On Thu, 06 Jun 2002 00:09:38 PDT Ray Olszewski wrote:
Jeff's response is the right one here -- the router (or some other
host on
the LAN) needs to run a DNS server that resolves FQNs of hosts on the
LAN
to their private addresses and forwards all other requests
On Thu, 06 Jun 2002 20:40:25 EDT you wrote:
OK Brad. I've put tinydns on. I left the tinydns option for internal
IP at 127.0.0.1
Is this the proper loopback interface address?
Yes, it is:
$ cat /etc/tinydns-private/env/IP
127.0.0.1
--Brad
Fritz
Sent: Thursday, June 06, 2002 9:13 PM
To: John Mullan
Cc: [EMAIL PROTECTED]
Subject: Re: [leaf-user] Using HOSTS file
On Thu, 06 Jun 2002 20:40:25 EDT you wrote:
OK Brad. I've put tinydns on. I left the tinydns option for internal
IP at 127.0.0.1
Is this the proper loopback interface
John Mullan wrote:
Thanks for you help so far Brad..
I'm sure I'm missing something, but no luck. I had tried to set it up
so that dnscache watches 192.168.1.254 and looks to tinydns. Not sure
if that is what is supposed to happen or if I even got it that way in
any of my
On Thu, 06 Jun 2002 23:01:43 EDT you wrote:
Thanks for you help so far Brad..
Glad to help.
I'm sure I'm missing something, but no luck. I had tried to set it up
so that dnscache watches 192.168.1.254 and looks to tinydns. Not sure
if that is what is supposed to happen or if I even
PROTECTED]]
Sent: Wednesday, June 05, 2002 10:18 PM
To: John Mullan
Subject: Re: [leaf-user] Using HOSTS file
I think you need /etc/network.conf - the main network config script.
Looks for some lines about two thirds of the way down that deal with
hosts
and private.domain (unless you have changed
: [leaf-user] Using HOSTS file
I think you need /etc/network.conf - the main network config script.
Looks for some lines about two thirds of the way down that deal with
hosts
and private.domain (unless you have changed it to something else
already)
The commented out host1 is an example
On Wednesday 05 June 2002 21:54, John Mullan wrote:
I have tried that as well. It allows the LEAF box to resolve
mullan.dns2go.com to 192.168.1.128 (by using PING on the LEAF box)
but nobody else on the network. They still get the external IP as
resolved by DNS2GO's servers.
By chance have
14 matches
Mail list logo
