On Tue, Apr 17, 2001 at 11:15:03PM -0500, will trillich wrote:
> how do you manage the migration?
Somewhat painfully... Basically, I've set up the firewall to route between
the three internal IP ranges in use and (once I've got the kinks worked out
of that) my plan is to, as each user machine nee
The recommended way to cope with DNS on a LAN using private addressing
that is connected to the internet somehow eg via NAT is to use a thing
called "splt primary DNS".
Basically what you do is this.
1. Have a DNS server on the publically addressed side that lists the
stuff that the internet shou
On Tue, Apr 17, 2001 at 04:54:48PM -0500, Dave Sherohman wrote:
> On Tue, Apr 17, 2001 at 03:19:40PM -0500, will trillich wrote:
> > and can you give an example or two on how to use /etc/bind/* to
> > set that up? (all my attempts give dlint conniptions, though
> > things seem to work-though-they-w
On Tue, Apr 17, 2001 at 03:19:40PM -0500, will trillich wrote:
> and can you give an example or two on how to use /etc/bind/* to
> set that up? (all my attempts give dlint conniptions, though
> things seem to work-though-they-wobble, with exceptions.)
(This had better not be a sly attempt to colle
On Mon, Mar 26, 2001 at 11:24:00AM -0600, Dimitri Maziuk wrote:
> On Mon, Mar 26, 2001 at 03:17:00AM -0600, will trillich wrote:
> > at the risk of exposing another 'religious' issue--
> >
> > let's say you have a static IP 12.34.56.78 and a public domain
> > name 'mydomain.org' attached to it.
>
On Mon, Mar 26, 2001 at 06:21:56AM -0800, Pann McCuaig wrote:
> On Mon, Mar 26, 2001 at 03:17, will trillich wrote:
> > let's say you have a static IP 12.34.56.78 and a public domain
> > name 'mydomain.org' attached to it.
> >
> > now you add a private internal lan using 192.168.*.* so your
> > sp
On Mon, Mar 26, 2001 at 03:17:00AM -0600, will trillich wrote:
> at the risk of exposing another 'religious' issue--
>
> let's say you have a static IP 12.34.56.78 and a public domain
> name 'mydomain.org' attached to it.
>
> now you add a private internal lan using 192.168.*.* so your
> spouse a
On Mon, Mar 26, 2001 at 03:17, will trillich wrote:
> at the risk of exposing another 'religious' issue--
>
> let's say you have a static IP 12.34.56.78 and a public domain
> name 'mydomain.org' attached to it.
>
> now you add a private internal lan using 192.168.*.* so your
> spouse and kids can
On Mon, 26 Mar 2001 03:17:00 MDT, will trillich writes:
>what kind of naming setup do you use for the intRAnet? something
>totally different from the public access point ("timmy.my.lan"
>for example) or do you branch off the original public name
>("timmy.private.mydomain.org" for example)?
Well,
at the risk of exposing another 'religious' issue--
let's say you have a static IP 12.34.56.78 and a public domain
name 'mydomain.org' attached to it.
now you add a private internal lan using 192.168.*.* so your
spouse and kids can surf for bomb recipes and porn...
what kind of naming setup do y
10 matches
Mail list logo
