hosting dns

[Stephen New]

i wish to host our own internal dns rather than paying a
ISP monthly costs to host it

what aspects are involved

thanks

 

[Michael Johnston [MSFT]]

It's pretty simple. You will need two public static IP addreses and two DNS servers. On one of the DNS servers, configure a standard primary zone for your
DNS zone. Populate it with the necessary records for the resources that will be internet accessible(MX records or mail, WWW host record for website). On the
second server, create a standard secondary, point it to the primary and transfer the zone over. Lastly, contact Network Solutions to have them update the NS
records for your zone to point to the new IP addreses of your internally host DNS servers. This will only work if you are listed as the administrative contact or
technial contact for your zone. If the current host registered the name on your behalf, they may have to make the changes for you. Be sure you have them turn
the zone over to you though. This way they are totally out of the picture and you can gain controll over your zone at that point.

If the current zone has a lot of records in it already, what you can do is to initially setup what will be your primary DNS as a secondary to the currently host
primary for your zone. Perform a zone transfer to get all the records for your zone, then change it's type to primary. This way you don't have to manually add
all the records. You may have to contact the current host to have them enable zone transfer to you before this will work.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Kevin D. Goodknecht]

In

i wish to host our own internal dns rather than paying a
ISP monthly costs to host it

what aspects are involved

thanks

You need a minimum of two DNS servers one internal resolving internal
machines to private addresses and one for external machines resolving names
to external Public addresses. Do not try this from only one DNS server, it
can make your web sites/servers inaccessable from the internet and should a
host with a private address get cached somewhere it can make you web sites
inaccessable until TTL runs out on the cached record, could be seven days or
more.

If you have the hardware and the bandwidth available you also need two
public IP addresses. Then have your registrar register your name server
hostnames and and IP addresses listed at the Root DNS servers. You need a
minimum of two DNS hosts and IP addresses to do all your own DNS hosting.


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
http://www.lonestaramerica.com/
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
--
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

 

[Jeff Cochran]

i wish to host our own internal dns rather than paying a
ISP monthly costs to host it

what aspects are involved

Setting up your DNS server, ensuring access to it from outside your
network, adding appropriate host records, pointing your domain
registration to your new name servers and waiting for the changes to
propagate across the internet.

It's not hard, it's not rocket science and it's well documented.
Might want to look at "DNS and Bind", "DNS on Windows NT" or "DNS on
Windows 2000" as matches your setup, all from O'Reilly and authored by
Cricket Liu, et. al.

Jeff

 

[Jonathan de Boyne Pollard]

MJM> Lastly, contact Network Solutions [...]

.... or the registrar of one's choice.

What registrar that could be, of course, varies according to what
the enclosing superdomain is. For "com.", for example, there is
a long list of accredited registrars.

<URL:http://verisign.com./nds/naming/registrar/custalph.html>

Also: Your description of the process is incomplete. It is important
that the existing DNS hosting service change what it is publishing.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-switching-content-servers.html#ChangingOld>

 

[Jonathan de Boyne Pollard]

KDGS> Then have your registrar register your name server hostnames
KDGS> and and IP addresses listed at the Root DNS servers.

The root servers will only be involved if he is registering a top-level
domain. And in such a case, a registrar would _not_ be involved.