I am unclear on how Untangle handles DNS.
Ideally, I would use it as a caching server to the world as well, instead of using it only for internal.
Here is my scenario:
I use Xplornet connection with 5 static IP addresses. 1 is dedicated to Untangle. (1 is UT for work network - others servers are separate directly connected to Xplornet no UT).
I use Xplornet DNS on all 5 machines.
I do not run BIND or NAMED on any of the machines.
I use Zoneedit for DNS A records and MX records.
UT has two network cards. 1 to Internet, configured on a static IP with both Xplornet DNS entries in place. I note that the external IPs are on a /24 subnet, though odd range).
Internal is 192.168.8.x with UT @ 192.168.8.254/24
I updated DNS for a new domain name called whatever.com on zoneedit. Everything can take up to 72 hours to propagate.
72 hours later ....
I can open a browser, ping, dig and see the whatever.com and all the pertinent info or pages.... all is good.
This is done from my iphone (on Rogers network), a CENTOS server (on its own static IP using same DNS entries as UT - from Xplornet), A bell network (Windows box in an office elsewhere).
Any of the machines on the 192.168.8.x network (With UT as a router at the front) are not able to resolve on anything tried (web browser, dig etc).
Same front end Xplornet DNS entries.....
UT does hand DNS internally, no there are no odd static entries in there, but if I enter them statically for whatever.com it will find it. Ok clear static entries reboot to be sure.
Added packet filter to allow all UDP on 53
Added firewall rule to allow all on 53.
Have not yet tried turning off all the services (OpenSource Package).
Anyone have any ideas? Could it be dirty dns cache?
Thoughts and comments are appreciated.