WIN2k:setting up DNS different from ISP

[RyanO]

I am running win2k internal network, for internet access I use a DSL account from VERIZON.

I have an SMC wireles router, My internal network is 192.168.123.0, my gateway is 192.168.123.254, and my DNS is my ISP dns obviously.

My goal is to get a my own registered domain, run a web server and Email server internally,(tis is for study lab purposes only, so bear with me) How would I configure my Domain,DNS and MY domain suffix, since I want to use Verizon only for interent connectivity?

The win2k server, its the only server in the network, an it is my domain controller.

if there is a document or webpage that you could redirect me that explain this. I will appreciate that too!

Thank you

 

[JackMDS]

Having your own domain registered does not provide you with an access to the Internet. You either host your site elsewhere, or you use the current connection pointing to your sever via DNS service (Doing so, may be a violation of your ISP contract).

DNS Service: http://www.zoneedit.com/


For $3.95 a month, you can put it here: http://www.3-95.com/

 

[RyanO]

That is why I said, I want to use my DSL connection to access the internet.
My question is how to make it all work if I was using a dynamic DNS from dyndns.com, usind windows 2000 as a domain controller.
I tried it and I lost connectivity to the net.

 

[JackMDS]

You can not connect to the Internet without Verizon. Your DSL is not an open conduit to the Internet looking for DNS; it connects through your Verizon account.

DNS service takes the traffic that is directed toward your domain, and uses Verizon to send it to you, (which is probably illegal as far as Verizon concern).

 

[RyanO]

It is a giving, that I can not connect to the net without Verizon.
I am not making myself clear.

Right now I am connected to the net, via Verizon, using my Winme desktop as the client that is directly connected, to my DSL modem.
I have an wireless SMC router, so the DSL modem is connected to the router so are all other clients and my win2k server.
So my network has been working for a long time.

All I want to accomplish is to make my Win2k a PDC, have all my machines authenticate through my PDC, to access my locall resources
Also setup an IIS server and Exchange server, in my internal network, this is solely with the purpouse to have a lab for my studies.

My question was, If i get dyndns.org dynamic dns server, how would I implemented into my network, since my IP is not static.
And believe there is not violation of any here...you could say that because I have multiple computers behind my DSL connection, but that depends and changes from ISP to ISP.

Thanks

 

[quxio]

I've got something similar to what you're trying to do. I use d2g.com for dynamic DNS service. The difference is that I've for a win2k server with AD instead of a domain structure. I've also got everything behind a SMC barricade router/switch.

First I installed win2k sevrer. Then I dcpromo'ed it and made a new forest and a new tree. I named the directory after the DDNS name (for you it would be the name given to you by dyndns). The server has DNS service installed and points to itself for DNS queries. After you've got DNS on the server installed, it should be able to hit the 'net without your ISP's DNS. You can configure DHCP to configure the IP parameters of clients.

I also have exchange2k installed on the server. Since my AD domain is the same name as the DDNS name, I can even make accounts in exchange that can send/receive from the internet, not just internally.

Having everything on one box isn't really the most secure/intelligent way to go as far as Microsoft is concerned, but for learning purposes, it'll do.

 

[RyanO]

Quxio!
Quxio!
Quxio!:

: Finally someone that understand what I am trying to do.
You actually have everything that I want to accomplish, even the Equipment, I have the SMC Barricade and also want to use win2k server and I want to integrate DNS to Active Directory, and setup exchange server.

Could you please! ICQ me 63131529, Your advise will save me couple days of extra work.

Setting the DNS in Win2k is not trivial.

Do I need to buy a domain name or can I just use Free DNS type service?

You could also email mockingbirdie@hotmail.com

Thanks much

 

[n0cmonkey]

If both the IIS and Exchange machines are for internal learning purposes, keeping them off the net would be best. I wouldnt worry about a domain name and just use something for your internal network. If you want to foolishly put a testing (ie non-production, I dont know what Im doing yet, I hope that the last patch for the month) IIS/Exchange server on the internet, just use the free services that dyndns.org and others provide.

As far as putting IIS and Exchange on the same machines, thats stupid. Split them up. You have money, you proved that by being able to afford exchange. Just buy another machine and Win2k server license and you should be set.

EDIT: Oh yeah, and asking for help in other ways is ok, but it doesnt help anyone else. Being greedy with help on a help forum isnt very nice.

 

[RyanO]

Understood!

I am just excited that I am trying to accomplish, what he already did.
This not a production enviroment, just for me to play with IIS 4.0 and Exchange, I am out of work since I relocated to another state and Jobs in IT are rare this days in Oregon.

I have a couple of leads that requires me to be sharp in IIS and Exchange for the interview, just in case I get the opportunity

Thanks

 

[spidey07]

Will you tell them that you used unlicensed software?

 

[RyanO]

Only if you tell them first about your unlicensed software.
As you can see I can make the same assumption about you and you can make an ASS out yourself on your own time.

Thanks for helping

 

[Saltin]

<< After you've got DNS on the server installed, it should be able to hit the 'net without your ISP's DNS. >>



Q, this means your DNS server is using root hints to reach the DNS servers on the net. This is fine, but it's not perfect.
What you should do, is configure your DNS server to forward to your ISP's DNS. This can be set in the properties of the server object in the DNS snap in.
Your ISP's DNS server is a hell of a lot closer to yours (hop wise) than the root hint Internic DNS servers. It saves time, and follows the hirearchical nature of DNS.

 

[n0cmonkey]

<<

<< After you've got DNS on the server installed, it should be able to hit the 'net without your ISP's DNS. >>



Q, this means your DNS server is using root hints to reach the DNS servers on the net. This is fine, but it's not perfect.
What you should do, is configure your DNS server to forward to your ISP's DNS. This can be set in the properties of the server object in the DNS snap in.
Your ISP's DNS server is a hell of a lot closer to yours (hop wise) than the root hint Internic DNS servers. It saves time, and follows the hirearchical nature of DNS. >>



While it may be a better idea to use the isps dns servers, they wont setup my internal network into their dns server. So for me, its easier to keep my BIND skills sharp if I use the software. Granted, lookups take a little longer, but I can live with that so I can better understand the software.

EDIT: Id also like to see anyone find unlicensed software on *MY* machines

 

[quxio]

<< Q, this means your DNS server is using root hints to reach the DNS servers on the net. This is fine, but it's not perfect.
What you should do, is configure your DNS server to forward to your ISP's DNS. This can be set in the properties of the server object in the DNS snap in.
Your ISP's DNS server is a hell of a lot closer to yours (hop wise) than the root hint Internic DNS servers. It saves time, and follows the hirearchical nature of DNS. >>



That's true, but for my testing purposes, speed to the internet from the server isn't a priority. Having my own DNS use root hints allows my internal client computer to resolve the internal network faster. Not that the speed is all that much anyway...

RyanO, sorry, no ICQ here.

Actually, for me, installing the DNS wasn't a problem. When I installed AD, I chose to let the installation install the DNS. It does it's thing and after a reboot, everything should work. The only problem I had was a bit of impatience on my part. After logging in, I immediately went to the DNS to check it out, only to find that it had not populated. Gotta wait a few seconds for that.

To install exchange, I went ahead and did the recommended /forestprep and /domainprep and then setup. The setup seems to be able to do these steps by itself, but whatever. Exchange does its own thing and makes DNS entries, blah, blah, blah. Setup a few test accounts, open ports on the router, and off you go.

You don't have to buy a domain name. Like I said, I use d2g.com from deerfield so my AD name is (name).d2g.com and email accounts are (name)@(name).d2g.com. The server runs d2g.com's client that notifies them of my external IP.

If you're going to use IIS, I learned that unlike most other routers and ftp daemons behind them, for some reason, you don't use passive mode on the client. I always heard the opposite and it was that way with a previous Linksys router I had before the SMC. Makes you wonder about SMC....

P.S. I use trial versions of server and exchange