Hostnames don't resolve without local domain
-
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
-
Thank you very much.
-
Finally I found some useful information.
-
To be honest I didn't understood anything that you wrote there, but I need a little bit of help.
-
Perhaps I'm missing something, but it might help if you mentioned what your problem is.
-
can almost promise you those are spammers @JKnott
But until they actually spam something, not really right to delete and ban..
-
Yup. Spam incoming....
-
@johnpoz I am not a spammer but thank you that you take care of it.
-
@JKnott Thank you my friend, I found someone that already fixed everything. Appreciate that!
-
What was your problem, if you're not a spammer?
What was the solution?
-
@johnpoz Ha, that took a while.