PHWinfo - Afficher un message

01/03/2006, 13h30

<danths@gmail.com> wrote in message
news:1141218683.170197.90490@e56g2000cwe.googlegro ups.com...
> Hello:
> I have our DNS hosted with the ISP at the same time would like to setup
> an additional setup within the office where in I can add only
> additional records not present in the primary DNS hosted with the ISP,

What you are describing is NOT a "secondary DNS" but rather
an architecture referred to as Shadow DNS (aka Split DNS).

You will actually setup another Primary for the same zone.

The result is that you will be able to add additional records
to the internal VERSION of your zone without those records
propagating to the public version of the zone.

Easiest way to do this is usually to setup the internal as a
Secondary (temporarily), copy the records and then change
it to Primary.

> these are usually servers yet to be deployed at the hosting center. How
> do I go about it. The ISP doesn't allow zone transfers and so I cannot
> create a full fledged secondary dns server.

In this case you will have to do the entire thing manually.

> I presume I would need some
> kind of forwarder so that it queries the primary DNS servers in case
> the record was not found in the set at the office. Where should I
> start?

Your other choice (if the number of additional records is small)
is to create a separate zone for EVERY record and put in an A
(host address) record with a 'blank name, same as parent'.

Example: FileServer.Example.Com would be a separate zone,
and you would put in an A record for the address of such an
internal server.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

01/03/2006, 13h30	#2
Herb Martin Messages: n/a Hébergeur:	Re: Secondary DNS <danths@gmail.com> wrote in message news:1141218683.170197.90490@e56g2000cwe.googlegro ups.com... > Hello: > I have our DNS hosted with the ISP at the same time would like to setup > an additional setup within the office where in I can add only > additional records not present in the primary DNS hosted with the ISP, What you are describing is NOT a "secondary DNS" but rather an architecture referred to as Shadow DNS (aka Split DNS). You will actually setup another Primary for the same zone. The result is that you will be able to add additional records to the internal VERSION of your zone without those records propagating to the public version of the zone. Easiest way to do this is usually to setup the internal as a Secondary (temporarily), copy the records and then change it to Primary. > these are usually servers yet to be deployed at the hosting center. How > do I go about it. The ISP doesn't allow zone transfers and so I cannot > create a full fledged secondary dns server. In this case you will have to do the entire thing manually. > I presume I would need some > kind of forwarder so that it queries the primary DNS servers in case > the record was not found in the set at the office. Where should I > start? Your other choice (if the number of additional records is small) is to create a separate zone for EVERY record and put in an A (host address) record with a 'blank name, same as parent'. Example: FileServer.Example.Com would be a separate zone, and you would put in an A record for the address of such an internal server. -- Herb Martin, MCSE, MVP Accelerated MCSE http://www.LearnQuick.Com [phone number on web site]