Associate
- Joined
- 1 May 2006
- Posts
- 810
- Location
- Bristol, UK
Morning all.
I'm going to be using today to set up Windows Server 2003 with Active Directory on a spare box. I've done lots of testing with virtual machines and I've got a setup checklist written down.
The one problem I'm having is with DNS. Normally a single server would also be connected to the internet and be used for routing and NAT. However, we already have a linksys router (running DD-WRT) which does a damn fine job of distributing our internet and the powers that be are reluctant to shift it since it's only a little project for myself. This means that the server will be connected to the router as a client. So all DNS requests from my desktop for example, go straight to the router and out to the internet (via our ISP DNS's), completely ignoring my server thus resulting in a whole host of problems.
DD-WRT is able to act as a DNS server, so I guess one option is to replicate the entire DNS structure from the server to the router, which won't be too laborious since there will only be 2-5 workstations. Failing that I could add the server IP to the 'dns servers list' on the client machines.
Was just wondering if anyone else had any other methods that are cleaner, for example any dns requests for 'locallan.example.com' (for example) are routed straight to the server.
TIA,
Freakish_05
I'm going to be using today to set up Windows Server 2003 with Active Directory on a spare box. I've done lots of testing with virtual machines and I've got a setup checklist written down.
The one problem I'm having is with DNS. Normally a single server would also be connected to the internet and be used for routing and NAT. However, we already have a linksys router (running DD-WRT) which does a damn fine job of distributing our internet and the powers that be are reluctant to shift it since it's only a little project for myself. This means that the server will be connected to the router as a client. So all DNS requests from my desktop for example, go straight to the router and out to the internet (via our ISP DNS's), completely ignoring my server thus resulting in a whole host of problems.
DD-WRT is able to act as a DNS server, so I guess one option is to replicate the entire DNS structure from the server to the router, which won't be too laborious since there will only be 2-5 workstations. Failing that I could add the server IP to the 'dns servers list' on the client machines.
Was just wondering if anyone else had any other methods that are cleaner, for example any dns requests for 'locallan.example.com' (for example) are routed straight to the server.
TIA,
Freakish_05
