Tag Info

New answers tagged

0

Run a local dns server on each node, and have resolv.conf point to localhost. This would work, but it would give us a lot more services to monitor and manage. FWIW, this is the only workable solution that I have found for this problem. You do need to restrict the server to only listen on localhost, but it has completely eliminated users noticing ...


9

The direct answer to your question is Yes, it will make it worse. This is because one of your name servers not responding will cause resolve delays all the time for clients who attempt to resolve via the failed name server, whereas the current technique will only fail +- half the clients until you detect the VM is down + TTL seconds. Generally name servers ...


4

If I understand you correctly, you propose to have both distributed servers be the listed nameservers for the domain in question, each with an authoritative zonefile that contains a single A record pointing to the local server for the hostname on which your HTTPS service runs. If that's correct, then yes, I would expect this to work based on the round-robin ...


2

DNS load balancing used to be the "thing" to use, but with caching in common use today it's not as practical. In Windows, you have the "Network Load Balancer" which can assist with what you want to do by using multicast over a private network. You can still do this across providers with a VPN between the two. In Linux, you'd need to use something like ...


1

You should really be talking with your IBM partner on cases like these, as they're the best ones to answer these kind of questions. That being said - the storwize v7000 is a dual-controller system. As long as you have dual paths (you mentioned DM multipathing) to each controller then a storage processor upgrade should reboot one controller at the time, ...


1

Depends on source of your data. If data you want to sync is generated somewhere else (developers workstation, etc) and only distributed to clients via those 3 servers, I would recommend to push the data to each of three servers via rsync, or some CI tool like Jenkins, keeping the files on local disks of each server. If the data is generated and served by ...


0

You would need to use software to do storage replication. There's a couple of options available including one from SIOS Technology Group (full disclosure, I've done some presentations for SIOS). I'm not sure how Azure would handle the shared IP. If it allows you to fail a single IP over between two machines then you can do this with SQL Standard Edition. ...


0

SQL Server don't support shared data on Azure Blob Storage. However, you can rely on Database Mirroring for a high availability. It is available in SQL Server Standard and don't even require WSFC or AD to work.



Top 50 recent answers are included