URL Rewrite (IIS 10) - Redirection between URLs on the same network

Question

URL Rewrite (IIS 10) - Redirection between URLs on the same network

FelipeSantosBRA 61

Hi,

I need help creating the following redirect in IIS 10 (Win Server 2019 DTC):

"name.domain.com" to "http://192.168.0.1/service"

In the DNS Server (integrated with AD), I have already created the A record that resolves "nome.domain.com" to the WEB Server's IP. I have also created a rule in URL Rewrite (default site level) that should perform the redirection informed. However, when carrying out the test in any browser, only the IIS 10 home page is loaded, that is, the redirection does not work.

The IIS server was only created for this purpose. And all hosts are on the same single-domain network and on a single VLAN (the default).

Below is the rule created in URL Rewrite (standard site level):

Name: Service Redirection

Match URL:

Requested URL: Matches the Pattern
Using: Wildcard
Pattern: name.domain.com
Ignore case: checked

Conditions:

Logical grouping: Match All
```
  (no condition added)
```

Server Variables:

     (not configured)

Action:

Action type: Redirect.
Redirect URL: http://192.168.0.1/service.
Append query string: checked
Redirect type: Permanent (301)

Are there any errors in this rule?

Thanks.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2024-01-31T18:37:00.9466667+00:00
After configuring DNS, your users should access the service via "http://name.domain.com/service". Isn't that enough?

I don't think you need this redirection rule (and the rule itself also contains a common mistake, https://halfblood.pro/the-very-common-mistakes-when-using-iis-url-rewrite-module-a2ab7e4fee59

Accepted answer

3 additional answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2024-01-31T18:37:00.9466667+00:00

After configuring DNS, your users should access the service via "http://name.domain.com/service". Isn't that enough?

I don't think you need this redirection rule (and the rule itself also contains a common mistake, https://halfblood.pro/the-very-common-mistakes-when-using-iis-url-rewrite-module-a2ab7e4fee59

Answer 1

Sam Wu-MSFT 7,561 Microsoft External Staff

@FelipeSantosBRA Do you have access to name.domain.com? If you can, you can try the following rule:

<rule name="test" stopProcessing="true">    
  <match url="(.*)" />      
    <conditions>          
      <add input="{HTTP_HOST}" pattern="name.domain.com" />      
    </conditions>    
  <action type="Redirect" url="http://IP address/service" redirectType="Permanent" /> 
</rule>

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2024-02-01T03:48:46.17+00:00

Deleted.
FelipeSantosBRA 61 Reputation points

2024-02-23T17:23:43.51+00:00

Thanks for your help. It is now working correctly. I created a second redirect, pointing to another server, but the page didn't load. Do I need to change the configuration?

FelipeSantosBRA 61

Hi,

I can find the solution:

<rule name="test" stopProcessing="true">
    <match url="^(.*)$" />
	    <conditions>
		    <add input="{HTTP_HOST}" pattern="^name.domain.com$" />
	    </conditions>
    <action type="Redirect" url="http://IP address/service" redirectType="Permanent" />
</rule>

Answer 2

FelipeSantosBRA 61

I'll run a test and get back to you soon.

Answer 3

FelipeSantosBRA 61

Hi. Unfortunately, it didn't work. Please see the prints for verification: https://1drv.ms/u/s!Ano4lKaa9hT7ha8nir3s-A5FzfW85A?e=xdhZX9. Where is the error?

Sam Wu-MSFT 7,561 Reputation points Microsoft External Staff

2024-02-02T09:59:58.9+00:00

@FelipeSantosBRA The ip address in your file is different from 192.168.0.1, and http://172.22.0.143/service can work, so please post more details information about your requirement.
FelipeSantosBRA 61 Reputation points

2024-02-02T18:00:28.89+00:00

Sorry about the mess. The 192.168.0.0 network was just an example. The attachments I sent are from the company where I work, whose network is 172.22.0.0. I just wanted to show that the redirect is not working.
Sam Wu-MSFT 7,561 Reputation points Microsoft External Staff

2024-02-06T10:03:33.39+00:00

@FelipeSantosBRA You can use failed request tracking to view detailed error information.
FelipeSantosBRA 61 Reputation points

2024-02-06T18:28:02.9433333+00:00

Ok I'll check.
FelipeSantosBRA 61 Reputation points

2024-02-23T17:25:34.72+00:00

Thanks for your help. It is now working correctly. I created a second redirect, pointing to another server, but the page didn't load. Do I need to change the configuration?

FelipeSantosBRA 61

Hi @Sam Wu-MSFT ,

I can find the solution:

<rule name="test" stopProcessing="true">
    <match url="^(.*)$" />
	    <conditions>
		    <add input="{HTTP_HOST}" pattern="^name.domain.com$" />
	    </conditions>
    <action type="Redirect" url="http://IP address/service" redirectType="Permanent" />
</rule>

Answer 4

FelipeSantosBRA 61

Thank you all.

Share via

URL Rewrite (IIS 10) - Redirection between URLs on the same network

3 additional answers

Your answer