This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Getting "Host not found" in WiFi-Network, but working in LAN

Hi,

I have a UTM 220 running here. We have to subnets, WiFi and LAN.

When I try to access a webserver over LAN using its internal FQDN (http://example.somedomain.net), the connection is established.

When I try to access the same server over WiFi (different subnet) using the internal FQDN, I'm getting "Host Not Found"

[PHP]2014:01:17-11:40:32 fw-1 httpproxy[21845]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked" action="block" method="GET" srcip="192.168.20.125" dstip="" user="" statuscode="502" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="2507" request="0xceeb0a0" url="example.somedomain.net/.../PHP]

When I try to access the same server over WiFi using the IP (192.168.10.31), the connection is established again.

What's wrong here?

Best regards,
Ben

This thread was automatically locked due to age.

0 apijnappels over 11 years ago

I guess your name resolution (DNS-settings). Probably your wifi subnet had different DNS-server settings.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ben0583 over 11 years ago

No, that's not the problem. DNS-server ip is assigned via DHCP, the same dns is used on all subnets and reachable from all subnets.
Cancel
Vote Up 0 Vote Down

Cancel
0 apijnappels over 11 years ago

is the wifi subnet also allowed to use the DNS server? You could try nslookup - ip-address to see if you're allowed to use it.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ben0583 over 11 years ago in reply to apijnappels

Yes, the WiFi subnet has access to the dns-server, and the ip can be resolved.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 11 years ago

It's gotta be DNS. Try creating a Network Host definition linking the FQDN to the internal IP. Also, you might want to compare what you have to DNS Best Practice.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 JonEtkins over 11 years ago

Can you ping the web server by name from one of the failing client machines?
Cancel
Vote Up 0 Vote Down

Cancel
0 JonEtkins over 11 years ago
You might also try looking more closely at what your DNS server is telling the clients. On a windows client, try the following:
C:\>nslookup
> set debug
> [server_fqdn]
> exit
Cancel
Vote Up 0 Vote Down

Cancel
0 Ben0583 over 11 years ago in reply to JonEtkins

Ok, it's working now. DNS request routing was not configured.

Thanks a lot!

Ben
Cancel
Vote Up 0 Vote Down

Cancel