Weird DNS Issues
-
@scottalanmiller said:
See the search name in the working one? That is missing in the not working one I think.
I see it in both.
Is there any clue as to why this is ONLY name resolution problems to the fileserver and nothing else?
-
Can't think of anything. If every setting is the same.
-
@garak0410 said:
Is there any clue as to why this is ONLY name resolution problems to the fileserver and nothing else?
Host files, LMHOST files If the other servers are answering to NetBIOS over IP calls where the new file server won't.
My biggest guess is the last one.. Windows 2012 server might not be resolving NetBIOS names any more...
-
Assuming you didn't install WINS on your new AD server you should remove the WINS information from all clients and from the DHCP server so it's not handing out that information.
This will also cause issues in some cases. -
Oh good point. Don't want old WINS mucking about.
-
This post is deleted! -
@Dashrender said:
Assuming you didn't install WINS on your new AD server you should remove the WINS information from all clients and from the DHCP server so it's not handing out that information.
This will also cause issues in some cases.Let me take a look at this.
Now, I KNOW I checked this but I guess I overlooked it and I know it wouldn't just go away. There was no reverse lookup for the file server (services01 is its physical name). I just added it.
-
@garak0410 said:
@Dashrender said:
Assuming you didn't install WINS on your new AD server you should remove the WINS information from all clients and from the DHCP server so it's not handing out that information.
This will also cause issues in some cases.Let me take a look at this.
Now, I KNOW I checked this but I guess I overlooked it and I know it wouldn't just go away. There was no reverse lookup for the file server (services01 is its physical name). I just added it.
Good to have but should not matter.
-
@scottalanmiller said:
@garak0410 said:
@Dashrender said:
Assuming you didn't install WINS on your new AD server you should remove the WINS information from all clients and from the DHCP server so it's not handing out that information.
This will also cause issues in some cases.Let me take a look at this.
Now, I KNOW I checked this but I guess I overlooked it and I know it wouldn't just go away. There was no reverse lookup for the file server (services01 is its physical name). I just added it.
Good to have but should not matter.
k...this morning has been rather quiet SO FAR. Only one user had problems.
-
Thanks for the help on this. I appreciate the positive candor in the midst of gaps in my DNS knowledge...
-
What did you change that seems to have solved the issue?
-
Its working now?
-
Good Morning...it seems to be stable now. Here's what I did but not sure what fixed it.
The reverse lookup zone showed an UNKNOWN IP for the new DC/DNS server. Added it.
Rebooted the file server (which was the only one having DNS name resolution problems).That's really it...I spent most of the time giving users workarounds.
The NEW DNS server shows no replication issues at all. Looks healthy.
-
How many DCs and DNS servers do you have now?
Did you remove WINS from the DHCP options?
-
Glad to hear that things are working.
-
@Dashrender said:
How many DCs and DNS servers do you have now?
Did you remove WINS from the DHCP options?
Still have the new Server 2012 and the soon to be demoted 2003. I've not removed WINS yet due to the need to check the legacy systems in our machine shop.
-
If you've turned off the 2003 server already, you should remove WINS from DHCP now. You could be causing yourself more issues by having it, than you will by removing it, again assuming the 2003 server is already off.
