Re: Network question and SQL

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mike Hodgson (mwh_junk_at_hotmail.com)
Date: 12/20/04


Date: Mon, 20 Dec 2004 11:05:38 +1100

Another thing to bear in mind is if you reference your SQL servers from
inside any DMZs. All decent firewalls these days refer to specific host
addresses, so if your SQL server does happen to get a new IP address
from a DHCP server then your firewall rules to that server will stop
working and your DMZ servers referencing your internal SQL boxes will break.

I can't really think of any particularly good reasons to allocate IP
addresses to servers via DHCP on an internal LAN. I'd say the cons
(increased reliance on DHCP servers, DNS servers, firewall rules, etc),
as John implied, far outweigh the pros (are there really any pros?).
All my SQL servers will always have static addresses if I have any say
in it (which I currently do).

Cheers,
Mike

John Bell wrote:
> Hi
>
> Alot of places have permanently allocated IP addresses for all their servers
> either "hard coded" (excluded) or reserved through DHCP. As your server
> should be up most of the time it will not be relinquishing the IP address
> therefore the main thing DHCP will give you is management (you will know all
> IP addresses are listed there) and the automatic updating of the DNS
> (assuming this is switched on). If you start having printers or other
> devices that are not DHCP capable, then this starts to fall down.
>
> Other things to consider would be the number of subnets that are being
> managed and the potential increase in the importance of the DHCP server. You
> will have to make sure that you don't loose information held on your DHCP
> server if it goes down, this will not be as important if it was only being
> used to deliver transient IP addresses. It may also increase your recovery
> time in case of failure.
>
> John
>
>
> "Hassan" <fatima_ja@hotmail.com> wrote in message
> news:uSt9XjY5EHA.1760@TK2MSFTNGP10.phx.gbl...
>
>>We are looking at implementing a new network at another customer site and
>>the customer wants to use DHCP for all his SQL Servers.
>>I am aware that permanent IP addresses are good . Can someone give me the
>>pros and cons of whats ideal and why ? Links to any supporting documents
>>would be helpful
>>
>>
>>
>
>
>



Relevant Pages

  • Re: medical records, web server, & stateful firewall vs packet filter
    ... > image and SQL servers directly (the image server link in particular ... The image and SQL servers ... the 2 firewall layers should run different s/ware - the idea is that a major ... security always cost a lot more than you expect (this comes up whenever we ...
    (comp.dcom.sys.cisco)
  • Re: DHCP assinged DNS servers dont work
    ... Although the WinXP firewall is enabled and configured via Group ... The first two DNS servers are AD controllers running ONLY core ... I have 75 WinXP machines on a Win2K3 domain using DHCP for address ...
    (microsoft.public.windows.server.networking)
  • Re: networking private and public hosts questions
    ... DHCP isn't going to "help". ... you need to run NAT. ... Move all the Servers to the private side of the Firewall and start ... Controllers must point to themselves in thier DNS Setting and the ISP's DNS ...
    (microsoft.public.win2000.networking)
  • Re: Dynamic DNS, DNS Records & Scavenging
    ... There are two DHCP ... Both the servers are set to update A and PTR records for clients. ... DNS however this doesn't seem to be the case. ... DNSUpdateProxy and when i did this i saw my test laptop register its ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP
    ... Open the event in event viewer, under the 2 arrows is a copy button, click it and paste it into the posting. ... "Meinolf Weber" wrote: ... I do not intend to change DNS or DHCP servers. ...
    (microsoft.public.windows.server.general)