| Author |
Message |
Steve Schofield
Guest
|
 Posted:
Fri Jan 14, 2005 9:44 pm Post subject:
DNS load? |
|
|
I have a Primary DNS server that is internet facing with a particular zone.
What i'd like to do is have a process, script or whatever populate a
separate internal AD/DNS server that would hold a copy of the same zone. I
know you can publish from an AD/Integrated to a secondary DNS server but
what about an easy way to publish records from a Primary Stand-Alone DNS
server to an AD/Integrated DNS server of the same zone on two different DNS
servers?
--
Steve Schofield
Microsoft MVP - ASP/ASP.NET
ASPInsider Member - MCP
http://www.orcsweb.com/
Powerful Web Hosting Solutions
#1 in Service and Support |
|
| Back to top |
|
 |
John Smith
Guest
|
| Posted:
Fri Jan 14, 2005 9:53 pm Post subject:
Re: DNS load? |
|
|
just create a (secondary) zone as you normally would, telling it the
master zone is held at the internet facing IP.
On Fri, 14 Jan 2005 10:44:30 -0500, Steve Schofield wrote:
| Quote: | I have a Primary DNS server that is internet facing with a particular zone.
What i'd like to do is have a process, script or whatever populate a
separate internal AD/DNS server that would hold a copy of the same zone. I
know you can publish from an AD/Integrated to a secondary DNS server but
what about an easy way to publish records from a Primary Stand-Alone DNS
server to an AD/Integrated DNS server of the same zone on two different DNS
servers? |
|
|
| Back to top |
|
|
Steve Schofield
Guest
|
| Posted:
Fri Jan 14, 2005 11:04 pm Post subject:
Re: DNS load? |
|
|
What if the internet facing zone and the Intranet zone are the dame domain
name MyDomain.com (Internet) and MyDomain.com(Intranet)?
--
Steve Schofield
Microsoft MVP - ASP/ASP.NET
ASPInsider Member - MCP
http://www.orcsweb.com/
Powerful Web Hosting Solutions
#1 in Service and Support
"John Smith" <jsmith@macroshaft.com> wrote in message
news:pan.2005.01.14.15.53.30.956613@macroshaft.com...
| Quote: | just create a (secondary) zone as you normally would, telling it the
master zone is held at the internet facing IP.
On Fri, 14 Jan 2005 10:44:30 -0500, Steve Schofield wrote:
I have a Primary DNS server that is internet facing with a particular
zone.
What i'd like to do is have a process, script or whatever populate a
separate internal AD/DNS server that would hold a copy of the same zone.
I
know you can publish from an AD/Integrated to a secondary DNS server but
what about an easy way to publish records from a Primary Stand-Alone DNS
server to an AD/Integrated DNS server of the same zone on two different
DNS
servers?
|
|
|
| Back to top |
|
|
Todd J Heron
Guest
|
| Posted:
Fri Jan 14, 2005 11:37 pm Post subject:
Re: DNS load? |
|
|
Won't work.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
Steve Schofield
Guest
|
| Posted:
Fri Jan 14, 2005 11:51 pm Post subject:
Re: DNS load? |
|
|
That is what I figured but thought'd I'd ask Thank everyone for their
replies, guess its "brute-force" method of putting records in.
--
Steve Schofield
Microsoft MVP - ASP/ASP.NET
ASPInsider Member - MCP
http://www.orcsweb.com/
Powerful Web Hosting Solutions
#1 in Service and Support
"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
news:#UEQF$l#EHA.3472@TK2MSFTNGP14.phx.gbl...
| Quote: | Won't work.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
--------------------------------------------------------------------------
--
This posting is provided "as is" with no warranties and confers no rights
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Sat Jan 15, 2005 12:14 am Post subject:
Re: DNS load? |
|
|
You could script it but it isn't worth the effort (usually.)
The "standard" way to do this is to replicate the
external ZONE before it becomes an AD support
zone (make it a secondary) then change the internal
to Primary/AD-int and thus forever break the
automatic replication.
Outside records seldom change so other than remembering
to duplicate all external changes/additions on the
internal set.
Also note, it is USUALY (almost always except for
the very large Internet companies) best to not even
supply your own PUBLIC DNS servers but rather
to leave (or more it back) to your Registrar.
--
Herb Martin
"Steve Schofield" <steve@deviq.com> wrote in message
news:#E5OVGm#EHA.1300@TK2MSFTNGP14.phx.gbl...
| Quote: | That is what I figured but thought'd I'd ask Thank everyone for their
replies, guess its "brute-force" method of putting records in.
--
Steve Schofield
Microsoft MVP - ASP/ASP.NET
ASPInsider Member - MCP
http://www.orcsweb.com/
Powerful Web Hosting Solutions
#1 in Service and Support
"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
news:#UEQF$l#EHA.3472@TK2MSFTNGP14.phx.gbl...
Won't work.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
--------------------------------------------------------------------------
--
This posting is provided "as is" with no warranties and confers no
rights
|
|
|
| Back to top |
|
|
John Smith
Guest
|
| Posted:
Sat Jan 15, 2005 12:53 am Post subject:
Re: DNS load? |
|
|
i agree w/ everything except where you say it is usually best to not even
supply your own public dns servers...that might be true in some cases (esp
for smaller companies), but i don't think such a blanket statement can
be accurately made. Way too many factors to consider...(just my 2cents
worth)...
why should someone not host their own public dns servers?
On Fri, 14 Jan 2005 12:14:20 -0600, Herb Martin wrote:
| Quote: | You could script it but it isn't worth the effort (usually.)
The "standard" way to do this is to replicate the
external ZONE before it becomes an AD support
zone (make it a secondary) then change the internal
to Primary/AD-int and thus forever break the
automatic replication.
Outside records seldom change so other than remembering
to duplicate all external changes/additions on the
internal set.
Also note, it is USUALY (almost always except for
the very large Internet companies) best to not even
supply your own PUBLIC DNS servers but rather
to leave (or more it back) to your Registrar. |
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Sat Jan 15, 2005 2:19 am Post subject:
Re: DNS load? |
|
|
"John Smith" <jsmith@macroshaft.com> wrote in message
news:pan.2005.01.14.18.53.32.888924@macroshaft.com...
| Quote: | i agree w/ everything except where you say it is usually best to not even
supply your own public dns servers...that might be true in some cases (esp
for smaller companies), but i don't think such a blanket statement can
be accurately made. Way too many factors to consider...(just my 2cents
worth)...
|
It can, since I did except the larger Internet companies.
| Quote: | why should someone not host their own public dns servers?
|
1) because the Registrars offer free service (in almost all
cases you already paid for it).
2) Most companies don't have two DNS servers available
on the Internet which is one of the business requirements
for registering in most top level domains
3) Running a service you don't need to run just opens you
server to another kind of attack should bugs ever be
discovered
4) Generally, the registrar has a presence on or close to the
backbone and so provide faster service
5) Such service does not load your servers which are presumably
doing something useful
6) 24/7 professional support with fault tolerant hardware (note,
if you only have one Web server you might say, "But when
my DNS is down so is my web" but then we get back to the
case where you didn't have 2 or more DNS servers anyway.
Those who REALLY need their own public DNS service know
who they are (or shouldn't be doing that job) and thus realize that
THEY fit in the exception class.
--
Herb Martin
| Quote: | On Fri, 14 Jan 2005 12:14:20 -0600, Herb Martin wrote:
You could script it but it isn't worth the effort (usually.)
The "standard" way to do this is to replicate the
external ZONE before it becomes an AD support
zone (make it a secondary) then change the internal
to Primary/AD-int and thus forever break the
automatic replication.
Outside records seldom change so other than remembering
to duplicate all external changes/additions on the
internal set.
Also note, it is USUALY (almost always except for
the very large Internet companies) best to not even
supply your own PUBLIC DNS servers but rather
to leave (or more it back) to your Registrar.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in