Originally Posted by thewoose
What I would like to do is have both of them show up in the YP as one server instead of two, and do an automatic failover should the main server become overloaded.
as long as the servers have been clustered together correctly, then at least with a v1 DNAS it should be sending clients to the 'backup' which the YP provides back to the DNAS.
with the v2 DNAS it's a bit funky with the current public build for doing that but has been resolved in the internal builds.
in either case, as long as the clustering is done correctly, then the YP will put the server with the most free slots first in the list and will change what is provided as time goes on. if someone connects directly then (barring any bugs) should redirect that if the DNAS has a known backup.
the only issue to that is it means both will be used at the same time - it sounds a bit like you only want the main being used unless there is an issue. if that is the case then what i've described probably isn't going to fit your needs and you might then need to do funky stuff like proxy handling to control who gets sent to what DNAS, etc.