[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1217
  • Last Modified:

How do I register the DNS SRV record in DNS?

None of the users can see the Domain.
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for -ldap._tcp.dc._msdcs.dydomain
Common causes of this error include the following:

- The DNS SRV record is not registered in DNS

-One or more of the following zones do not include delegation to its child zone:

dydomain. (the root zone)
0
rockette
Asked:
rockette
  • 8
  • 7
2 Solutions
 
oBdACommented:
If your AD domain name is indeed "dydomain" (no top-level domain like .local, .intra, .com, .whatever), then that's your problem.
If this is a fresh AD installation, I'd recommend to wipe it and recreate with a proper DNS name.
Otherwise check this article about how to work around the DNS problem (but you may experience other problems related to a single-label domain name):
Information about configuring Windows for domains with single-label DNS names
http://support.microsoft.com/kb/300684
0
 
rocketteAuthor Commented:
It is a single label DNS but it appears on the DNS as dydomain.local. If there is no TLD how should I enter the domain if I do a clean install and thanks for your help?
0
 
oBdACommented:
Just enter dydomain.local as domain name when running the dcpromo wizard; use dydomain as NetBIOS (pre-Windows 2000 domain name) domain name.

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/?kbid=237675

10 DNS Errors That Will Kill Your Network
http://mcpmag.com/features/article.asp?EditorialsID=413

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036

How to Verify the Creation of SRV Records for a Domain Controller
http://support.microsoft.com/?kbid=241515

SRV Resource Records May Not Be Created on Domain Controller
http://support.microsoft.com/?kbid=239897

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/?kbid=314861

Windows Server 2003 Service Pack 2 32-bit Support Tools
http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90

The Domain Name System name recommendations for Small Business Server 2000 and Windows Small Business Server 2003
http://support.microsoft.com/?kbid=296250
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
rocketteAuthor Commented:
Can I just wipe AD and no dto a complete reinstall?
0
 
oBdACommented:
Certainly. Just demote it (pick "Last DC"), remove any traces it might had left in DNS, then repromote it.
0
 
rocketteAuthor Commented:
thanks very much for your help and time. I'll try it  tomorrow!
0
 
rocketteAuthor Commented:
I'm still having exactly the same problem after removing and reinstalling AD. I called the domain newmetchem.local
This is the error message when I tried to get a user to join the domain newmetchem.local
(I did specifically ask to join metchem.local)
Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain newmetchem.local:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.newmetchem.local

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

newmetchem.local
local
. (the root zone)

I ran NSLOOKUP and it looked OK as far as I could see.
(It showed priority, weight, port etc) and the IP's of both network cards.
I ran it again after a reboot and  I got a non-existent domain message.

I haven't set DHCP on the server as yet - I'm getting the user network addresses direct from dhcp on  the router but I'm specifically allocating addresses on the 2003 server. When I try to get a web page on the server it's flaky - finds it, then doesn't. then does!!

The external network card attaches to the router with an address of 192.168.0.15, subnet mask 255.255.255.0, default gateway 192.168.0.100 (router) and DNS 127.0.0.1
The internal network card is 192.168.0.1, subnet mask 255.255.255.0, no default gateway and DNS of 127.0.0.1

On one user machine I can change the DNS from the router's to the 192.168.0.1 and get web pages - on another machine it fails to find pages when setup like that.
Any clues?


0
 
oBdACommented:
Make sure that dynamic updates are enabled for your forward lookup zone, and carefully read the DNS articles I linked above: "on one user machine I can change the DNS from the router's" is where your problems start. *All* domain members (including the DC) may *only* use your DC as DNS server, and your DNS should forward to your router or your ISP's.
0
 
rocketteAuthor Commented:
OK thanks.
I'm having problems because I can't even seem to be able to ping the Domain and now I wonder if it's a network issue rather than a server issue. But, I can ping the external network card on the server but not the 192.168.0.1 card.
Am I missing something?  Is there something preventing me pinging the IP?
0
 
oBdACommented:
You only need one NIC in your DC; you have a dedicated router.
Plug the router into the same switch with the rest of the machines. Decide for one NIC in the DC to keep, disable the other one, use the one you kept as *only* DNS server on *all* machines, and use the router's IP address as default gateway.
0
 
rocketteAuthor Commented:
Thanks - that does make sense. I'll try that tomorrow! Interestingly, even though I couldn't ping the DC with any machine, I could get my mac laptop to use the DC's DNS even though it wouldn't ping. Do I have to use DHCP from the domain or can I use DHCP from the router as long as I explicitly enter the server's DNS?
0
 
oBdACommented:
If you can set the router's DHCP options to hand out your DC as DNS server instead of itself, then you can use the router's DHCP as well.
0
 
rocketteAuthor Commented:
Thanks for all your help and the original problem is solved - it looks like the issue was down to using both network cards. Having disabled one as you suggested, users could join the domain. I can't make the router supply a DNS that isn't its own (limitation of router) but I can specifically point to the server's DNS although this does seem a little slower than pointing directly to the router. I'll eventually remove DHCP on the router and install on the server. I haven't done anything to the server DNS since reinstalling AD. Any ideas on browsing speed?
0
 
oBdACommented:
You can experiment with (different) Forwarders versus Root Hints (that is, no forwarders at all configured, the DNS server will then query the root DNS servers), but your clients *have* to use your DC as DNS server.
0
 
rocketteAuthor Commented:
Succinct answers and very patient!
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now