Cannot Be Queried For Soa Error
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack
The Namespace Cannot Be Queried. The Specified Server Cannot Perform The Requested Operation
Overflow the company Business Learn more about hiring developers or posting ads with us
The Namespace Cannot Be Queried 2012
Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network the dfs service status cannot be queried service dfs was not found on computer administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top NameServer SOA https://www.namepros.com/threads/dns-issue-nameserver-xxxx-cannot-be-queried-for-soa.839204/ records misconfigured up vote 2 down vote favorite This is my config of NS. hostingdk.com. SOA zone1.hostingdk.com admin.hostingdk.com 2010051905; 43100; 7200; 2419100; 86400; hostingdk.com. NS zone1.hostingdk.com. hostingdk.com. NS zone2.hostingdk.com. zone1.hostingdk.com. A 96.30.49.11 zone2.hostingdk.com. A 96.30.46.238 Both zone1 & zone2 have registered name server in Enom domain control panel. My problem is, one domain .lv cant not change DNS to my NS. They said: Error : Nameserver zone1.hostingdk.com cannot be queried for SOA http://serverfault.com/questions/143237/nameserver-soa-records-misconfigured Error : Nameserver zone2.hostingdk.com cannot be queried for SOA Please help me, how to fix it ? domain-name-system domain-name nameserver share|improve this question edited May 19 '10 at 11:23 pauska 17.2k44272 asked May 19 '10 at 3:40 Khoa Bui What is the domain you are trying to point to the DNS? If you can provide us with that detail, we can probably diagnose the issue easier. –Mark Henderson♦ May 19 '10 at 3:43 he already did - it's in the SOA record above –Alnitak May 19 '10 at 15:37 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote The error being reported is because your two servers (zone1 and zone2 above) are not correctly serving your zone file: % dig +norec @96.30.46.238 hostingdk.com. soa ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec @96.30.46.238 hostingdk.com. soa ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 5139 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 This may be because of the semi-colon issue pointed out by @Dom - in which case the server logs on those two boxes should tell you that. If you're running BIND, use named-checkzone to check the syntax of your zone files. If
& MappingSocial Networking & CommunicationUtilitiesWeb BrowsersComputer & HardwareGadgetsGaming & LeisureSmartphonesMobile AppsWindows Mobile (Pocket PC / PPC)Networking DFS Namespace Cannot Be Queried Error - Remove & Delete Orphaned Namespace Home»Software»Enterprise Solutions»DFS Namespace Cannot Be Queried Error - Remove & Delete Orphaned Namespace DFS Namespace Cannot https://techjourney.net/dfs-namespace-cannot-be-queried-error-remove-delete-orphaned-namespace/ Be Queried Error - Remove & Delete Orphaned Namespace When attempting to view, query, modify or delete a DFS (Distributed File System) namespace with DFS Management MMC (DFSmgmt.msc), Distributed http://dnscheck.pingdom.com/troubleshooting.php File System MMC (DFSgui.msc), DFSutil.exe, DFScmd.exe and other DFS tools, one or more of the following errors may occur, and you cannot perform any view, add, modify or delete cannot be any namespaces and their properties.
\\domain.com\namespace: The Namespace cannot be queried. Element not found. \\domain.com\namespace: The Namespace cannot be queried. The RPC server is unavailable. \\domain.com\namespace: The Namespace cannot be queried. Access is denied. DfsUtil: Contacting registry of windows-server to remove \\domain.com\namespace DfsUtil: Specified registry entry was not found. Could not complete the command successfully. SYSTEM ERROR - Element cannot be queried not found. These namespaces will be marked with red "X" icon in the DFS Management tool. Once it's determined that the namespace is having error, the ability to create new folder, delegate management permissions, delete and view properties is removed from the available actions. It also hinder the ability to create and add new namespaces, especially if you want to replace the namespaces with the same name. The issue occurred because the affected domain-based namespaces that gave error have been removed from the namespace server that is hosting the namespaces, but are not deleted from AD DS namespace configuration. In other words, the namespace is orphaned. Distributed File System (DFS) Namespaces service stores configuration data in several locations, namely: Active Directory Domain Services (AD DS) stores domain-based namespace configuration data in one or more objects that contain namespace server names, folder targets, and various other configuration data. The namespace servers maintain shares for each namespace hosted. The registry keys on the domain-based namespace servers store namespace memberships. Thus, if the DFS namespace confhere below). DNS servers Host: IP: Host: IP: Loading... Troubleshooting guide Adress is invalid or incorrect. Pingdom: The string you provided was not a syntactically correct IPv4 or IPv6 address. Please try again. Private IPv4 address. Pingdom: The address you provided was in a block marked "Private" in RFC 1918. Reverse for - points to an unknown host name. Pingdom: A reverse lookup for the address you provided returned a hostname where queries (for A and AAAA records) either didn't return a reply packet, or returned reply packets with ANSWER sections empty. Could not find reverse address. Pingdom: A reverse lookup for the address you provided didn't return a reply packet at all. Or a reply packet with an empty ANSWER section. Reserved IPv4 address. Pingdom: The address you provided was in a block marked "Reserved" in RFC 3330 or RFC 5735. Reserved IPv6 address. Pingdom: The address you provided was in a block marked "Reserved" in RFC 5156. Not announced. Pingdom: The specified IP address was not announced by any ASN (Autonomous System Number). Name server (ip) announced by: (ip) Pingdom: Team Cymru has the provided IPv4 address listed. The list may be empty. Zone announced by more than one ASN. Pingdom: The total number of ASNs (Autonomous System Numbers) in which the name servers for the zone being tested has listed IPv4 addresses is greater than one. Name server not announced by any AS. Pingdom: The provided IPv4 address is not listed in any ASN (Autonomous System Numbers) Zone announced by fewer than two IPv4 ASN. Pingdom: The total number of ASNs (Autonomous System Numbers) in which the name servers for the zone being tested has listed IPv4 addresses is zero or one. Name server announced over IPv6 by: (ip) Pingdom: Team Cymru has the provided IPv6 address listed as announced by an ASN. This list may be empty though. Zone announced by more than one IPv6