Jump to content
RESET Forums (homeservershow.com)
MattG

Server is forcing it's IP into clients as DNS server

Recommended Posts

MattG

It suddenly came to me why my computer acts wonky when I've got the server running.  I checked the IPv4 properties and the server IP address was selected as the preferred DNS server.  I don't want that.  I tried resetting it to obtain DNS server address automatically but after rebooting it was reset again to the server IP.

Must I force the address to my router?  Or, preferably, is there a setting in the server to keep it from resetting the client computers?

edit: Clients are all Windows 7 computers (pro and home)

Thanks,

-Matt

Edited by MattG

Share this post


Link to post
Share on other sites
Drashna Jaelre

This is entirely normal, and ... if you were joined to the domain and it was configured properly, then this wouldn't even be an issue.  But for most people..... 

If you're okay with this, then make sure you configure the "DNS" role on the server so that the "DNS Forwarders" are configured to a proper (and working) DNS server.  

Otherwise, do this: https://tinkertry.com/how-to-make-windows-server-2012-r2-essentials-client-connector-install-behave-just-like-windows-home-server

Specifically, the "SkipAutoDNSServerDetection" option. This will stop it from updating the DNS server on the client. 

  • Like 2

Share this post


Link to post
Share on other sites
MattG

Well, as you may have assumed (correctly, I might add) I am not most people, lol. :)

This is a replacement for my old WHS v1 server that I adored and worked perfectly. :(

Would using the server as the DNS server be a way to block certain websites?  Would I be able to do that on a client-by-client basis, or would it be a global function, so to speak?  Basically, can I use it to filter out websites per user?

Oooh, nice link.  Thanks for that!

 

-Matt

Share this post


Link to post
Share on other sites
Drashna Jaelre

:)

Block certain websites? Yes, by adding invalid entries for those domains. But this is a lot of work and time consuming. But you *could* point the server to OpenDNS and let them handle that work. :)

Would you be able to do it on a client by client basis?  No idea.  I think so, but I have no idea how to do so (I've never tried).

  • Like 1

Share this post


Link to post
Share on other sites
MattG

Should I call you Drashna or Christopher?  

I wanted to thank you again for the link you posted about getting the server to act more like WHS.  It worked like a champ on this new Win10 Pro laptop.  I honestly can't thank you enough.  :)

Share this post


Link to post
Share on other sites
Drashna Jaelre

Either is fine.  I prefer "drashna" when not working. 

 

And you're very welcome! 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • Umfriend
      By Umfriend
      Hi all, new here and WSE noob.
      So I have a server running WHS2011 and I want to go WSE2016 (or WSE2019 if it will still offer client backups, web access etc.). So I installed a evaluation and am testing with old unused computers. Now I know that there are two things some talk about when using WSE in a SOHO setting: not joining the domain and not having WSE as the DNS server.
       
      Now my question is basically this: I connected a client with defaults (so no hacks) and now I am wondering "why bother"? I don't understand what the reasoning is behind not joining the domain for instance. As far as I can tell, the user sees no difference between connecting to WSE2016 or WHS2011. But people are talking about it so there must be a catch I don't get.
       
      Edit: My clients would be both fixed PCs as laptops which would have to be able to work on other networks (but not connected to other servers or anything).


×
×
  • Create New...