M
me
My co -worker at work originally posted an issue with our W2k DNS server
that we haven't resolved. The situation wasn't described in full so
hopefully this is a better description.
Our mail server is known to the public as xyz.com, which is also the name of
our w2000 domain.
Because of the way Win 2000 dns is, every domain controller server on the
network sees itself as xyz.com. If I do a trace route to xyz.com, at any
given time, I will get a different server IP address -- rarely the real
one, and usually the other ones. Because of the way our email server works,
users login to the server at xyz.com/login, and xyz.com is their email
address. They can't login to the xyz.com server while using the Win2000 dns
server [ the wrong server responds]
This is not a problem from outside the network, just when accessing that
server internally, with the W2000 dns server.
We have a separate unix dns server which manages this information correctly
and provides the correct information -- inside and outside. Short of change
the name of our domain, is there any way to correct this issue-- so that a
windows 2000 dns server knows who the real xyz.com server is? [Everyone
can't be xyz.com]
Original question:
O.K. This gets complicated very quickly! Our school system is
running a Windows 2000 domain. Our FQDN is cartersville.k12.ga.us.
We have an e-mail server that can be accessed through a web browser
and it has a web server built in so that e-mail users can have their
own web site. You access mail from the web browser by using the FQDN
as opposed to our normal website that has the 'www' prefix. The
e-mail server also has a web server built in that redirects to our
main web server if someone uses the FQDN but DOES serve up web pages
for specific users, i.e. if you type
cartersville.k12.ga.us/ajohnson/homework, it will bring up the
homework for the teacher AJohnson. The problem is that our Windows
2000 DNS won't allow users to go to the inner web pages of the e-mail
server from within our network because the domain is
cartersville.k12.ga.us. It works fine from outside our network in.
If I ping our FQDN I'll get one of our three domain controllers. It's
not practical to change anything on the mail server and I'm sure
there's something I could change in DNS if I only knew what.
that we haven't resolved. The situation wasn't described in full so
hopefully this is a better description.
Our mail server is known to the public as xyz.com, which is also the name of
our w2000 domain.
Because of the way Win 2000 dns is, every domain controller server on the
network sees itself as xyz.com. If I do a trace route to xyz.com, at any
given time, I will get a different server IP address -- rarely the real
one, and usually the other ones. Because of the way our email server works,
users login to the server at xyz.com/login, and xyz.com is their email
address. They can't login to the xyz.com server while using the Win2000 dns
server [ the wrong server responds]
This is not a problem from outside the network, just when accessing that
server internally, with the W2000 dns server.
We have a separate unix dns server which manages this information correctly
and provides the correct information -- inside and outside. Short of change
the name of our domain, is there any way to correct this issue-- so that a
windows 2000 dns server knows who the real xyz.com server is? [Everyone
can't be xyz.com]
Original question:
O.K. This gets complicated very quickly! Our school system is
running a Windows 2000 domain. Our FQDN is cartersville.k12.ga.us.
We have an e-mail server that can be accessed through a web browser
and it has a web server built in so that e-mail users can have their
own web site. You access mail from the web browser by using the FQDN
as opposed to our normal website that has the 'www' prefix. The
e-mail server also has a web server built in that redirects to our
main web server if someone uses the FQDN but DOES serve up web pages
for specific users, i.e. if you type
cartersville.k12.ga.us/ajohnson/homework, it will bring up the
homework for the teacher AJohnson. The problem is that our Windows
2000 DNS won't allow users to go to the inner web pages of the e-mail
server from within our network because the domain is
cartersville.k12.ga.us. It works fine from outside our network in.
If I ping our FQDN I'll get one of our three domain controllers. It's
not practical to change anything on the mail server and I'm sure
there's something I could change in DNS if I only knew what.