Hostnames don't resolve without local domain
emammadov last edited by emammadov
If user computer gets ip address via dhcp, then it can resolve hostname of other computer or server (for example: fileserver). But if user manually adds ip address into his computer, then he can't resolve the server hostname, he has to add .localdomain (fileserver.localdomain) to resolve.
We are using DNS Resolver. DNS Query Forwarding, DHCP Registration and Static DHCP are enabled in DNS Resolver. What should I do to solve it?
That's how it's supposed to work. Either query by the full host name or be in the same domain so it uses that by default if you don't specify one.
marvosa last edited by marvosa
It works on your DHCP clients because the dhcp server is providing a DNS suffix to your clients. For statically configured clients, if you don't have a domain to join, then you will need to add the DNS suffix manually on each client:
Otherwise, you will have to do lookups via FQDN.
So outside of implementing AD or an AD equivalent, you basically have 4 options to achieve your objective (only two of which are reasonable IMO):
- Manually add a DNS suffix to each statically assigned client
- Change all static clients to DHCP and use DHCP static mappings instead of configuring static IP's.
- If you have access to MS Server, you could deploy a WINS server, add the WINS server to your DHCP scope and configure the WINS server on all your static clients. However, you would be reverting back to a deprecated protocol developed in the 80's and relying on NetBIOS instead of DNS. I don't really consider this an effective option, but since it would technically work, I just threw it out there. ;)
- Manually edit the etc\hosts file on each device. Which in this day and age is just as absurd as running a WINS server... LoL
emammadov last edited by
Thank you very much.