My point is that you may do this DNS clean up and you still have problem. In regards to " The domain name itself does not resolve well it does, but DNS appears to be forwarding it out, so we're getting an external IP responce so DFS doesn't work.
If you have an authoritative zone on your DNS server and its not using that zone, then yes you do have a major DNS issue.
Is this happening on all of your DNS servers? I would simply try to fix some of these issues before you go down the path you are considering with a DNS cleanup. You can try the following options to change FSMO role server:. I have read ove rthe article and it would apply to The same approach would be taken. Please note that if you decide to take the steps indicated in that article, during the time that you are implementing this change, you will impact your AD Services.
The domain name itself does not resolve well it does, but DNS appears to be forwarding it out, so we're getting an external IP responce so DFS doesn't work. Can you provide more information? What issues and errors are you seeing? How many DCs do you have? Did you check the FSMO role configuration? I've seen it written both ways, so I have always used the DNS server's address as the primary on that server and then a secondary using the other DNS, and then lastly I enter in the loopback.
Now that being said I've never had issues, and I typically run fairly consistent check to make sure AD and DNS are working as expected. Does anyone else have anything I can check on? I don't believe this issue existed before the old servers were decommissioned and think it's probably related to that.
Also, when browsing with a client using only Server1 as DNS server, internet is quick, as expected. When using a client with only Server2 as DNS, browsing the internet still works but all pages seem to load a bit slower flushed dns, released and renewed between the switch. Good suggestion cduff, I will try this tomorrow after hours. Can't wait to figure out what is happening and will report back. Probably something stupid on my end but who knows! Can you ping the gateway? One other thing to check is to make sure that whatever VLAN these servers are running on is set up in the gateway switch.
I've had a time or two when the VLAN was not set up in Vmware's virtual networking for some of our virtualized servers and the behavior was very similar to what you are saying. I can ping the gateway, so it's weird that the gateway isn't accessed when doing a traceroute.
What I failed to mention and realize was bad is that this server is multi-homed, in that it has two physical NICs accessing different subnets. Windows is perhaps getting confused on which adapter to use. So I am going to do some testing and possibly reorganizing of things this week and will post back. Ha meanwhile I am fixing a lot of other errors I'm finding in the event log : Thanks everyone for the input! It's really appreciated! To continue this discussion, please ask a new question.
Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. The event data contains the error. Hello all! So let me explain what I have then I will explain what the issue is. I have a central server running Windows Server R2. All Computers that are connected are running Windows 7 SP1. What am I missing here? Any help would be great and I can clarify if needed.
Thanks again! Wednesday, January 18, PM. Ved Prakash Mishra 0. Run the nslookup to check that DNS resolving your query. Thank you for the quick response. To answer your first question yes. So my DNS is xxx. I don't believe I require a Forward and the Root Hints appear to be set up properly But my two computers are still unable to resolve DNS EDIT: I would also like to point out that the computers go off line about am every day and come back online about pm every day.
This is a pretty consistent thing. Can you pl. I think you are using 2 DNS server? But your sub net is different. Thursday, January 19, AM. Thursday, January 19, PM. All rights reserved. Friday, January 20, PM. Tuesday, January 24, AM. Tuesday, January 24, PM.
0コメント