Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 1 subscriber
  • Views 8564 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 Problem. Wrong DNS servers

nathy84
Hi

I'm using the newest Sophos SSL VPN client.
We have the following problem.

We are not able to resolve the internal ressources after connecting with the VPN client.
- We can resolve the external ressources.
- With a nslookup I get the correct server and I can resolve the internal servers.
- With a Ping command I'm not able to resolve the severs. Also not with the FQDN.
- A ipconfig/registerdns and a ipconfig/flushdns will solve the problem

How can I solve this problem globaly for all clients.

Best regards


This thread was automatically locked due to age.
Parents
  • 0
    Hi, Fabian, and thanks for tracking that down.

    I think that if the registerdns command works, then the flushdns shouldn't be needed.

    On the contrary, if the DNS problem is after disconnecting the VPN client, then only the flushdns should be needed.  If anyone gets a chance to test this hypothesis, I would appreciate some feedback.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Hi, Fabian, and thanks for tracking that down.

    I think that if the registerdns command works, then the flushdns shouldn't be needed.

    On the contrary, if the DNS problem is after disconnecting the VPN client, then only the flushdns should be needed.  If anyone gets a chance to test this hypothesis, I would appreciate some feedback.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    Hi Bob

    I found out the reason for this DNS issue in our network:
    We had IPv6 disabled. Sounds strange, but we had a GPO for this. After I excluded my test laptop from this GPO, I didn't have to enter an "ipconfig /renew" or "/registerdns" anymore.
    Our Sophos partner found that solution. He actually saw this in other networks before.
Unfiltered HTML