Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
6
Newest
 Commentator
Impact
~3k people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
Jan
28
comment DNS forwarding for external addresses on same domain as Windows Server 2012
Thanks for confirming that. I'll go down the route of having the internal DNS managing int.example.com in that case.
Jan
28
accepted DNS forwarding for external addresses on same domain as Windows Server 2012
Jan
28
comment DNS forwarding for external addresses on same domain as Windows Server 2012
Thanks for confirming the problem. If I were to add the records to the internal DNS for the external domains, wouldn't that mean I'd have to maintain records on both the internal and external DNS servers? This isn't a huge problem but it would be nice to only have to maintain unique records for the external addresses. I could use a different TLD for the internal domain but I'd like the experience to be as transparent as possible for the users inside the network (e.g. they can access www.example.com but then can access intranet.example.com which is resolved using the internal DNS).
Jan
28
asked DNS forwarding for external addresses on same domain as Windows Server 2012
Apr
8
comment Server not responding from outside the LAN
I'd made the changes to /etc/network/interfaces and run sudo ifdown eth0 && sudo ifup eth0. This seemed to work at the time but the breakage after the reboot would indicate it didn't.
Apr
8
accepted Server not responding from outside the LAN
Apr
8
revised Server not responding from outside the LAN
added 123 characters in body
Apr
8
comment Server not responding from outside the LAN
You star! I had completely forgotten that gateway had been changed a while ago. The networking had been restarted to use the new gateway and seemed to be working just fine but the reboot must have had an effect somehow. Changing the gateway back has fixed the problem. If you could make your comment into an answer, I'll mark it as such. Thanks for the help!
Apr
8
comment Server not responding from outside the LAN
It would appear that they did in fact enable NAT for the source address as all incoming requests now appear to originate from the firewall's IP. I can see that was definitely NOT an issue before as the logged requests had external IPs. I've just checked the logs and the machine was shutdown to move it to another rack around the same time it stopped working. I'm guessing something changed some time ago on the server that required a reboot to take effect. Any ideas what configuration/changes could cause the server to reject packets that aren't source NAT-ed by the router?
Apr
7
answered Server not responding from outside the LAN
Apr
6
comment Server not responding from outside the LAN
Nothing in the logs as the connection doesn't seem to get established to the server.
Apr
6
awarded  Commentator
Apr
6
comment Server not responding from outside the LAN
ufw is already disabled and the Apache conf has not changed in the last few weeks at all. If it was the apache config, wouldn't it also not work from the local network?
Apr
6
comment Server not responding from outside the LAN
I've run sudo ufw reset but I still haven't enabled it so this shouldn't make a difference right? Ah just realised you may have been talking about the corporate firewall so yes, those routes are the same as they were before.
Apr
6
comment Server not responding from outside the LAN
Completely disabled. Even tried removing it completely but it hasn't made a difference. $ sudo ufw status Status: inactive
Apr
6
asked Server not responding from outside the LAN
Mar
1
comment Can't get logstash to work with upstart script
Thank you! The issue was down to the apache log not being readable. Can't believe I've been stuck for so long with something so obvious!
Mar
1
accepted Can't get logstash to work with upstart script
Feb
28
comment Can't get logstash to work with upstart script
You were absolutely right! I was running the test as root and the service as logstash user. It definitely looks like a user issue but I still can't figure it out. The debug logs from the test run as root which works are here (pastebin.com/pzc634Xt) and the logs from the service (run as logstash which doesn't work are here: pastebin.com/CKp7Lwpq). Can you offer any more advice?
Feb
27
comment Can't get logstash to work with upstart script
The log output from `/var/log/logstash/logstash.conf is here: pastebin.com/AcdiUSM6. The config file works fine as I am able to run it from the command line, just not when run as a service.