dnas relay bug
 

After upgrading to latest build (256), simultaneous connect/disconnect are detected. Client connections to this server are also dropping while source relay drops.

2015-04-28 11:22:12 INFO [RELAY 127.0.0.1:8008/stream1 sid=1] Disconnected from SHOUTcast 2 source relay.
2015-04-28 11:22:12 INFO [RELAY 127.0.0.1:8008/stream1 sid=1] Trying to restore connection to source relay...
2015-04-28 11:22:12 INFO [RELAY 127.0.0.1:8008/stream1 sid=1] Connected to SHOUTcast 2 source relay.
2015-04-28 11:22:12 INFO [YP] Stream #1 has been removed from the SHOUTcast Directory.
2015-04-28 11:22:12 INFO [RELAY 127.0.0.1:8008/stream1 sid=1] Title update [Pleymo - Tank Club]
2015-04-28 11:22:12 INFO [YP] Stream #1 has been added to the SHOUTcast Directory.

2015-04-28 11:22:17 INFO [RELAY 127.0.0.1:8008/stream2 sid=2] Disconnected from SHOUTcast 2 source relay.
2015-04-28 11:22:17 INFO [RELAY 127.0.0.1:8008/stream2 sid=2] Trying to restore connection to source relay...
2015-04-28 11:22:17 INFO [RELAY 127.0.0.1:8008/stream2 sid=2] Connected to SHOUTcast 2 source relay.
2015-04-28 11:22:17 INFO [RELAY 127.0.0.1:8008/stream2 sid=2] Title update

Issue was resolved by installing older version of DNAS (2.4.2)
Relay & server are located on the same server and using the same binary files\SHOUTcast folder.

its most likely due to http://forums.winamp.com/showthread.php?p=2970776#known and issue #3 (which in a relaying setup as you're doing cannot be worked around without a newer DNAS build, so going back is the only solution in your case).

ok, i'll wait for a new release.
where can i download a previous release of v2.4.7 ?
DNAS v2.4.2 seems to be too old ...

there isn't an older 2.4.7 build available and you going back to 2.4.2 is the only option (as you've done).

Ok, thank you DrO, got it.

FYI, this bug is reproduced only on Windows version of SHOUTcast server.
SHOUTcast Server v2.4.7.256/posix(linux x64) have no such problem.

that is not true and it's reproducible on all OS versions (with most reported cases from linux builds) and is subject to the specific setup and timing of data flowing through all parts of the stream (as covered by that known issue item).