Building a new web/mail server...got DNS questions...
Hello experts!@
Hey, it's been a while since I've done this, so I'm just trying to get my facts straight...
Okay, so I have a Dell Poweredge server that I'm going to be turning into a web server and email server for approximately 10 domains. So my understanding is that I need to have 3 services in place:
1. DNS Server
2. HTTP Server
3. SMTP/POP3 Server
So, I'm going to use windows DNS, IIS6, and a free package recommended called mail enable (for SMTP/POP).
In setting up dns, I made a "zone" for each domain ie:
mycompany.com
siteA.com
siteB.com
siteC.com
and so forth...
Using IIS6 "host headers" feature, and with the server pointed to use itself for DNS all this works fine. The problem arises when I try to access these sites from elsewhere on the net, or if I use nslookup.
I'm thinking that I'm missing something about the DNS config...not on the server itself, but somewhere else. I should know this, but I've haven't done MIS stuff like this in a while.
So, here's the question, installing Windows2003 DNS services on a machine with a public IP address isn't enough to make it a "true DNS server" is it? Doesn't something else have to be done? like with my isp or something?
Most of "the sites" are registered with Network Solutions or melbourne.it, and really what I want to do is simply say on those sites that "ns1.mycompany.com" is the nameserver...then I can have it so all I have to do is tweak the DNS configuration on that server.
Anyway, I hope that makes sense...I can easily give more information about this if needed.
Thanx!
=neo
Hey, it's been a while since I've done this, so I'm just trying to get my facts straight...
Okay, so I have a Dell Poweredge server that I'm going to be turning into a web server and email server for approximately 10 domains. So my understanding is that I need to have 3 services in place:
1. DNS Server
2. HTTP Server
3. SMTP/POP3 Server
So, I'm going to use windows DNS, IIS6, and a free package recommended called mail enable (for SMTP/POP).
In setting up dns, I made a "zone" for each domain ie:
mycompany.com
siteA.com
siteB.com
siteC.com
and so forth...
Using IIS6 "host headers" feature, and with the server pointed to use itself for DNS all this works fine. The problem arises when I try to access these sites from elsewhere on the net, or if I use nslookup.
I'm thinking that I'm missing something about the DNS config...not on the server itself, but somewhere else. I should know this, but I've haven't done MIS stuff like this in a while.
So, here's the question, installing Windows2003 DNS services on a machine with a public IP address isn't enough to make it a "true DNS server" is it? Doesn't something else have to be done? like with my isp or something?
Most of "the sites" are registered with Network Solutions or melbourne.it, and really what I want to do is simply say on those sites that "ns1.mycompany.com" is the nameserver...then I can have it so all I have to do is tweak the DNS configuration on that server.
Anyway, I hope that makes sense...I can easily give more information about this if needed.
Thanx!
=neo
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I also recomend a strong firewall (like the Symantec SGS 5600 series) between your server and the internet.
Erik Bjers
VPN Network Engineer
SAIC
erik.c.bjers@saic.com