We help IT Professionals succeed at work.

Win.2013 DNS Screwed UP

238 Views
Last Modified: 2014-11-26
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.
Comment
Watch Question

MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Maurice LComputer Tech/Programmer

Author

Commented:
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.
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
CERTIFIED EXPERT
Top Expert 2014
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Maurice LComputer Tech/Programmer

Author

Commented:
Yes that is a good point.. My apologies, I'll try tonight and I'll create those forwarders to the current DNS.
Will post my results later.

Many thanks to you gurus..
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
The detailed explanations given by FinservCo are absolutely perfect and worth.
Maurice LComputer Tech/Programmer

Author

Commented:
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:
NSLOOKUP
DCDIAG /TEST:DNS /V
DCDIAG /V

I hope not to have to redo, just restarting this OLD monster is a pain on the neck.
ALSO
- This is the ONLY server DC, DNS, etc. NO EXCHANGE, NO IIS.
- Used only as a File Server
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.

Thank you.
DNS-Error.txt
dcdiag-test-v.txt
dcdiag-v.txt
Architect
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
About the dual adapters.  Domain controllers should never be multi-homed (have more than 1 IP address).  If your adapters support teaming, then they could be teamed with the one IP address.  That way if one gets disconnected the other will still work.
Maurice LComputer Tech/Programmer

Author

Commented:
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.
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.
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.
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.
I'm going to check that dns entry, since is part of the dns from the provider.
I'll keep you posted.
Maurice LComputer Tech/Programmer

Author

Commented:
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..
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.
Thank you for your help to both.
CERTIFIED EXPERT
Top Expert 2014

Commented:
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.
Maurice LComputer Tech/Programmer

Author

Commented:
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.
Maurice LComputer Tech/Programmer

Author

Commented:
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.
Thanks for your concern.
CERTIFIED EXPERT
Top Expert 2014

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