Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 604 views
  • Users 0 members are here
Options
Suggested
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

DNS Proxy fails after Up2Date to 5.2??

martindw
I have an ASL box configured to do DNS proxy (among its other many talents), which has been working seamlessly until Up2Date 5.2.  Then I found that all web and email requests were failing for inability to look up  addresses.  I put a second DNS into the DHCP (to make the machines go to another internal DNS on a different VPN subnet if they couldn't get the ASL) and everything came up swimmingly.

Anyone else seeing DNS croak after Up2Date?

Dan


This thread was automatically locked due to age.
  • 0
    Yep had the same problem user ASL as master DNS server for DHCP clients,. On update to 5.2 name resolution stopped working, Work arround was to point ASL to resolve name instaed of Root servers to ISP DNS servers. DHCP clients used ASL for Primary DNS with external as secondary. Has been working well for a while.

    Matt
  • 0 in reply to Matt_01
    Yeah, that's exactly what I did.  My suspicion, though I can't prove it w/o sniffing the network which I haven't gotten around to doing, is that DNS queries are failing on ASL (the primary) and so everyone is querying the secondary (ISP) DNS and therefore everything "works" although, in point of fact, ASL DNS proxy is NOT working. . .

    Dan