Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 5 subscribers
  • Views 2385 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

Internal DNS Server Issues (no resolutions)

Glen O'Riley

I'm having an issue lately where internal address' are not resolving though externals are. Nothing that I can think of was changed. All hosts are in the static DNS list with corrosponding name, IP and MAC.

External resolution is working.

Short from the ridiculousness of static DNS entries on every computer I'm looking to hopefully fix this.

I've done restarts a plenty, flushed the cache etc but it just no longer resolves ANYTHING internally.



This thread was automatically locked due to age.
Parents
  • 0

    Is this happening for other computers?  If not, have you tried flushing the DNS cache on your computer? (I'm guessing you have.)

    If you restore a config backup from before this started, do you still have the same problem?

    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

    Hi Bob, yes it is happening on all computers. Happening after factory reset and fraction of a rebuild too which is odd.

    I went to install XG and that install had issues (did NOT like the product once it was installed - layout was too different and I don't like WiFi int's etc when there are none physically .... an OCD thing I guess) but now EVERY time I go to reinstall UTM9 I get a install.tar or similar file is missing. from both the original iso and the newly downloaded one (put onto usb flash trying both balena etcher and rufus). I'm starting to query hardware failure though that still doesn't quite account for why I still had internet through it just no internal name resolutions despite the static list being WELL populated.

    When I'd do a restore or restart from scratch it would work for a minute or so on 1 computer then splat again.

    I'm at a loss on it aye. It's been BRILLIANT and faithful for years now just recently it's not. No changes were made even.

    What brought the problem to light was the QNAP had a busted lead so I took LAN3 out of aggregate on the QNAP for a bit, rebuild the leads and patch panel for boxes in the rack recently and hooked all 4 in and LAN3 got a different .197 address. Once I realised something as amiss there I re-did the link aggregation so ALL 4 were as one (.001) and then noticed every computer refused to drop the .197 so started nslookup's etc and noticed they were all failing.

    I have rebuilt netstacks on a few machines, done all the flushdns' etc without change. The box resolves instantly for external but nothing internal. It's the only DNS and DHCP server internally and as I said that static mappings is WELL populated to keep the regular machines inside their own range (OCD control thing) so there should not be anything arguing.

    Fix 1 problem get 4 more it seems.

  • 0 in reply to Glen O'Riley

    Whack-a-mole - frustrating!

    What happens if you ping one of the internal FQDNs from the 'Support >> Tools' 'Ping' tab?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0 in reply to Glen O'Riley

    Whack-a-mole - frustrating!

    What happens if you ping one of the internal FQDNs from the 'Support >> Tools' 'Ping' tab?

    Cheers - Bob

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