totally screwed up :/
From: Eric (eric_at_hotmail.com)
Date: 08/10/04
- Next message: Glen Williamson: "Re: Unable to find Primary DNS"
- Previous message: Adrian Marsh: "Re: Restoring DNS Primary"
- Next in thread: Lanwench [MVP - Exchange]: "Re: totally screwed up :/"
- Reply: Lanwench [MVP - Exchange]: "Re: totally screwed up :/"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Aug 2004 13:24:13 +0200
OK! Back to the drawing board. We have:
- An internal network with clients that log on to an win2k-server dhcp,
let's call it mainframe. We also have exchange server on this computer.
- A firewall.
- A webserver that's in the dmz, let's call it webserver.
The trafic goes through the firewall on one wire to the webbserver in the
dmz, and on another wire to the rest of the net (where the mainframe is).
The problem (as I described it yesterday) is that we can't use the full
domain name from the clients *inside*the firewall, ie not use
www.domain.com, and we want that. Kevin D helped me out yesterday by
suggesting that we created a www.domain.com -zone with the ip to the
webserver. That worked great but what I didn't know was that the mainframe
(where I pulled this trick) acts as the primary DNS-server so now all the
nameservers on the Internet points to an internal adress that doesn't
work...
The thing is that the guy who set this EXCELLENT sollution up is long gone,
and I ain't good at it, but that's how it is.
It *seems* like AD is used, and it seems like the webbserver acts as an
secondary DNS (I don't know the use of that because we have a DNS from our
ISP as well) but any ideas of how to get things rolling?
/e
- Next message: Glen Williamson: "Re: Unable to find Primary DNS"
- Previous message: Adrian Marsh: "Re: Restoring DNS Primary"
- Next in thread: Lanwench [MVP - Exchange]: "Re: totally screwed up :/"
- Reply: Lanwench [MVP - Exchange]: "Re: totally screwed up :/"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
