For more than a year now, I have been using ZS as a firewall / router to provide internet access to our firm’s guests while keeping them off of our internal network. One side of ZS sits on our internal network and the other sits on our “guest” network. Like this
Internal network – Zeroshell – guest network
We occasionally have DNS issues on our internal network. For example, I am sometimes unable to reach internal servers by their name and must use an IP address instead. We have a single DNS server set up on our internal network. While scanning the network for possible “rogue” dns servers, I noticed that DNS services on the internal network side of the ZS box are visible. That is, I can “see” the DNS server running on the ZS interface that faces our internal network. Could this be the issue? I understand that client queries are “directed” specifically to the DNS server(s) for which the client is configured. Our internal client machines all get their DNS server settings from DHCP so I know they are all querying the proper internal server and not the ZS box. So…
1) Should I be able to see the ZS DNS server on our internal network?
2) Could the ZS DNS server facing our internal network be somehow interfering with our internal DNS server?
3) If the server’s visibility on our internal network is in fact the issue, how can I resolve this?
Thanks so much for any insight, direction, assistance you can possibly provide.
I’d probably use dig or nslookup on the affected hosts to figure out which dns they’re using and if the service is accessible and also resolving.
Not enough information in your post about firewalls, routing, and dns zones to give you much more info.
It could be that the dhcp for the Internal network is giving the zero shell’s dns server as a potential name resolver.
Have you thought about slaving your internal dns zones to the zeroshell DNS server?