help setting up a internet DNS server as new name server

[fox...@gmail.com]

I am after a bit of help and guidance. I am trying to configure DNS on
one of our servers so that we can use it as our own nameserver. We run
a website design company and the name servers of the company we use
keeps going AWOL. In the first instance we need to get it setup as the
third name server and then eventually become totally reliant on (I know
we need another one and this is on the way). We want to be able to use
this name server as a third name server for some of our domains.

I have found a few tutorials but im a little lost. The first thing
I'm stuck on is the FQDN. I have a domain that points to this server
and I ideally want the name format of the nameserver to be something
like ns1.mydomain.com.

Where do I configure this on the server. Is it the computer name as at
the moment the computer name is something else. I am struggling to
find where this FQDN is setup on the server.

Thanks

[Lanwench [MVP - Exchange]]

In news:1158593067.4...@d34g2000cwd.googlegroups.com,
fox...@gmail.com <fox...@gmail.com> typed:

Hi - someone else may post with more specific advice, but mine is - find a
reliable (public) DNS host, ideally a company that has a decent datacenter
to support it, and have them be authoritative for this domain. You are
unlikely to have that same infrastructure on your own network....and if
you're asking the question you are now, perhaps it would be best to leave
this in the hands of people who do it for a living. I mean no offense by
this. :)

[Herb Martin]

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

"Lanwench [MVP - Exchange]"
<lanw...@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:%23TRupQL...@TK2MSFTNGP05.phx.gbl...

> In news:1158593067.4...@d34g2000cwd.googlegroups.com,
> fox...@gmail.com <fox...@gmail.com> typed:
>> I am after a bit of help and guidance. I am trying to configure DNS
>> on one of our servers so that we can use it as our own nameserver.
>> We run a website design company and the name servers of the company
>> we use keeps going AWOL.

Follow LanWench's idea and move you DNS BACK to the
REGISTRAR.

If you don't have a good registrar transfer to GoDaddy or someone
else both reliable and cheap.

>> In the first instance we need to get it
>> setup as the third name server and then eventually become totally
>> reliant on (I know we need another one and this is on the way). We
>> want to be able to use this name server as a third name server for
>> some of our domains.
>>
>> I have found a few tutorials but im a little lost. The first thing
>> I'm stuck on is the FQDN. I have a domain that points to this server
>> and I ideally want the name format of the nameserver to be something
>> like ns1.mydomain.com.

>> Where do I configure this on the server. Is it the computer name as
>> at the moment the computer name is something else. I am struggling to
>> find where this FQDN is setup on the server.

That is one way. In the System Control Panel you can name the server
short name (e.g., ns1) and the server's domain name (mydomain.com),
but for such things as presence on the Internet the machine can have
as many names as you wish merely by placing the correct records into
DNS.

For AD, Domain, and file sharing purposes in a Windows environment
(internal) that "computer name" set in the System Control Panel is more
critical to get correct.

>> Thanks
>
> Hi - someone else may post with more specific advice, but mine is - find a
> reliable (public) DNS host, ideally a company that has a decent datacenter
> to support it, and have them be authoritative for this domain. You are
> unlikely to have that same infrastructure on your own network....and if
> you're asking the question you are now, perhaps it would be best to leave
> this in the hands of people who do it for a living. I mean no offense by
> this. :)

Good advice.

Very few companies should host their own DNS PUBLIC servers.

My recommendation is generally GoDaddy for both price, features,
and reliability.

Only problem I have had with GoDaddy is their lack of change control
notification when making significant changes to the DEDICATED
servers (not DNS per se.)