jimmy1829
asked on
Domain joined server does not register with DNS
Hi Expert,
I am experiencing this frustrated issue which I could not figure out.
We recently had a few servers on 192.168.20.0/24 subnet joined the domain on 192.168.250.8/24 subnet.
I did not have problem join them to the domain expect receiving "Changing primary DNS name to .... failed. The name will remain...... The error is the specified domain either does not exist or could not be contacted.
Once these server were on the domain, they were not able to register themselves on the DNS server.
I have tried ipconfig/registerdns with no luck. Wireshark live monitor seems to stuck at dynamic update with domain controller.
Please advise.
Jimmy
I am experiencing this frustrated issue which I could not figure out.
We recently had a few servers on 192.168.20.0/24 subnet joined the domain on 192.168.250.8/24 subnet.
I did not have problem join them to the domain expect receiving "Changing primary DNS name to .... failed. The name will remain...... The error is the specified domain either does not exist or could not be contacted.
Once these server were on the domain, they were not able to register themselves on the DNS server.
I have tried ipconfig/registerdns with no luck. Wireshark live monitor seems to stuck at dynamic update with domain controller.
Please advise.
Jimmy
can you ping your DNS server from the others?
ASKER
Yes, ping works fine between all servers
what happens when you manually creater a pointer in your DNS to one of the server? Does it react normally after that?
Didn't you forget to change DNS adresses in the other servers NICs?
Didn't you forget to change DNS adresses in the other servers NICs?
ASKER
I have not manually created any pointer. Shouldn't the server update themselves?
The DNS address looks fine under NIC property.
The DNS address looks fine under NIC property.
Do you have DHCP server activated? did you set the DNS in the scope options?
Usually the DHCP register the machine into the DNS automatically.
But it can happen, even if you have DHCP server activated on the DNS server that static IP don't register themself.
That's why i usually prefer creating myself pointers to the other servers rather than waiting for an hypotetic self-register.
Usually the DHCP register the machine into the DNS automatically.
But it can happen, even if you have DHCP server activated on the DNS server that static IP don't register themself.
That's why i usually prefer creating myself pointers to the other servers rather than waiting for an hypotetic self-register.
ASKER
Sorry, forget to mention. All these servers are statically configured.
Sorry, forget to mention. All these servers are statically configured
Indeed! (not very usual to have servers with dynamic IPs)
Just read what i wrote just before, this is one of the reason that can explain why they dont register in the DNS.
Let's be more theorical with a microsoft definition :
"A computer that is configured to use Dynamic Host Configuration Protocol (DHCP) to obtain IP addresses can automatically register its IP address and Domain Name System (DNS) name with the DNS server that is authoritative for the zone that hosts its domain. This eliminates the need for an administrator to manage host (A or AAAA) resource records for client computers."
That means that if your secondary servers have DHCP client service disable and are set to static IP, they will hardly register themselves into your DNS server.
This is why you need to manually create pointers to avoid a mess.
ASKER
Thanks, when you say pointer, you mean in reverse lookup zone?
What about forward lookup zone?
What about forward lookup zone?
ASKER
Actually there is one server that has dynamically registered successfully, and I have no idea how though.
Just create manually A Hosts into your domain folder under your forward lookup zone and you won't have to worry anymore.
ASKER
thanks again.
So that means there is no dynamic way of doing this, correct?
So that means there is no dynamic way of doing this, correct?
If dhcp service is not active on client side, not to my knowlegde
ASKER
actually DHCP service is running on client side, but we do not have DHCP server setup though
You got the answer then
ASKER
thanks, actually I just setup another server within the same subnet as the domain controller, and that server does not have any issue register with DNS
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No other accepted solutions