Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,514 questions
Windows Server DNS issue with Windows Client 10 Client machine
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 43%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP1%3C/text%3E%3C/svg%3E)
PerserPolis-1732
1,516
Reputation points
Hi,
I have a issue with my Windows Client 10 machines (Notebooks). As you know Notebooks has as well LAN and as WLAN. If the user connected to the LAN, getting here a IP from for example 192.168.178.1 and the WLAN getting a different IP from DHCP for example 10.100.1.1. Either the LAN IP or WLAN IP are in recorded DNS server dependent on which network you are connected.
Sometime I cannot reach the machine either with ping or remote desktop or something else. I put in DNS Server the TTL value to "0", but sometime helps and sometimes not.
The only way is, I run the command line "ipconfig /registerdns" on the Client machine and on the DNS Server delete the Windows client record and run the "ipconfig /flushdns" , then I can reach the machine. I have to mention only if can access to the Client machine, I can run the above command line.
The best way is in that situation to run a logon script with power shell or batch with command "ipconfig /registerdns" and "ipconfig /flushdns". But how?
I have really no idea how I can resolve that issue. Any Idea?
Regards
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
Rich Matheisen 45,596 Reputation points2024-07-01T15:01:52.0033333+00:00 Are the two adapters configured to register the connection with DNS?
The easiest way might be to use a different sub-domain on each network (e.g. company.com, and wireless.company.com). The two adapters would be configured with the associated subdomain, and set to register the connection in DNS (I'm guessing they already are). Create the associated DNS zone. Then clean up the DNS zone with the multiple "A" records for the same machines.
There is also the use of different DNS servers on each network.
It sounds like you've got a network design problem that has nothing to do with the "Windows Server PowerShell" tag on your question.
-
PerserPolis-1732 1,516 Reputation points
2024-07-01T15:21:55.81+00:00 Are the two adapters configured to register the connection with DNS?
As I know, yes. Is there other way for WLAN?
How can I easy do that with sub-domain?
with TTL set to "0" does work, but it needed sometimes a registerdns.
do you have other solution?
-
Rich Matheisen 45,596 Reputation points
2024-07-01T18:24:52.71+00:00 Why aren't the DHCP servers managing the DNS data for the addresses they issue? Why delegate that activity to the client machines?
Setting up the subdomain in DNS is straightforward. How you configure the clients is something you'll have to determine. Probably the easiest way is to have the DHCP servers provision the clients. That may involve undoing whatever you've already done with the client machines that led to the problem in the first place.
One other question: why would you NOT be able to ping a machine on the LAN from a machine on the WLAN (and vice versa)? Are your routers not configured properly?
I've run into problems with networks where you can ping "B" (on network "Y") from "A" on network "X" and the answer from "B" comes back over network "Y". That non-symmetric routing can cause problems.
One more thing: The TTL on a DNS record only informs the entity that asks for the information that it shouldn't cache the information. It has nothing to do with way the DNS resource record is managed. Using TTL in that way places a great deal of trust on the inquiring entity to actually discard the information.
-
PerserPolis-1732 1,516 Reputation points
2024-07-02T05:36:47.2933333+00:00 We have a DHCP Server with 4 Network scops.
Why aren't the DHCP servers managing the DNS data for the addresses they issue? Why delegate that activity to the client machines?
How?
One other question: why would you NOT be able to ping a machine on the LAN from a machine on the WLAN (and vice versa)? Are your routers not configured properly?
As you know the Notebook has as well LAN and as WLAN, if the both LAN and WLAN is on, they are getting two different IP address. And on the DNS Server is one of these IP address recorded. As I mention, if you ping the machine with machine name, you cannot get any answer or cannot reach the machine. Only if you know the IP-Address what actually has the Notebook connected.
If I delete on the DNS Server the entry of the Notebook and if I run a registerdns or flushdns on the client machine, then I can ping the machine with machine name
Sign in to comment