Windows 2003 Public DNS Server

[Michael Trantas]

I'm getting ready to set up my company's own DNS servers because we have
been having some problems adding specific DNS records to our accoount
through Network Solutions. I am going to use this new server as our public
DNS server so that we can take some of the responsibility away from them and
bring it in house.

I have several questions and I'm looking for some good advice:

1. When I set the DNS server up, do I just copy the public DNS records from
Network Solutions (including all A, MX and CNAME) and put them in my Windows
2003 DNS server or is there a way I can pull all of this info. from Network
Solutions servers - we have about 15 domains, each containing a number of
DNS records.

2. Once I copy everything to my DNS server, do I just list as one of our
Name Servers at Network Solutions so people can resolve to it? How do I
test it to see if it's actually working?

Does anyone even know if there is a step-by-step instruction guide out there
that I can use - I looked on Microsoft's website but couldn't find anything
related to public DNS...

Even better, can someone sort of guide me through this process - I don't
want to mess anything up while I'm building...

Thanks!

Michael

[Herb Martin]

"Michael Trantas" <mike.t...@paychoice.com> wrote in message
news:ODeWpG5H...@TK2MSFTNGP04.phx.gbl...

> I'm getting ready to set up my company's own DNS servers because we have
> been having some problems adding specific DNS records to our accoount
> through Network Solutions. I am going to use this new server as our
> public DNS server so that we can take some of the responsibility away from
> them and bring it in house.
>
> I have several questions and I'm looking for some good advice:

My strong advice is to move to a quality REGISTRAR
(one who meets your needs) instead. (You are really
supposed to have a minimum of two DNS servers by
Internet business rules.)

GoDaddy works for me. You may find it does for you but
there are other good ones.

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

[Tomack]

It may be a long learning curve setting up your own DSN Name Server, You may
have to register a Domain name for it also. you may have to Name your Name
Server associated with the Newly register Domain name.

Example:

If your company name is register as TESTCOMPANY.COM as your external domain
and your Internal Domain is a sub-domain of your external domain aslo called
parent domain for internal Network CORP.TESTCOMPANY.COM and now you are
tryging to Host your OWN NAME SERVER for which you may have have something
like NS1.TCompany.NET and NS2.TCompany.NET to support resolving not only your
External queries but also internal queries.

I'm not the subject matter expert but , it could be a long learning curve.
so keeping your external domain to any other ISP is the best option. Godaddy
is good try RackSpace.com (best)

Tom