Re: domain name: internet vs. intra-net
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-wobble, with exceptions.)
>
> (This had better not be a sly attempt to collect a new newbiedoc...)
not until we get it hammered down all nice and flat, no. :)
> I have recently inherited a network which was set up with company.com
> as the official, registered external domain name and company.net for
> the internal systems. It is not pleasant and even somewhat confusing.
> (There are other poor practices in place which make it worse, such as
> foo.company.com and foo.company.net sometimes being the same machine
> and sometimes not, depending on which machine you're on at the time,
> but I digress...) I am now in the process of migrating the internal
> network from company.net to east.company.com and west.company.com.
> (Yes, it spans two buildings. Without subnets. (Yet.)) I'm finding
> it _much_ easier to keep things straight with the new names.
how do you manage the migration? i've got
/etc/bind/
serensoft
serensoft.rev
lan
lan.rev
> What sorts of complaints is dlint giving you? So far, I've been keeping
> everything on one name server with separate zone files for everything and
> it doesn't bother BIND at all. (I'm having some odd routing problems,
> but that doesn't have anything to do with DNS...)
ERROR: "mail.serensoft.com. A 208.33.90.85", but the PTR record for 85.90.33.208.in-addr.arpa. is "ns.serensoft.com."
One of the above two records are wrong unless the host is a name server or mail server.
To have 2 names for 1 address on any other hosts, replace the A record
with a CNAME record:
mail.serensoft.com. IN CNAME ns.serensoft.com.
WARNING: the zone serensoft.com. has an A record but no reverse PTR record. This is probably OK.
and i'd like
208.33.90.85 to be serensoft.com eth1, visible everywhere (as
it already is)
192.168.1.100 to be mac.serensoft.com
but invisible to the outside net, and
it should be able to ping win.serensoft.com
192.168.1.200 would be win.serensoft.com
which is not visible to the outwise world
192.168.1.1 to be server.serensoft.com eth0, internal-lan only
how to i separate the internal/private 'no-update' addresses from
the public 'update'-able addresses, in bind/dns?
--
don't visit this page. it's bad for you. take my expert word for it.
http://www.salon.com/people/col/pagl/2001/03/21/spring/index1.html
will@serensoft.com
http://sourceforge.net/projects/newbiedoc -- we need your brain!
http://www.dontUthink.com/ -- your brain needs us!
Reply to: