Koozali.org: home of the SME Server

Obsolete Releases => SME Server 9.x => Topic started by: Drifting on October 10, 2018, 02:50:44 PM

Title: DNS and windows server.
Post by: Drifting on October 10, 2018, 02:50:44 PM

Hi, this is going to be simple I am sure to answer?
But for the life of me I cannot work out how to clear the DNS / Wins cache (Which I assume is where the issue lay)
Windows server, built a second one on the network, named it the same as the old server, however did not fix the ip. Did the usual 4 million updates, and took it off the network.
When I try and ping the server name, it comes up with the temp server IP, not the original that is now working. This is from the console of the SME server. Same from a couple of windows machines. Tried rebooting the SME that is acting as a gateway, even tried flushing the DNS cache.
Ideas?

Paul.

Title: Re: DNS and windows server.
Post by: Fumetto on October 11, 2018, 01:08:59 AM

Who is your DNS server for all LAN IP?

Title: Re: DNS and windows server.
Post by: ReetP on October 11, 2018, 10:02:38 AM

There is a way to clear the dns cache and I never remember how.

I think it is in the wiki someplace.

Title: Re: DNS and windows server.
Post by: mmccarn on October 11, 2018, 12:51:27 PM

Here's the wiki instruction for resetting the DNS cache on the SME server:
https://wiki.contribs.org/Useful_Commands#Refresh_DNS_cache

You may only need to restart 'dnscache'

Code: [Select]

sv t dnscache
Of course, this won't help if the SME server isn't where the bad entry is cached...

Title: Re: DNS and windows server.
Post by: Drifting on October 11, 2018, 03:31:52 PM

Spot on chaps, thank you so much. And yes, it was the an SME server that I use for my DHCP, DNS etc. And rock solid it has been for ages :-)

Thank you again.

Paul.

Title: Re: DNS and windows server.
Post by: Drifting on October 17, 2018, 04:50:04 PM

Actually moving on from that.

I seem to have a stuck name in Netbios! How do you flush that cache on SME? Have done it to the two windows machines I have. And my SME is the main gateway, dhcp, dns and workgroup master browser. (The only master on the network at that)

Paul.

Title: Re: DNS and windows server.
Post by: ReetP on October 17, 2018, 08:27:23 PM

I think the smeserver-dhcpd contrib will flush all the leases for you.

Check the wiki.

Title: Re: DNS and windows server.
Post by: Drifting on October 18, 2018, 02:02:08 PM

Quote from: ReetP on October 17, 2018, 08:27:23 PM

I think the smeserver-dhcpd contrib will flush all the leases for you.

Check the wiki.

Yes, I thought so too, but seems not, already use that contrib on the server (And very good it is too)
Whatever it was on the sme, it has now refreshed itself, yet nothing I seemed to do could make it get forgetful!


Paul.

Title: Re: DNS and windows server.
Post by: mmccarn on October 18, 2018, 02:16:44 PM

The NETBIOS cache is managed by nmbd.  Flush it using
  sv t nmbd

Source:
https://www.linuxtopia.org/online_books/network_administration_guides/samba_reference_guide/17_NetworkBrowsing_36.html

Title: Re: DNS and windows server.
Post by: Drifting on October 18, 2018, 03:11:21 PM

Quote from: mmccarn on October 18, 2018, 02:16:44 PM

The NETBIOS cache is managed by nmbd.  Flush it using
  sv t nmbd

Source:
https://www.linuxtopia.org/online_books/network_administration_guides/samba_reference_guide/17_NetworkBrowsing_36.html

Typical! I spent ages googling trying to find out how to restart netbios. Must have been asking the wrong questions! Thank you so much for the link and suggestion.

Paul.

Title: Re: DNS and windows server.
Post by: mmccarn on October 19, 2018, 01:02:46 PM

Quote from: Drifting on October 18, 2018, 03:11:21 PM

Typical! I spent ages googling trying to find out how to restart netbios. Must have been asking the wrong questions!

I know the feeling!

I saw your mention of 'netbios' and for some reason this thought popped into my head:
"I wonder what nmbd does.  Maybe that's the netbios piece."

I started by googling nmbd to find out what it did, rather than googling netbios to find out which service handled that...Totally random, as far as I can tell.