Nginx not working after installing echoipdns?

[NomNomCameron]

I have a rails app serving assets on port 80 but the app itself is running on 3000, I'm using nginx to proxy requests from 80 to 3000

This was working until I installed echoipdns

I'm running sudo echoipdns development -f 127.0.1.1 (to have any requests that aren't local forwarded to local dns)

I uninstalled nginx and reinstalled it, visiting localhost should show the static index.html from nginx but I am not getting anything, not even a 502 status?

Any thoughts/help would be great!

[arvind-agarwal]

@NomNomCameron ideally echoipdns should not come in nginx port forwarding. Since it is only acting as a DNS server. To investigate this, Please tell me which OS you are using.

Also following are steps I would try.

1. Kill echoipdns process and see if things still work.
2. I notice you are using 127.0.1.1, are you sure that is correct address? Since typically loopback address will be 127.0.0.1
3. Is your local machine running a DNS server? On IP 127.0.1.1? Since echoipdns is meant to just forward DNS requests to existing DNS server. For Linux and Mac systems you can eliminate -f parameter since echoipdns will automatically detect the DNS server and forward requests to that. And all domains having word development in this case (since you have given domain key as development) e.g. xyz.development etc. will be forwarded to 127.0.0.1, and domains such as abc.10-0-0-1.development to respective ip address in the domain. If -f is specified it must point to IP of existing DNS server.

Post some of these findings to investigate this further.

[NomNomCameron]

OS is Ubuntu 14.04

even without echoipdns not running, a request to 127.0.0.1 will not hit nginx (nginx currently has the stock configuration as I completely removed it and reinstalled it). I should get the nginx index page but I'm not.

I was using 127.0.1.1 for Ubuntu's dns server, I didn't know echoipdns would default to using this if that argument wasn't sent to it.

[NomNomCameron]

This problem ended up being due to the prerouting rules set in iptables. I reset them and nginx started working. I should be able to set nginx to listen to port 20559 and forward to 3000 like I need while still being able to use echoipdns, so I'll try that!

[NomNomCameron]

I just noticed thought that ssh to github.com doesn't work while echoipdns is running... Any suggestions on that?

[NomNomCameron]

Other services that don't use port 80 while echoipdns is running also don't work...

[arvind-agarwal]

Please post exact error you are getting. Also try to ping to those addresses and see if they are resolved. Echoipdns is just resolving DNS so ideally it should not come in the way.

Also post exact command you used to start echoipdns.

One thing to check would be that when you ping the same domain (having problem), is it resolving to required ip or not? If you start echoipdns without a domain key than it will redirect all domains to 127.0.0.1 and you may not get desired result, so always ensure you start echoipdns with a specific key, and if that key is present in the domain name it will be redirect to either local or embedded ip in the domain name.