Re: Any Way to Not Assign DNS Name to IP Address?
- From: "Bill Grant" <not.available@online>
- Date: Mon, 8 May 2006 13:08:45 +1000
Who told you that you cannot have two or more scopes for the same
network? It is pretty much standard practice to have multiple scopes on a
DHCP server and use DHCP relay to allocate addresses to different IP subnets
on different segments of the network.
Will wrote:
We want each segment to receive different DHCP settings. The default
routers are different for each segment, for example.
This requires differerent DHCP Scopes, and you cannot have two DHCP
Scopes for the same network. Microsoft requires each scope to be
on a different port of the DHCP server.
So, no, a DHCP relay is not a solution for the requirement I
originally put forward.
"Bill Grant" <not.available@online> wrote in message
news:ehNKqCXcGHA.3348@xxxxxxxxxxxxxxxxxxxxxxx
You do not need to have a second NIC in the DHCP server machine.
All that you need is a machine in that segment which can do DHCP
relay. The relay server has an IP in the new subnet. It receives the
broadcast request and forwards it directly to the DHCP server. DHCP
allocates an IP address in the same IP subnet as the relay agent.
Will wrote:
I have a DHCP server that I am trying to add a second port on, to
assign different DHCP settings to a separate network with its own
DHCP Scope. I want this new ethernet to *only* be used for DHCP.
In an ideal world, I would not even enable IP on this adapter, and
would like it to only respond to DHCP requests. Unfortunately, the
Microsoft DHCP server has the unfortunate feature that you assign
DHCP scopes at the server level by IP addresses of the network
interfaces, rather than by the network interface names. It would
have been nice to assign a particular ethernet interface to the
scope I wanted, and deactivate all TCP/IP on that adapter.
In the meantime, the new ethernet does have an IP address, and as a
result DNS is now resolving the DHCP server to both of those IPs.
This is causing a number of problems since that server is also a
file server and we would prefer all access to that server to go
through a firewall on a single controlled segment. We disable
file sharing on the other segments, but hosts on the new DHCP
segment use DNS to resolve the file server name and attempt file
share access on the wrong network address.
Is there a way to control DHCP so that the hostname used for the new
DHCP segment on the DHCP server will be some different name than the
default hostname used on other segments?
.
- Follow-Ups:
- References:
- Any Way to Not Assign DNS Name to IP Address?
- From: Will
- Re: Any Way to Not Assign DNS Name to IP Address?
- From: Bill Grant
- Re: Any Way to Not Assign DNS Name to IP Address?
- From: Will
- Any Way to Not Assign DNS Name to IP Address?
- Prev by Date: Re: NET SNED requirement in Windows 2003
- Next by Date: Browse a server on a different subnet
- Previous by thread: Re: Any Way to Not Assign DNS Name to IP Address?
- Next by thread: Re: Any Way to Not Assign DNS Name to IP Address?
- Index(es):
Relevant Pages
|
Loading