Hi Nginx forums team,
I’m with a issue related a removed configuration file for a specific
hostname. So, I need to associate the hostname with a new ip address
from
other vm, but it’s not possible because, this hostname always are
resolved
by nginx. I am using ubuntu server lucid 64; I removed the
sites-available
and sites-enabled config files for this virtual host, as well as
reloaded
the nginx service. Anybody knows, if I’m forgetting anything, or if this
is
a common issue?
On Sat, Oct 11, 2014 at 06:23:28PM -0400, jbjares wrote:
Hi there,
I’m with a issue related a removed configuration file for a specific
hostname. So, I need to associate the hostname with a new ip address from
other vm, but it’s not possible because, this hostname always are resolved
by nginx.
Do you mean “browser still talks to nginx on old-vm but I want it to
talk to something on new-vm”, or “nginx still talks to something on
old-vm but I want it to talk to something on new-vm”, or something else?