# Custom MPD redirect

**URL:** https://community.wowza.com/t/custom-mpd-redirect/153
**Category:** Wowza Streaming Engine
**Created:** [August 14, 2015, 8:59am UTC](https://community.wowza.com/t/custom-mpd-redirect/153 "2015-08-14T08:59:04Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/system/32/447_2.png) [@system](https://community.wowza.com/u/system)
#### Post date: [August 14, 2015, 8:59am UTC](https://community.wowza.com/t/custom-mpd-redirect/153/1 "2015-08-14T08:59:04Z")

</div>

Already posted as comment on the MPEG-DASH page. No feedback so trying here:

Is it possible, or can it be made possible, to force the Wowza IP address (instead of domain) in the mpd manifest Location?

Our problem:

Clients are directed to the liverepeater-edge server pool through DNS round robin. The client’s live stream freezes, when a browser tries to access a different edge after a DNS refresh.

Player sends initial request to server A [streampool.com/mystream](http://streampool.com/mystream) and receives a mpd with Location [streampool.com/mystream\_with\_session](http://streampool.com/mystream_with_session)

Minutes later the browser resolves DNS for [streampool.com](http://streampool.com) again, and lands on a different server, where the session does not exist, and stream stops

I guess this would be solved if the mpd Location response contained an IP address instead of domain.

---

<div class="post-metadata">

### Author: ![Roger\_Littin1](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Roger\_Littin1](https://community.wowza.com/u/Roger_Littin1)
#### Post date: [September 9, 2015, 11:33am UTC](https://community.wowza.com/t/custom-mpd-redirect/153/2 "2015-09-09T11:33:45Z")

</div>

Hi,

You can set the domain name (or ip address) to use in the Location header by setting the following property

Path: /Root/Application/HTTPStreamer/Properties

Name: mpegdashPlaylistHostDomain

Value: 1.2.3.4

Type: String

This should fix the location header however, it may also need a BaseURL tag that isn’t currently supported. Our engineers are aware of the issue and are looking into it.

Roger.
