Member Avatar for Nemuksis

Hi,

I have my own registered domain. I want to set up my own DNS server and host a website completely independent of any third party hosting service. I have Windows Server 2003 (I am new to this terminology and am not sure if I am using it correctly). Lets say my domain is xyz.com How do I go about setting up this infrastructure so that I can have my own DNS set up and host my website ?

Any tut's/guides is highly appreciated.

server is hosted with

  • 3 Contributors
  • 2 Replies
  • 219 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by rhandore

Dani AI

Generated

A practical supplement to the existing replies from , and .

Running an authoritative DNS for a domain is straightforward technically but carries operational, security and delegation requirements. ’s caution about using registrar/third‑party DNS is well-founded — those services handle redundancy, DDoS protection and ease of delegation. Contrary to ’s brief note, there is no separate “ICANN signup” for a personal nameserver; delegation and any glue records are created through the domain registrar, which communicates with the TLD registry.

Minimal checklist for a self‑hosted Windows DNS setup (practical, not exhaustive):

  • Obtain static public IP(s) and confirm the hosting provider allows inbound UDP/TCP port 53 (and 80/443 for web). If behind NAT, arrange correct 1:1 mapping.
  • On the Windows box create a primary (authoritative) zone for the domain, add A records for hostnames (www, mail) and A records for the nameserver hosts (ns1/ns2). Add matching NS records inside the zone.
  • At the registrar create host/child nameserver entries (glue) that map ns1/ns2.domain to the public IP(s), then set the domain’s authoritative nameservers to those hostnames.
  • Use at least two authoritative servers on different networks when possible; a single server is a single point of failure.

Security and operational notes:

  • Do not run an open recursive resolver — disable recursion or restrict it to trusted IPs, and limit zone transfers to authorized secondaries.
  • PTR (reverse DNS) is controlled by the IP owner (host/ISP); coordinate PTRs with them if needed for mail delivery.
  • Windows Server 2003 reached end of support years ago; exposing it to the Internet is high risk — upgrade or place DNS behind a hardened, modern resolver/authoritative service.

Quick external checks (run from another network):

nslookup -type=NS example.com 8.8.8.8
dig +trace example.com
nslookup www.example.com ns1.example.com

Also verify delegation from multiple public resolvers and consult the registrar’s “register nameserver/host” documentation when creating glue.

Recommended Answers

All 2 Replies

Member Avatar for pjdg

Hi,

I have my own registered domain. I want to set up my own DNS server and host a website completely independent of any third party hosting service. I have Windows Server 2003 (I am new to this terminology and am not sure if I am using it correctly). Lets say my domain is xyz.com How do I go about setting up this infrastructure so that I can have my own DNS set up and host my website ?

Any tut's/guides is highly appreciated.

server is hosted with

Greetings and Felicitations

You say you are new to the terminology, I don't know if this also means you are relatively inexperienced, however, I really don't recommend running your own DNS servers. You are almost always better-served by using your registrar, hosting service or a third-party DNS provider.

But if you are determined, the basic process for setting-up your DNS would be to first add A records to your domain, for the name server, then register your name server. This is different from specifiying which name server to use for your domain.
The process does vary from registrar to registrar and you will have to research your registrar's documentation to discover their process on exactly how to do this.

To register a name server the domain name and IP address need to be specified, you are basically declaring that this is a name server and nothing else. The domain, or domains, the name server resolves is not specified.

Once registered you can reference your name server in exactly the same way as you would reference your registrar's, your hosting provider's or third-party name servers. Create NS records, giving the names of your name servers.

However, this is a very basic overview and unless you are really adventurous and ready to resolve a number of problems, I would suggest you do not go down this path. There are easier ways of skinning DNS ... ;)

I wish you much luck - and keep smiling

Member Avatar for rhandore

Hello,

First of all, you need to register your DNS server with ICANN (Internet Corporation for Assigned Names and Numbers) for anyone to actually find it. The easiest way is to register a domain on somewhere like GoDaddy or another domain hosting site that will let you manually edit the DNS records or at least set up forwarders to your own DNS.

thank you

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.