Domain Name Registrations

[Yay Deutschland!]

Hello

I am a newbie to DNS registrations and I want to register a domain name on
the internet, lets say myname.com with "CompanyX", and then run the name
server ns1.myname.com and ns2.myname.com myself using Windows 2003 DNS on
Active Directory. My question is, after I regestered and paid for my domain,
do I tell "CompanyX" to forward ns1.myname.com and ns2.myname.com to two of
my external IP addresses as the delegation record?

After the delegation is complete, do I have to setup Windows 2003 DNS upload
my DNS records to the "CompanyX"'s servers? or do I have to open up a port
like Port 53 so internet users can get into my ns1 and and ns2 servers? It
is very strange because I know a friend that does this they have a ns1 and a
ns2 and they don't have Port 53 forwarded to it, but those servers somehow
know how to "respond" to requests from the internet.

Thanks

 

[Herb Martin]

Hello

I am a newbie to DNS registrations and I want to register a domain name on
the internet, lets say myname.com with "CompanyX", and then run the name
server ns1.myname.com and ns2.myname.com myself using Windows 2003 DNS on
Active Directory.

Ok, but you should let the REGISTRAR company
handle the DNS for the Internet side.

You will (should) only supply your internal DNS
on AD.

My question is, after I regestered and paid for my domain,
do I tell "CompanyX" to forward ns1.myname.com and ns2.myname.com to two of
my external IP addresses as the delegation record?

No. Delegation for this is ONLY done at the "parent"
zone (e.g., com. in this case). That is handled by the
ACT OF REGISTERING -- you supply the IP addresses
of 2 (or more) DNS servers, or as mention above, it is
better to just let the Registrar do this for you.

After the delegation is complete, do I have to setup Windows 2003 DNS upload
my DNS records to the "CompanyX"'s servers? or do I have to open up a port
like Port 53 so internet users can get into my ns1 and and ns2 servers?

One hopes not. But were you really going to do this
(don't) then yes you would have to open both UDP
and TCP 53 (if you won't to allow for all legal queries).

This is ONE of the reasons you don't want to do it this
way.

It
is very strange because I know a friend that does this they have a ns1 and a
ns2 and they don't have Port 53 forwarded to it, but those servers somehow
know how to "respond" to requests from the internet.

Forwarding is something else entirely.

Leave your Internet DNS with the registrar.

Setup the internal version of the zone for YOUR
network users ONLY -- set all of them to use your
internal server only -- including the DC/DNS and
other servers (they are DNS clients too).

Have your internal DNS servers forward to your
ISP for external resolution (yes you will open
53 but only for OUTBOUND requests and their
responses.)

Think of you internal zone, and the Internet version
of the zone as TWO DIFFERENT zones even though
they happen to have the same name.