New answers tagged spoofing
You could set up a DNS server set up in a configuration called "split DNS". Some domains would have their lookups directed at the new server and all others would follow the regular path. http://en.wikipedia.org/wiki/Split-horizon_DNS If you are using BIND, this might help: http://www.cyberciti.biz/faq/linux-unix-bind9-named-configure-views/
First, good thinking to test before the transition. You'd be surprised at how many sysadmins don't test. Using @newserver ignores the NS records and sends the request directly to newserver. You can test that it serves the right NS records by specifying "NS" on the command line: dig @newserver mydomain.com ns That verifies that you have the right NS ...
Essentially, you're trying to work around what appears to be somebody else's bad implementation. That seems reasonable to me, and sometimes, that's a necessity. If this program is indeed "crashing" when trying to connect to one database but not another, as opposed to, oh, you know, displaying an error message, that's pretty weak. I have a standby solution ...
While you certainly could use techniques like SSH port forwarding to make a remote listening TCP socket appear like a local one, it probably would not be of any help. If your client is "crashing" upon connection, it most likely would not stop doing so just because you are using a different destination IP address. There might be a myriad of reasons why the ...
Top 50 recent answers are included