Setting up a DNS Server

[joohang]

I have a Windows 2000 domain controller that uses a fake domain name called "ocarina.net"

It is on an ADSL connection and I use ISA Server as a firewall/proxy. At the moment, the purpose of the server is a development and testing.

I wanted to host some of my sites own my own recently. Can I upgrade my ADSL plan to the one with one static IP and hosting allowed, and then register this server as the DNS server for a domain like "joohang.net"?

 

[Hoober]

Bump for good thread. I'd like to know, too.

 

[joohang]

Bumpy

 

[spidey07]

maybe your dsl provider has a "business" class DSL offering?

But sure, you could run your own DNS server and register it for whatever domains you want to host. At that point your DNS server would be "authoritative" for that domain.

Or even easier and more robust, don't be the primary DNS server for a domain...instead be a secondary where you are only backup up a primary.

 

[DnetMHZ]

another possibility would be to host the sites yourself and leave the DNS up to a
free service like zoneedit.com you can setup I believe 5 domains for free
and it works very well. nice web interface for making changes, etc.

just an idea

DnetMHZ

 

[randal]

Once you get a static IP, you can specify your own computer to be the dns server ... it's customary to *not* run dns and iis on the same machine; that's not that important, though

yes, you can do it. should you? depends on if your dsl provider allows servers. also depends on if you want to actually run your own dns server; there are a few free internet-based and web-adminable dns server services out there; using them would be what i would do.

$.02
randal

 

[joohang]

The point of this server is mainly for learning.

I want to build a domain controller with a real domain, do some playing/testing with the latest .NET Enterprise goodies, and host some of my sites on it.

My DSL provider does have a business plan. Only costs $95/month Canadian for one static IP with hosting allowed. 1.5 Mbps / 512 Kbps connection.

I thought about using zoneedit. If I find it too annoying to configure for DNS, I'll just use that instead.

spidey07: Could you explain a bit more about setting it up as a secondary DNS? Would my provider's DNS be the primary? Or you mean I should set something like zoneedit as primary and my server as secondary?

 

[joohang]

<< Once you get a static IP, you can specify your own computer to be the dns server ... it's customary to *not* run dns and iis on the same machine; that's not that important, though >>



This server is NOT mission critical in any way. I can always add a new Duron server for $500 Canadian. Actually, I might have a server cluster soon with 2 or 3 Duron servers to play around with Application Center 2000. Isn't life grand?

 

[randal]

even though the *nix world has had it forever, I must say that MS's implementation of load balancing and clustering is pretty good. multiple computers doing one task in parallel makes things much smoother =)

We use win2k at work, and setting up DNS is not that difficult at all ... just not for the faint of heart; if you screw up once early on, it'll bite you hard down the road.

I don't know who your ISP is, but ask them if they'd be willing to do DNS for you ... if they agree, then set your machine up to be secondary to it, and supply that info into your registrar --- easy as pie.

there are lots of walkthroughs for ms dns ... the microsoft knowledge base is quite extensive and helpful in setting it up.

$.03
randal

 

[joohang]

Most people I know who claim *nix to be SOOOO superior to Windows 2000 tend to be zealots who think they understand Microsoft's latest technologies from press releases and crappy media like ZDNet articles.

I am very impressed with Microsoft. Just think back 5~6 years ago when they first took Internet seriously. Now look how much they achieved now.

IE is the most superior web client of all browsers without a doubt. To anybody who debates with me on this one, I can make counter-argue with some very strong statements.

Then look at IIS, COM, ASP.. and soon .NET equivalent technologies that replace (or coexist with) them. Sure there are security flaws and bugs, and I admit that Microsoft are usually favourite targets for creating exploits and viruses, but no system is perfect and I've seen so many solutions that just WORK using Microsoft products.

Just look back at Microsoft 5 years ago and compare it to where they stand now. I don't know about you, but I'm damn impressed.

Went really off topic (thanks to randal ) so I'll stop here.

 

[joohang]

<< We use win2k at work, and setting up DNS is not that difficult at all ... just not for the faint of heart; if you screw up once early on, it'll bite you hard down the road. >>


That's why just about every Microsoft staff I've talked to emphasized PLANNING as the most important issue for implementing AD.

90% of the time, admins who complain about Microsoft screw things up because they believe that they can figure things on their way through with their existing knowledge/skills. i.e. &quot;This looks like LDAP. Oh it's easy. I can just do it. I know it already.&quot; (WRONG!) Another common mistake seems to be: GUI (i.e. MMC) = easy = therefore no need to get trained.