Re: Network board to accept DHCP address?

[Craig Johnson]

There are a number of aspects to this that I have questions about.
Here are some thoughts to get you started.

1. It may not be the best thing to get rid of the router. I have set
up many BMgr servers that sit behind other routers, with the router (at
least) doing NAT. Often the BMgr server also doing NAT. One reason to
keep the router in place is to allow it to do DHCP for you and present
a fixed ip address for BMgr. BMgr filtering is going to be a nightmare
if its public address keeps changing.
2. If you have a SLES box as the DHCP client, it may be somewhat easier
to deal with than having a NetWare box as the DHCP client. But overall
I think it will still be easier to have a simple router in place doing
DHCP and NAT (and probably port forwarding) while presenting a fixed
target (default gateway) to the internal firewall.
3. DNS should not be a problem here. You can set it up on any internal
host server easily (Windows, Linux, NetWare or combo of them) as long
as they can reach the internet to forward DNS requests. I recommend
you set them up as forwarders to your ISP's DNS servers. DNS servers
will not be used by your internal hosts unless you point the hosts to
them, usually with DHCP. Set up DNS, and test it using nslookup,
before changing DHCP settings to point to them.

Craig Johnson
Novell Support Connection SysOp