To assign a static IP to a domain in IIS on Windows Server 2022, you must first configure the server’s network adapter with a fixed address and then bind that specific IP to your website within the IIS Manager. This process ensures that DNS records resolve consistently to the server’s actual network identity, preventing connection errors caused by DHCP lease changes or misconfigured host headers.
Configure the Network Adapter for Static IP
The foundation of this setup is ensuring the Windows Server 2022 machine itself has a permanent IP address. If the server obtains its address via DHCP, it may change after a reboot, causing your IIS bindings to break or your DNS records to become invalid. You need to manually set the IPv4 properties on the primary network interface.
Open the
Network Connections panel by pressing
Win + R, typing
ncpa.cpl, and hitting Enter. Right-click your active Ethernet adapter and select
Properties. In the list of items, locate
Internet Protocol Version 4 (TCP/IPv4), select it, and click the
Properties button.
In the new window, select
Use the following IP address. Enter the desired static IP address, Subnet mask, and Default gateway. Ensure the
Use the following DNS server addresses field contains the correct internal DNS server (often the local DC) if you are hosting internal domains. Click
OK to save these settings. The system will apply the changes immediately.
Create or Update DNS Records
Once the server has a static IP, you must ensure that your domain name points to this address. This involves configuring the DNS Server role on Windows Server 2022. If you do not have the DNS role installed, add it via
Server Manager >
Add Roles and Features.
Open
DNS Manager from the Administrative Tools. Expand your server node and locate your Forward Lookup Zone corresponding to your domain (e.g.,
example.com). Right-click the zone and select
New Host (A or AAAA).
Enter the hostname (e.g.,
www or leave blank for the root) and paste the static IP address you configured in the previous step. Check the box for
Create associated pointer (PTR) record if you also want reverse DNS resolution. Click
Add Host and then
Close. Verify the record exists by pinging the hostname from another machine on the network. For more details on managing DNS updates, see
Windows Dynamic DNS Update Issues at Boot.
Bind the Static IP in IIS
Now that the network and DNS layers are aligned, you need to tell IIS to listen on that specific IP address. Open
IIS Manager from the Start menu. In the left-hand Connections pane, expand the server node and click on
Sites.
Select the website you wish to configure. In the right-hand Actions pane, click
Bindings.... In the Site Bindings window, select the binding type (usually
http or
https) and click
Edit.
If the site does not exist, click
Add. In the Type dropdown, keep
http unless you are setting up SSL. In the
IP address dropdown, select the specific static IP you assigned earlier. Do not leave it as "All Unassigned" if you want strict control over which interfaces serve this content. Set the Port to
80 for HTTP or
443 for HTTPS. Under
Host name, enter your domain (e.g.,
www.example.com) if you are using host-header-based routing. Click
OK to save the binding.
Verify Firewall and Connectivity
After configuring the binding, ensure that Windows Defender Firewall allows traffic on the selected port. Go to
Control Panel >
Windows Defender Firewall >
Allow an app or feature through Windows Defender Firewall. Ensure that
World Wide Web Publishing Service is checked for both Private and Public networks. Alternatively, use PowerShell to verify inbound rules:
Get-NetFirewallRule -DisplayName "*Web*" | Select-Object DisplayName, Enabled, Direction, Action
Test the configuration by opening a browser on a client machine and navigating to your domain. If the page loads, the static IP assignment is successful. If it fails, check the Event Viewer under
Applications and Services Logs >
Microsoft >
IIS-IISManager for any binding conflicts.
Frequently Asked Questions
What happens if I change the server's IP after binding it in IIS?
If you change the network adapter's IP address without updating the IIS binding, the site will stop responding because IIS will still be listening on the old, non-existent address. You must update the binding in IIS Manager to match the new static IP immediately after changing the network settings.
Can I bind multiple sites to the same static IP?
Yes, multiple websites can share the same IP address and port combination as long as they have different Host Names configured in their bindings. IIS uses the Host Header to distinguish between the sites based on the domain name requested by the client.
Why is my site inaccessible even though the IP is correct?
This is often due to firewall restrictions or incorrect DNS propagation. Ensure that the Windows Firewall allows inbound traffic on port 80 or 443, and verify that your DNS record has propagated correctly by using
nslookup from a remote machine.
Do I need to restart IIS after changing the IP binding?
No, restarting the entire IIS service is not required. The changes take effect immediately upon saving the binding in IIS Manager. However, if you encounter persistent connectivity issues, recycling the Application Pool associated with the site can help clear stale connections.
How do I handle SSL certificates with a static IP?
SSL certificates are tied to the domain name, not the IP address directly. Once you have bound the static IP in IIS, you can attach your SSL certificate to the binding just like any other site. Ensure the certificate's Common Name (CN) matches the Host Name entered in the binding dialog.