Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 3 subscribers
  • Views 3292 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

Cache for DNS-Host definition

redhorse2017
Good morning,

I've got a problem with a DNS-Host definition:

For example, Host A has the hostname hosta.local with ip-adress 192.168.0.1 which is assigned by a windows dhcp server. Now, ASG doesn't recognize the change of the ip-adress to 192.168.0.2, the packet filter rule doesn't match, because hosta.local has still 192.168.0.1 in its definition on ASG.

Is it possible to update the dns-cache for the dns host definition in scheduler or something like that?

Kind regards
Christian


This thread was automatically locked due to age.
  • 0
    If I understand your question correctly, you should assign a fixed IP to Host A instead of letting it use DHCP.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    Yes, fixed IP or static assigned DHCP address.

    Anyone knows how long a "DNS Host" lookups are cached until it is renewed by the ASG?
  • 0 in reply to UrsWeiss
    Anyone knows how long a "DNS Host" lookups are cached until it is renewed by the ASG?


    iirc, 2 hours. but that may have changed.

    Barry
  • 0

    EDIT:

    shame on me ... deployed host with sum with static old ip :-(

    everything works now... redirected the requests going to the old ip to the new ip and now deployed the correct ip

     

    what a shame ... sorry @all

     

     

    Hi all,

     

    I encountered this problem, too

     

    i've set up dns-host definitions for our sum server on each customer utm.

    like so:

    now i've changed the dns for sum.company.com from A.A.A.A to B.B.B.B at the dns hoster...

    All (there are a lot) customer UTM didn't recognize the change in the public dns and they all do have the old A.A.A.A IP in their cache.

    I think this is some kind of bug...

     

    ... do you have an idea what i can do to make my customer umts update their dns cache ? 

     

    Cheers,

     

    Chris

  • 0 in reply to ChrisBKA

    Hallo Chris,

    You can do this at the command line with:

    cc dns_flush_cache

    Or, in WebAdmin, at the bottom of the 'Global' tab in 'DNS'.

    Depending on the TTL in the authoritative name server, it still may take awhile for their internal devices to refresh.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Unfiltered HTML