Re: Running my own nameserver
From: Herb Martin (news_at_LearnQuick.com)
Date: 02/21/05
- Next message: Jeff Cochran: "Re: Running my own nameserver"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: Curious???"
- In reply to: Nate_at_communities.nospam: "Re: Running my own nameserver"
- Next in thread: Jeff Cochran: "Re: Running my own nameserver"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 20 Feb 2005 21:53:16 -0600
<Nate@communities.nospam> wrote in message
news:OttG2P7FFHA.3664@TK2MSFTNGP15.phx.gbl...
> I understand what you have told me, that part im not figureing out is when
I
> go to register the domain name and it asks for the name servers I would
want
> to specify ns1.mynewdomainname.com and ns2.mynewdomainname.com however I
do
> not know where I specify the IP address for these name servers.
Don't do it that way. Where are you trying to register?
GoDaddy and Register.com both offer DNS servers for you
to use (you paid for it already) and theirs will already have
IP addresses -- in fact you don't "specify" them at all but
let the Registrar pick them (they have dozens.)
> somewhere
> you have to specify ns1.mynewdomainname.com points to my ip address and I
> don't know where that is. From what I can find it seems as though you have
> to register the nameserver its self somewhere but I cant figure out where.
Don't do that - you will end up with (something like):
mydomain.com NS dns1.register.com
That is, a DNS server at the registrar will handle your
DNS.
> Also, I already have DNS up and running for my network. I have created a
new
> forward lookup zone for the new domain and by default it has a SOA and NS
> record.
Well, that would be fine if you were going to use it publicly
(don't) and it had a PUBLIC address, but I am strongly advising
you to put the public DNS at the Registrar.
(It's free.)
> I will be adding a txt record for SPF and MX record also.
GoDaddy supports TXT for SPF, and the more expensive
Register.com does not.
> Do I need any other records?
A (and maybe some CNAMES) for www, (domainname.com), ftp,
smtp server (besides the MX).
You will also need a PTR in the Reverse zone but that has
NOTHING to do with the forward zone except that the MX,
A for the SMTP server, and PTR must all match (make sense
together.)
> I don't think so but since this will be my first publicly
> accessible DNS server I want to ensure that I am not missing anything.
GoDaddy supports TXT (for SPF etc.) but not the SPF
record itself.
This is not causing any problems since compliant systems
are checking BOTH TXT and SPF (as many DNS servers
don't support SPF directly yet.)
-- Herb Martin <Nate@communities.nospam> wrote in message news:OttG2P7FFHA.3664@TK2MSFTNGP15.phx.gbl... > I understand what you have told me, that part im not figureing out is when I > go to register the domain name and it asks for the name servers I would want > to specify ns1.mynewdomainname.com and ns2.mynewdomainname.com however I do > not know where I specify the IP address for these name servers. somewhere > you have to specify ns1.mynewdomainname.com points to my ip address and I > don't know where that is. From what I can find it seems as though you have > to register the nameserver its self somewhere but I cant figure out where. > > Also, I already have DNS up and running for my network. I have created a new > forward lookup zone for the new domain and by default it has a SOA and NS > record. I will be adding a txt record for SPF and MX record also. Do I need > any other records? I don't think so but since this will be my first publicly > accessible DNS server I want to ensure that I am not missing anything. > > "Herb Martin" <news@LearnQuick.com> wrote in message > news:OQlykR5FFHA.464@TK2MSFTNGP15.phx.gbl... > > <Nate@communities.nospam> wrote in message > > news:eBs6mr4FFHA.4004@tk2msftngp13.phx.gbl... > >> Can anyone tell me what I have to do in order to run my own internet Name > >> Server so I can host my own dns records? > > > > Install it on a machine. For Windows this means > > installing it on the Server product. > > > > If you wish to have your own "zones" you must then > > create the zone. > > > > If you wish to do all this on the INTERNET, then > > you need to purchase and register the name. They > > will ask for the names/IPs of your TWO (or more) > > DNS servers when you do that. They register you > > by placing these name (DNS servers) in the parent > > zone. > > > > For example, if you register NatePlace.com it gets > > delegated from the com. zone to your DNS servers. > > > >> It's my understanding that you have to register a name server somewhere > > but > >> searching Google for "name server" or "name server registration" only > >> come > >> up with information about registering domain names. > > > > For Internet DNS servers you are almost ALWAYS > > better off (small Internet presence companies) leaving > > your DNS with a quality registrar. > > > > Here's how to register a name and it will cost you > > less than $10: > > > > Go to www.GoDaddy.Com > > > > Pick a name. > > > > Pay for it. > > > > Make sure to specify that you want them to "park" the > > DNS on their DNS servers. > > > > You can edit your DNS records in a web page right > > there on their site. > > > > And if you don't like it you can move it or just not > > renew it next year, and then you will lose less than $10. > > > > > > > > > > > > > >
- Next message: Jeff Cochran: "Re: Running my own nameserver"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: Curious???"
- In reply to: Nate_at_communities.nospam: "Re: Running my own nameserver"
- Next in thread: Jeff Cochran: "Re: Running my own nameserver"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
