Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."
Today's Topics:
1. Re: Manage DNS views in Netdot (Phil Regnauld)
2. Re: Manage DNS views in Netdot (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Tue, 7 May 2013 21:43:25 +0200
From: Phil Regnauld <[email protected]>
Subject: Re: [Netdot-users] Manage DNS views in Netdot
To: "Blakkheim.GW '" <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Blakkheim.GW ' (blakkheim.gw) writes:
> Hello Phil and thank you for your answer.
> What if I create a "fake" zone in Netdot, for example :
> externalview.domain.com
> Inside this zone, I create records with public adresses which will be visible
> only from the outside world in the form record.domain.com (and not
> record.externalview.domain.com)
>
> In my "real" zone domain.com there will be the same records but with private
> adresses. Then, in my named.conf or so, I tell BIND that the internal view
> would pick up the domain.com Netdot generated zone file whereas the external
> view would pick up the externalview.domain.com zone file.
> Is this completely stupid ?
Absolutely not, that sounds like a reasonable way to do things.
PS: I have once developed software that does exactly that (manage
split inside/outside DNS views). With all the headaches that entailed,
in the long run I would argue it's better to move away from views if
possible, and aim towards usnig a dedicated subdomain (int.domain.com)
for the internal systems, and put the rest in domain.com - and actually
refer to those as such (i.e.: mail.int.domain.com, etc.)
It also makes things like DNSSEC easier to implement :)
Cheers,
Phil
------------------------------
Message: 2
Date: Tue, 07 May 2013 16:49:16 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Manage DNS views in Netdot
To: Phil Regnauld <[email protected]>
Cc: "[email protected]" <[email protected]>,
"Blakkheim.GW '" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 5/7/13 3:43 PM, Phil Regnauld wrote:
> in the long run I would argue it's better to move away from views if
> possible, and aim towards usnig a dedicated subdomain (int.domain.com)
> for the internal systems, and put the rest in domain.com - and actually
> refer to those as such (i.e.: mail.int.domain.com, etc.)
My suggestion as well.
Keep it simple.
cv
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 54, Issue 4
*******************************************
