experiment

[Bigi]

Current situation:

- a large neighbourhood lan
- a local isp who get the internet from an official IPS and gives us acces
outside
- the local isp server running linux
- our setting to get outside are
GATEWAY: 192.168.2.1
DNS : 193.231.236.10
ALT.DNS : 193.231.236.17


A part of the network want to get from the local isp band and redistribute
it to some local computers.
I created a new domain, installed AD and now .... problems
The server is not multihomed, and has a connection to internet.

I want the client computers to enter in their tcp/ip proprieties the gateway
and dns of my server, and the server do the rest to forward the packets to
the right destination
the server has the following tcp settings
Gateway: 192.168.2.1 -> the linux server
DNS : 192.168.2.238 -> the local computer IP

my question is how do i create the dns lookup zone for the Official ISP
(193.231.236.10, 193.231.236.17), what kind of zone should it be etc
if any one can help me .......

 

[Herb Martin]

my question is how do i create the dns lookup zone for the Official ISP

(193.231.236.10, 193.231.236.17), what kind of zone should it be etc
if any one can help me .......

If you mean you will "split" or "shadow" your DNS -- external and interal
versions of the SAME ZONE then think of it this way:

In a Shadow or Split DNS, you really have TWO ZONES that just happen
to have the same name.

Because of this they must not be held on the same (set of) servers but must
be disjoint. So, build one (the external usually) and then build the other.

When you add a record to the External zone, you generally must add that
same record (manually) to the Internal zone so that internal users can find
those same services.

For the External zone you will almost always use "Primary with Secondaries"
because it is unlikely you wish to expose a DC ('out there'.)