<div>
Thanks Mahesh, but 127.0.0.1 is not a public ip, that's called the localhost so is just pointing back to itself same as using the server IP.
</div>


<div>
Yes that is a good point.. My apologies, I'll try tonight and I'll create those forwarders to the current DNS.<br />
Will post my results later.<br />
<br />
Many thanks to you gurus..
</div>


<div>
The detailed explanations given by FinservCo are absolutely perfect and worth.
</div>


<div>
I did all the steps as advised but I guess my only choice is as Mahesh advise to remove the problem and reinstall, unless you guys have a better Idea, I have attached all TXT files of the 3 tests requiered:<br />
NSLOOKUP<br />
DCDIAG /TEST:DNS /V<br />
DCDIAG /V<br />
<br />
I hope not to have to redo, just restarting this OLD monster is a pain on the neck.<br />
ALSO<br />
- This is the ONLY server DC, DNS, etc. NO EXCHANGE, NO IIS.<br />
- Used only as a File Server<br />
about 120 users 80 constant, contains some folders that are ADMIN ONLY, and other bells and whistles that has taken me a few hairs to figure out permissions and security.<br />
<br />
Thank you.<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/11_w48/885008/DNS-Error.txt" target="_blank" class="file-inline" title="netdiag /fix and nslookup test (2 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>DNS-Error.txt</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2014/11_w48/885009/dcdiag-test-v.txt" target="_blank" class="file-inline" title="dcdiag /test:dns /v (9 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>dcdiag-test-v.txt</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2014/11_w48/885010/dcdiag-v.txt" target="_blank" class="file-inline" title="dcdiag /v (10 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>dcdiag-v.txt</a>
</div>


DNS-Error.txt

dcdiag-v.txt

dcdiag-test-v.txt

<div>
About the dual adapters. &nbsp;Domain controllers should never be multi-homed (have more than 1 IP address). &nbsp;If your adapters support teaming, then they could be teamed with the one IP address. &nbsp;That way if one gets disconnected the other will still work.
</div>


<div>
Thank you Mahesh and FinServCo, this is my nightmare Legacy, this server was untouched for the last 10 years working with XP machines, when I took over (about a week ago) I thought it was going to be a walk in the park, boy I was wrong.<br />
Once I start the migration to windows 7 Hell broke loose with DNS, so I use the back door and simply avoid joining the domain and simply using the account name and password so the server would at least provide access to the users, it worked.<br />
I have no Idea why it has 2 nics but I will disable 250 since it seems is the one unused, and adding an Application DC, I don't thing the owner will allow me, but thanks for the insight.<br />
Also I weighted moving to Virtual but no can do, and the more I dig into the folders and documents the more I believe I should stick with this and fix the DNS, thankfully the backup somehow works I've check that every single file is accounted for, they use a NAS backup and SOS in the cloud, so files even if the server goes down are protected.<br />
I'm going to check that dns entry, since is part of the dns from the provider.<br />
I'll keep you posted.
</div>


<div>
I added the forwarder and got rid of the extra DNS, disabled the NIC, tested Internet in the server and the DNS is now working Hoorah, not so fast..<br />
I'll close and give you guys the points because the DNS is finally working in this server but I will open another post since the windows pc's still dont like the server, so I guess is a different task.<br />
Thank you for your help to both.
</div>


<div>
Just make sure if you're using DHCP for all the workstation computers that they're being assigned the correct IP from the DC (the one you don't remove) to use as a DNS server, and no other.
</div>


<div>
Thank you, it has been a nightmare for me but thanks to Mahesh and FinServCo, I solve 1 of my issues, now I need to tackle the other one.
</div>


<div>
Thanks also footech but DHCP does not come from the DC, and even though the DNS on the computers is pointing to the server once I do that the Internet goes off, (but it works in the server after setting up the forwarders, I'll create another thread and explain better.<br />
Thanks for your concern.
</div>


<div>
The setting should be the same whether you're using DHCP on the server or on some other device. &nbsp;The DNS IP handed out should only be that of the server (otherwise you're likely to experience problems). &nbsp;The server should resolve DNS queries on behalf of the workstations in order to reach resources on either the internal network or the internet. &nbsp;But as you said, you can open another question if you need more assistance.
</div>


<div>
<div class="content wysiwyg-content">
I have now a Windows 2013 Server that someone built a long time ago, it has been in use as a file server, it is an OLD, OLD Server but the owners do not want to go with a new one, so my task:<br />
Repair the DNS on the server<br />
Login all accounts to the server.<br />
EASY?, not so fast..<br />
The person that created the server had the brilliant Idea to name the server as:<br />
my.first.server.com (name just changed for safety but XXXX.XXXX.XXXX.COM is real)<br />
I have tried a few things but so far:<br />
from a windows 7 pro:<br />
Uder Computer Properties/ Change Settings<br />
Either using Network ID or Change.<br />
Trying the full domain name:<br />
An active directory domain controller for the domain my.first.server.com could not be contacted.. etc.<br />
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Dir. Domain Contrlr. for Domain my.first.server.com<br />
The error was DNS name does not exist<br />
error code 0x0000232B RCODE_NAME_ERROR<br />
etc.<br />
<br />
STRANGE ENOUGH, if I try with the WORKGROUP NAME: OurOFFICE<br />
The computer is able to find the domain, asks for an account with admin rights then:<br />
I enter my Admin Name and Password for the domain, then:<br />
Message:<br />
Computer Name/Domain Changes<br />
The following error occurred attempting to join the domain &quot;OurOFFICE&quot;<br />
An attempt to resolve the DNS name of a domain controller in the domain being Joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. etc....<br />
<br />
Now the server nslookup results:<br />
Microsoft Windows [Version 5.2.3790]<br />
(C) Copyright 1985-2003 Microsoft Corp.<br />
<br />
C:\Documents and Settings\Maurice&gt;nslookup<br />
Default Server: &nbsp;localhost<br />
Address: &nbsp;127.0.0.1<br />
<br />
&gt;&nbsp;nslookup my.first.server.com<br />
DNS request timed out.<br />
&nbsp; &nbsp; timeout was 2 seconds.<br />
Server: my.first.server.com<br />
Addresses: &nbsp;10.194.117.250, 10.194.117.251<br />
<br />
&gt;&nbsp;nslookup OurOFFICE<br />
Server: servername.my.first.server<wbr />.com<br />
Addresses: &nbsp;10.194.117.251, 10.194.117.250<br />
Aliases: &nbsp;OurOFFICE.my.first.server.<wbr />com<br />
<br />
DNS request timed out.<br />
&nbsp; &nbsp; timeout was 2 seconds.<br />
*** Request to zacoalco timed-out<br />
&gt;<br />
<br />
The computer is pointing to 10.194.117.251 as DNS (which of course closes the internet unless I add a secondary DNS after)<br />
<br />
So my choices are: <br />
- anyone that can help me guiding me to repair this mess.<br />
- Maybe create a new zone?<br />
<br />
Major issue is the domain name: my.first.server.com that I think is a mess trying to change, demoting/promoting etc. so is there a more viable solution top this mess...<br />
<br />
Thanks for any insight.
</div>
</div>


I have now a Windows 2013 Server that someone built a long time ago, it has been in use as a file server, it is an OLD, OLD Server but the owners do not want to go with a new one, so my task:
Repair the DNS on the server
Login all accounts to the server.
EASY?, not so fast..
The person that created the server had the brilliant Idea to name the server as:
my.first.server.com (name just changed for safety but XXXX.XXXX.XXXX.COM is real)
I have tried a few things but so far:
from a windows 7 pro:
Uder Computer Properties/ Change Settings
Either using Network ID or Change.
Trying the full domain name:
An active directory domain controller for the domain my.first.server.com could not be contacted.. etc.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Dir. Domain Contrlr. for Domain my.first.server.com
The error was DNS name does not exist
error code 0x0000232B RCODE_NAME_ERROR
etc.

STRANGE ENOUGH, if I try with the WORKGROUP NAME: OurOFFICE
The computer is able to find the domain, asks for an account with admin rights then:
I enter my Admin Name and Password for the domain, then:
Message:
Computer Name/Domain Changes
The following error occurred attempting to join the domain "OurOFFICE"
An attempt to resolve the DNS name of a domain controller in the domain being Joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. etc....

Now the server nslookup results:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Maurice>nslookup
Default Server:  localhost
Address:  127.0.0.1

> nslookup my.first.server.com
DNS request timed out.
    timeout was 2 seconds.
Server: my.first.server.com
Addresses:  10.194.117.250, 10.194.117.251

> nslookup OurOFFICE
Server: servername.my.first.server.com
Addresses:  10.194.117.251, 10.194.117.250
Aliases:  OurOFFICE.my.first.server.com

DNS request timed out.
    timeout was 2 seconds.
*** Request to zacoalco timed-out
>

The computer is pointing to 10.194.117.251 as DNS (which of course closes the internet unless I add a secondary DNS after)

So my choices are: 
- anyone that can help me guiding me to repair this mess.
- Maybe create a new zone?

Major issue is the domain name: my.first.server.com that I think is a mess trying to change, demoting/promoting etc. so is there a more viable solution top this mess...

Thanks for any insight.

Win.2013 DNS Screwed UP

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).