![]() ![]() ![]() But, the workstation couldn't resolve any sites. When we ran an Ipconfig /all command from a workstation on the LAN, everything DNS related matched what we had setup in DHCP. All pretty straightforward and normal, from my perspective. Under System - DNS - Domain Zone Forwarder, we have the same two Comcast DNS servers listed as Public DNS servers, queried via WAN1. The Flex 200's DHCP settings listed the Zyxel as the first DNS server, and then Comcast's DNS servers as the second and third. Yet, user's claimed that they still couldn't connect to the Web, so we started looking at DNS settings. When we went to check their connectivity, we saw that the firewall was reachable remotely, so we jumped on and noted that broadband connectivity to the firewall was fine. The customer reported that their broadband was down and sent most staff home since no one could work. We've had relatively few issues, but today we ran into something weird. The customer has no on-site server, so the USG Flex 200 serves DNS and DHCP. We support a small office that's using a USG Flex 200 in front of a Comcast Business modem (Comast is ISP). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |