Re: [PLUG] Name resolution
On 04/05/2018 12:00 PM, plug-requ...@pdxlinux.org wrote: There are a bunch of Windows machines and the server hooked to a Netgear Nighthawk wireless router.? It points at nameservers out on the Internet that don't have the local names.? Create a hosts file which maps ip addr to machine name. Copy to each machine on the LAN. By default, both Linux & MS Win will check the local hosts file first for name resolution and then send out a DNS query. This default order of operations can be changed so I'd check to confirm on each machine that it's set to check the hosts file first. "Host Name Resolution Using a Hosts File One common way to resolve a host name to an IP address is to use a locally stored database file that contains IP-address-to-host-name mappings. On most UNIX systems, this file is /etc/hosts. On Windows 2000 systems, it is the Hosts file in the \%/SystemRoot/%\system32\drivers\etc directory. Following is an example of the contents of the Hosts file: |#| |# Table of IP addresses and host names| |#| |127.0.0.1 localhost| |139.41.34.1 router| |167.91.45.121 server1.central.slate.com s1| Within the Hosts file: * Multiple host names can be assigned to the same IP address. Note that the server at the IP address 167.91.45.121 can be referred to by its FQDN (server1.central.slate.com) or a nickname (s1). This allows the user at this computer to refer to this server using the nickname*s1*rather than typing the entire FQDN. * Entries can be case sensitive depending on the platform. Entries in the Hosts file for UNIX computers are case sensitive. Entries in the Hosts file for Windows 2000 and Windows NT–based computers are not case sensitive. The advantage of using a Hosts file is that it is customizable for the user. Each user can create whatever entries they want, including easy-to-remember nicknames for frequently accessed resources. However, the individual maintenance of the Hosts file does not scale well to storing large numbers of FQDN mappings." More info here => https://support.microsoft.com/en-us/help/172218/microsoft-tcp-ip-host-name-resolution-order ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Name resolution.
On 2018-04-04 15:20, michael wrote: I have a private RFC1918 network with a private DNS server on it on a CentOS 7 based server that can resolve Internet names as well. There are a bunch of Windows machines and the server hooked to a Netgear Nighthawk wireless router. It points at nameservers out on the Internet that don't have the local names. Short of getting the owner to change the Nighthawk so that it goes to the Linux server for names and the Linux server so that it will forward from Spectrum's DNS servers, how can I get host resolution to/from these Windows boxes locally? When we VPN in, it would be nice to have the local names... but getting the owner to change the configuration on the Nighthawk is asking a lot. ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug || | "ApexMW" Nighthawk Netgear Wireless Router | || | VPN access to ApexMW | || | Wired to "Projector" | || | Wired to www.int.apexmw.com| || | Wired to Spectrum cable modems | || | Wired to two more wireless routers... | || |--| | engineering1 | | | | Windows 10 | | Wireless | | ApexMW | |__| |--| | engineering2 | | | | Windows 10 | | Wireless | | ApexMW | |__| /---\ | 2 more Windows 10 computers connected wirelessly. | | Connected to ApexMW | \---/ |---| | www.int.apexmw.com| | | | CentOS 7 | | | | VirtualBox guests:| | Windows 2012 R2 | | winserver.int.apexmw.com | | Windows 2012 R2 | | winserver2.int.apexmw.com | | | | Connected ApexMW | | * wired | | | | Connected Projector | | * wired | |---| |--| | "Projector" Netgear Wireless N300 router | | Wired to www.int.apexmw.com | | Wired from Internet port to ApexMW | | Wired to controller2.int.apexmw.com | |--| || | michael.int.apexmw.com | || | Raspbian Stretch | || | Raspberry Pi 3 Model B | || | Connected Projector| | * wireless | || || | controller2.int.apexmw.com | || | Raspbian Stretch | || | Raspberry Pi 3 Model B | || | Connected Projector| |* wired | || So Raspberry Pi's running Raspbian Stretch are on "Projector," the development network. All Windows machines are connected to the Nighthawk. There is no host resolution locally for people on Windows boxes because the Nighthawk assigns a remote DNS server instead of the local DNS server. Is there a convenient way without touching the Nighthawk to resolve local names from the Windows boxes? They are getting IP addresses via dhcp from the Nighthawk. I could see about static IP and name server configuration, but that's not an ideal solution. The engineering1 computer is statically configured because it is running a service that the Raspberry Pi's running Linux need. ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Name resolution.
On 4/4/2018 1:20 PM, michael wrote: > I have a private RFC1918 network with a private DNS server on it on a > CentOS 7 based server that can resolve Internet names as well. > > There are a bunch of Windows machines and the server hooked to a Netgear > Nighthawk wireless router. It points at nameservers out on > the Internet that don't have the local names. Short of getting the > owner to change the Nighthawk so that it goes to the Linux server > for names and the Linux server so that it will forward from Spectrum's > DNS servers, how can I get host resolution to/from these Windows > boxes locally? When we VPN in, it would be nice to have the local > names... but getting the owner to change the configuration on the > Nighthawk is asking a lot. Not enough info to answer. A diagram (ASCII art is fine) of the relevant network connections and devices would be extremely helpful. ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
