Forum Home
Press F1
Thread ID: 125697	2012-07-13 11:07:00	DNS issues on Domain behind IP Cop	berryb (99)	Press F1

Post ID	Timestamp	Content	User
1288270	2012-07-13 11:07:00	Have a DNS issue that I can’t work out. 2 domain controllers, DNS working fine between them, no issues internal and basically no issues externally. Are using IP Cop for a firewall/filtering. Domain name is same as public – domain.co.nz Can’t get to www.adobe.com and a couple of other sites but all others work. Get Connection to 192.150.16.64 failed. The system returned: (113) No route to host This error is from IP Cop. Server DNS logs no errors and has forwards setup to Xtra DNS and Google and these all resolve. IP Cop has DNS set to Google and Xtra. Just upgraded IP Cop from ver 1.4 to 2.0.4 but same issue in 1.4 Firewall is locked down, have port 53 allowed out, log shows connection to xtra and Google DNS from the servers. I don’t have port 53 open in port forwarding and shouldn’t need to or want to. Seems IP Cop doesn’t like the 192.0.0.0 range. Have another site with SBS 2003 behind the same version IP Cop with same DNS settings and Adobe site loads fine. Ideas??	berryb (99)
1288271	2012-07-13 12:38:00	Bad mask on a 192.x.x.x internal or DMZ range in the IPCop config? It appears to be a routing prob, not DNS, as it resolves ok.	fred_fish (15241)
1288272	2012-07-14 11:56:00	So I take it you can't ping the site from the internal network or the firewall? Can you do a 'tracert -d adobe.com' and post the results. What are some of the other sites that don't work?	WarNox (8772)
1288273	2012-07-18 07:34:00	Thanks for the post and it made go and see if I can ping direct from the modem and it doesn't so in the process of changing the modem. Will report back. Cheers	berryb (99)
1288274	2012-07-24 02:59:00	Turned out to be an issue with the modem. It was set to 192.168.1.254 and it didn't route to anything external in the 192.0.0.0 range. Changed the modem and all fine. Cheers	berryb (99)
1