SRP527W not acting a DNS Server/Proxy

Hi Guys
We have a SRP527W with 1.1.24 firmware.
We have DHCP disabled and have assigned a IP address of 10.65.73.254 on the Interface Setup/Lan/VLAN Settings/data_lan.
When I configure a client to use 10.65.73.254 as its DNS server it cannot resolve hostnames eg (www.cisco.com). Obviously I have 10.65.73.254 as the default gateway on the client and it can ping the external host via IP Address so it only appears to be the modems function as a DNS Server that is not working.
From the diagnostics ping I can put in www.cisco.com and it resolved and works, so the modem is correctly getting it's DNS Settings from the ISP
Any ideas?
Thanks
Darren

Hi Daniele,
Thanks for confirming what I was seeing.
I have done some further testing, it seems it is a bug introduced in 1.1.24, a modem with 1.1.23 does not seem to show the same problem, although it does take some time to resolved DNS addresses with the 1.1.23 release.
I got around the problem by renabled DHCP on vlan 1 (therefore removing the ip address on the vlan), went back to the quicksetup /lan put the 10.65.73.254 address on the lan, then went back to interface/lan/vlan and change it back to static and put the 10.65.73.254 address back. Now it seems to be resolving.
So even though lan address seems to be disabled, it must still be working for DNS
Cheers
Darren

Similar Messages

Stop RV082 acting as DNS server?

We have a RV082 that we're using soley for routing and no other services (firewall is disabled). For some reason you can query a DNS server on it even though we have never set a DNS server address for it to use. I'm guessing that it has some hard-coded DNS system to use with the System Management > Daignostic > DNS Name Lookup utility. Because you can query this DNS service from outside the router, this actually gets flagged by our security scanners as a DNS vulnerability. Is there no way to disable this DNS server?

Hi It, here is an excerpt from the product documentation. Are you using the DHCP from the router? Did you specify any DNS value on the router? It seems by default the router acts as a DNS proxy (using your WAN setting to feed DNS to the LAN client). Keeping the value at 0.0.0.0 makes the router service as a DNS proxy.
DNS (used for DHCP Server only)
Optionally, enter the IP address of a
DNS Server
. You also can enter a secondary
DNS server. Specifying a DNS server can provide quicker access than using a
DNS server that is dynamically assigned through the WAN settings. You can keep
the default setting of 0.0.0.0 to use a dynamically assigned DNS server.
-Tom
Please mark answered for helpful posts

Not able to debug server proxy

Hi All,
Iam doing File-Proxy scenario.
I set a break point in server proxy code.
But the breakpoint is not getting triggered.
Please help me in this regard.
Thanks.

HI
If u need to debug the server proxy then just go through the below thread.
Debugging Inbound Proxy:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Thnx
Chirag

AppleTV3 will not act as Bonjour sleep proxy

Hi everyone - I'm one of these people who has a 'little bit of everything' in my local network, so its only as I'm tearing it down to move house that I'm starting to find a few things. This one in particular relates to the Bonjour Sleep Proxy on the network - specifically that my AppleTV3s (I have 2 of them), neither will advertise a sleep proxy service (checked using 'dns-sd -B _sleep-proxy._udp local'), resulting in me being unable to wake sleeping machines (which do have 'wake for network' access enabled).
Now I have an old TimeCapsule, and also an old AppleTV2 - which, when I plug them in both will advertise as sleep proxies on the local network - but based on my understanding from this article;
About Wake on Demand and Bonjour Sleep Proxy - Apple Support
Anything later than an ATV2 should also work (i.e. either of the ATV3's). I've tried resetting to defaults, they are both running the latest firmware, and I have confirmed that it doesn't offer the service either over wifi or ethernet. I'm getting rid of unnecessary hardware as I move, the ATV2 and TC being both surplus.
Anyone else come across this and have a solution for ATV3's as a sleep proxy? (other than leaving the ATV2 and old TimeCapsule installed, purely for this purpose)

Hello blindjudge,
I was looking through our resources for information that may help you to troubleshoot the AppleTV not showing in the iTunes sidebar. Check out this article named: Troubleshooting Apple TV not recognized in iTunes found here http://support.apple.com/kb/ts1453.
This section in particular:
1. Restart iTunes (quit or exit and then reopen iTunes).
2. Reconnect Apple TV to iTunes.
Choose iTunes > Preferences (Mac) or Edit > Preferences (Windows), click Apple TV, and make sure "Look for Apple TVs" is selected.
If Firewall is on in Mac OS X (in the Sharing pane of System Preferences), make sure iTunes Music Sharing is selected.
Open iTunes on your computer.
Select the Apple TV icon with "Click to set up" next to it in the Devices list.
Enter the five-digit passcode from your TV screen.
3. Reset.If you are still having trouble, you can try to reset your equipment by unplugging power cords for the following:
Apple TV
Your TV
Your wireless networking equipment or AirPort Base Station
Your router from the power outlet.
Wait thirty seconds and then plug everything back in again.4. Restart your computer.5. Rejoin the network (wireless) or restart your network router.If you have an AirPort Base Station, see the troubleshooting section of the setup guide for your model. If you have a third-party router, check the documentation that came with it.
AirPort Express Setup Guide v4.2
AirPort Extreme Base Station Setup Guide
Designing AirPort Extreme 802.11n Networks
AirPort Extreme (802.11n) Setup Guide
All the best,
Sterling

How to configure DNS server to redirect all web traffic to one external website?

I'd like to use the DNS service on my OS X Server as a way to force all all web traffic to one specific, external website. Not quite sure how to go about configuring it, though - any recommendations?
(BTW, this is, obviously, not our primary DNS server; I intend to silently update the preferred DNS server for users who fail to complete their timesheets in order to force the issue)

Web clients don't generate uniquely-identifiable DNS queries; there's no SRV request or related traffic that you could select on and spoof. So if you do implement this, everything querying the spoofing DNS server will get the spoofed host, or you'll have to spot specific queries that are likely web queries; Facebook, Google, Bing, etc.
If you still want to implement this, then I'd probably replace the DNS server with a runt DNS server (maybe hack dnsmasq or maraDNS, or create yourself a trivial DNS server) and have that always return the specified IP address. This avoids having to hack BIND to be universally authoritative, which is probably on par with hacking a simpler DNS server to always return a fixed IP address, and the latter is probably easier to undo.
A firewall can spot TCP port 80 and port 443 traffic, unlike a DNS server. Firewalling outbound port 80 traffic is more typical of these requests, and either trap that traffic to a specific web page based on the capabilities of the firewall, or the web proxy approach that Camelot suggests. There are folks that tie access into the web proxies into external authentication and related; that'd be able to do what you want. Web proxies are usually combined with firewall blocks, as most sites want only the web proxy to have external access, too. But this is also rather more pieces than a DNS redirect, too.

Configure single CSS as authoritative dns server

Hi Experts,
I have one CSS11501 acting as the load balancer. And all the servers are in private network behind it. We need to configure an authoritative dns server for this web domain. I want to use this CSS to be the dns server. I saw that there are some advance configuration notes about configuring dns server
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11000series/v6.10/configuration/advanced/guide/DNS.html
I wonder if I only use a single server, what the configuration is needed? is there an example. Most of the documents have the example for multiple CSS in global server load balancing environment.
We currently only have standard feature license. I wonder if we have to purchase the 'enhanced feature set' to implement this function?
Only the command 'add dns xxx.xxx.com' under content rule could be used in the standard software. Is this sufficient enough to be as dns server?
Thanks for your help in advance.

licensing hasn't changed for the CSS in a long time.
So this old document still applies
http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_tech_note09186a0080094a76.shtml
The Enhanced feature set contains all components of the Standard feature set and also includes:
Network Address Translation (NAT) Peering
Domain Name Service (DNS)
Demand-Based Content Replication (Dynamic Hot Content Overflow)
Content Staging and Replication
Network Proximity DNS
Content Routing Agent
Client Side Accelerator
Gilles.

Cisco 1821 as DNS server

Hello I have a cisco 1821 router acting as remote access for vpnclients, LAN LAN VPN device and also
LAN router. All in one.
My LAN has a 192.168.23.0/24 addressing, and router has 2 IP Addresses, one on public IP on the public interface Fa0/1
and 192.168.203.1 on the private interface Fa0/0
I set up it as a name server for local LAN:
ip dns server
ip host pc10 192.168.203.10
ip host pc83 192.168.203.83
ip host c1821 192.168.203.1
I did this so that local PC on my lan can have a resolution for local addresses since I do not have a DNS server inside my line
and I do not have a Active Directory infrastructure.
on the public IP interface my router can be queried for LOCAL IP resolution for my lan 192.168.203.0/24, I Tryed from outside using dig command.
I Wanted to prevent this. I cannot use an ACL because I would prevent DNS queries to work in general. trying to resolve
an external IP Address from inside my lan, I just want the router to refuse DNS resolution for any query coming to external interface,
while I Want to allow only queries coming form my local lan to internal interface.
is this possible in some way ?
thank you
Riccardo

You are asking your IOS device to act as a split-DNS server, providing RFC1918 addresses on internal interfaces, and global address (or no addresses) on the public inetrface.
Look at the "ip dns view" command so you can present differnt DNS responses by interface.
This article may help:
http://www.nil.com/ipcorner/RouterDNS/

Can I avoid setting up a DNS server?

Dear all,
I’m a newbie to set up a server but I recently bought a Mac Mini Server and I have some questions in setting up the machine.
My ultimate goal:
Set up a multimedia server in my Mac Mini Server which provide photos up / download and Quicktime video streaming services for my friends outside my local Lan.
My settings:
ISP (Dynamic IP) →DSL modem →Linksys Router (DHCP) →
1. Web Cam IP: 192.168.1.253 port 50000
2. Synology NAS IP:192.168.1.107 port 5000
3. Mac Mini Server IP: 192.168.1.108
4. Mac Book Pro x 2(wireless)
Since I don’t have a static IP, I registered a domain name which link to my dynamic IP. i.e. abc.viewnetcam.com
I can access my web cam and Synology from outside through port forwarding i.e. http://abc.viewnetcam.com: 50000 & http://abc.viewnetcam.com: 5000
During set up my Mac Mini Server, I was required to enter the Primary Domain Name, since I did not have a DNS server in my local Lan, I entered MacMinSserver.private
After I set up the server, I found that there was a message left on the desktop saying that; ….The domain name servers you’re using don’t have an entry for the domain MacMiniServer.private, and therefore your clients won’t be able to access your server using the name MacMiniServer.private…..
Now here is the question:
1. Can I just simply avoid to set up a DNS server in my Mac Mini Server? Cause it is very complicate; I have read up some information about DNS server settings which make me feel puzzle.
2. If DNS server is a must, so how can I set it? I have read the instructions in the HoffmanLabs, but after setting up the DNS server, how can I access my server from outside? Through port forward?
( Now I can access my server from outside in Safari with URL afp://abc.viewnetcam.com:548)
Many thanks.

I take some time to digest your suggestions. I’m convinced to build up a DNS server, although I don’t fully understand how it works.
DNS is a way to ask a server or a series of servers to translate a string of a specific format into an IP address. If you follow the article in your implementation, then the local DNS services will cooperate with and access external DNS servers world-wide for public DNS translations.
But then questions come up again, first what should be my Primary Domain Name?
I don't know what you're looking at that is using "primary domain name", but the "domain name" you use? I use real and registered and public domains for the domain on private LANs. It's simple, effective, and unique. And I don't have to deal with collisions. I don't prefer to recommend using a made-up domain, as it's a few dollars to get a real domain and then you don't have to deal with collisions if and when you need to expose parts of your network.
Here, a bogus TLD would be, for instance, macminiserver.myhouse.ngmy69; that's a top-level domain (ngmy69) (TLD) that is not allocated, and unlikely to be publicly allocated, and a subdomain (myhouse) of your choice, and a host name (macminiserver) of your choice. (There are around 300 TLDs already allocated and live, and more are on the way. com, net, biz, org, travel, cat, two-character country codes, and more...)
This is listed in the article, including the trade-offs, and including a description of bogus domains.
As you said that the external DNS and the internal DNS should be separately functioning, then is it true that I have the freedom to choose my Primary DNS name? Or I have to stick to certain rules?
DNS and IP routing work by cooperation. You have to stick to certain rules, and the article guides you through the four general choices for picking a domain name.
In my case, do I need to use the external domain name, i.e. macminiserver.abc.viewnetcam.com or I rent another registered domain name and it will be macminiserver.xxxxx.com or even I create an imaginary name?
After you get your LAN DNS going, then read the [dynamic DNS article|http://labs.hoffmanlabs.com/node/1541].
Here, you've picked a domain (viewnetcam.com) name that's real and registered. That, and the use of the abc and macminiserver subdomains are something you'd have to work out with the folks administering that domain. While it is technically a domain name, macminiserver.abc.viewnetcam.com is also variously called a host name, as that'll usually have an associated IP address, and a subdomain like abc.viewnetcam.com might and variously will not.
With a real and registered domain (your own registered domain, or a DynDNS host), you can (later) choose to expose parts of your network. You don't own a DynDNS name, and DynDNS doesn't allow you to use various server functions and you can't use that on your LAN. DynDNS is a good solution for remote access into a home network and even for a VPN connection in but (if you're eventually looking to use mail or secure web access or other features) you'll usually end up using your own domain name.
The second question is that, how can I avoid using the subnet 192.168.1.0/24, as my router is providing the DHCP service, will that means I need to re-organized the whole network included the web cam and my Synology? Is there any simple way to achieve that?
It's the effort you think it is, and it involves getting that gateway server reconfigured to have its address in a different subnet and the DHCP server reconfigured to pass out addresses within a range within that subnet, and this is an effort that scales as your network increases and as you get IP addresses embedded. If you're going to do remote access via VPN, many home networks and many coffee shops will use 192.168.0.0/24 or 192.168.1.0/24, and having the same subnet on both ends of the VPN means IP routing tosses a snit.
[Please read the DNS article|http://labs.hoffmanlabs.com/node/1436] through, and then post up questions you might have.

DNS server cannot be created because the authoritative parent zone

I am working in 2008r2sp1. I tried adding DNS Server and DHCP Roles first. Then under DNS Forward Lookup Zones I added "mysite.com" as a New Zone.
Also I searched my computer for a "NTDS" folder and the only on I found was "C:\Windows\inf\NTDS".
A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS infrastructure, you should manually create a delegation to this DNS server in the parent zone to ensure reliable name resolution from outside the domain "artisdextri.com". Otherwise, no action is required.
The folder C:\Windows\inf\NTDS> is not valid. Specify a valid path, including drive letter. For example: C:\NTDS.
dcpromo /unattend:"C:\Users\Administrator\Documents\ForestAdd.txt"
ForestAdd.txt
[DCINSTALL]
InstallDNS="yes"
NewDomain="forest"
NewDomainDNSName="mysite.com"
DomainNetBiosName="MYSITE"
ReplicaOrNewDomain="domain"
ForestLevel="4"
DomainLevel="4"
DatabasePath="C:\Windows\inf\NTDS>"
LogPath="C:\Windows\inf\NTDS"
SYSVOLPath="c:\Windows\SYSVOL"
SafeModeAdminPassword="pass1"

Hello,
If this is the first forest root DC, just ignore the information.
Check the blog:
A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server.
http://blogs.technet.com/b/activedirectoryua/archive/2011/07/07/a-delegation-for-this-dns-server-cannot-be-created-because-the-authoritative-parent-zone-cannot-be-found-or-it-does-not-run-windows-dns-server.aspx
Hope this helps.

Incorrect DNS when using DHCP. DNS server is considered to be a Virus??

Running 10.5.5. Noticed extreme slow down in resolving domains in safari, firefox. I currently use Verizon FIOS. When looking in network settings it shows a DNS server as 85.255.115.30. This is not verizon's DNS server. When I delete that server out and add the Open DNS server's address internet works great. This is not an issue on Verizon's end because any ethernet connection to any internet provider will default to using that address for DNS. Only does it over ethernet. Tried deleting the port and re adding and still comes back. No issues when booted off another drive. Mcafee says that a Trojan changes the DNS on PC's. No PC's are networked to this mac. I cannot delete this DNS server under the DNS tab in advanced settings...?

That IP address does seem to fall within the range known to have been used by the DNS changer trojan (try searching the web for "DNS changer", puper, OSX.RSPlug.A, 1023.dmg, etc.). That very likely means that at some point, malware managed to run with "root" privileges on your system.
Under such circumstances, it would be safest to back up all of your data and reinstall the OS and applications from known "good" media.

Register global IPv6 Address on NRPT defined DNS-Server

Hello
I have implemented IPv6 on my home network and I am using Windows Firewall with IPSec to secure connections from foreign networks to my home network.
I configured a NRPT with generic rules for my domain so my client is using the home DNS-Server to resolve names of computers on my home network. This is working quite good so far but I it seems like the foreign client does not register his own
global IPv6 on the home DNS-Server.
When i run ipconfig /registerdns the list of servers to which the update has been sent to is empty (<?>) while the DNS-Server list does not mention the DNS-Server configured using NRPT. So my very simple question is: How can I configure my Client to
register DNS based on the NRPT or a static list of DNS-Servers?

Hi,
Does the FQDN of the foreign client match the NRPT rule?
Please make sure that the FQDN of the foreign client matches the NRPT rule. Then when the client try to send a update packet, it will be redirect to the internal DNS server.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Removing a DNS Server

Hello everyone,
I have a single forest with
multiple domains .
We have five Domain Controllers,some of
them are Server 2008 R2 and others Server
2012 R2(On all installed DNS server)
I recently started to upgrade the DC 2008 R2 to 2012 R 2 and now i would like to remove the DNS server from DC 2008 R2.
All the zones in all DNS servers are Active Directory - Integrated zone.
I found this article : http://technet.microsoft.com/en-us/library/cc794727(v=ws.10).aspx ,
but do not really understand the first two items.
How I remove the DNS server from the forest?
Thanks in advance,

I recently started to upgrade the DC 2008 R2 to 2012 R 2 and now i would like to remove the DNS server from DC 2008 R2.
All the zones in all DNS servers are Active Directory - Integrated zone.
I found this article : http://technet.microsoft.com/en-us/library/cc794727(v=ws.10).aspx ,
but do not really understand the first two items.
How I remove the DNS server from the forest?
Thanks in advance,
Greetings!
If you are upgrading your domain controllers to 2012, why are you taking this method? If you want to keep this DC operational do not remove the DNS server separately or you will experience difficulties during installing DNS again. Transfer FSMO roles to
an available DC and demote 2008 servers and re-promote after installing 2012.
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Cisco 877W acting a a DNS server. Does it answer external DNS queries coming from the WAN

Hello,
I have a Cisco 877W running on my ADSL2+ service at home.
It is setup to act as a DNS server to answer DNS queries for my LAN and has the below commands as part of its configuration
ip dns server
ip dhcp pool LAN
network 192.168.2.0 255.255.255.0
default-router 192.168.2.254
dns-server 8.8.8.8
My question is, when I scan my WAN IP for open ports, port 53 (DNS) is open. Does this mean my router will be acting as a DNS server for anyone on the internet who directs DNS queries to my WAN IP?
If so, am I able to turn off port 53 towards the Internet, or do I need to add an an access-list to only accept queries from my internal network.
Thanks for your feedback.

That's correct. The "ip dns server" command will answer queries on any interface.
Given that your DHCP server is telling your clients to use Google DNS and not your router, I would just turn the router's DNS server off with the "no ip dns server" command.
Setting up an ACL (and/or inspection or zone-based firewalling) on your Internet-facing interface is the best practice to protect your network in general, not just to prevent external DNS queries.

Configure proxy and dns server for a single URLConnection

Hello!
I am relatively new to network programming in Java so I was looking for a solution to set a DNS server and a PROXY server for one SINGLE UrlConnection. The settings should only be used in one thread, while another thread maybe has different settings.
The most suggestions I found on the net looked like follows:
Proxy:
System.setProperty("proxyPort","8080");
System.setProperty("proxyHost","proxy");
DNS Server
sun.net.spi.nameservice.provider.<n>=<default|dns,sun|...>
sun.net.spi.nameservice.nameservers=<server1_ipaddr,server2_ipaddr ...>
sun.net.spi.nameservice.domain=<domainname>
The problem is that both solutions are not thread safe and the settings are valid system wide (as far as I am understand). In my application a lot of different workerThreads open a connection to a remote server via URLConnection , for example:
URL url = new URL("http://www.sun.com");
HttpURLConnection con = (HttpURLConnection) url.openConnection();In the worst case 200 different workerThreads open a connection nearly at the same time. If the worst case happens one workerThread changes the DNS and PROXY settings and in the next step another thread which already has set dns and proxy tries to connect to a specified server with wrong dns and proxy settings.
One solution would be to synchronize the whole method that configures the connection and tries to connect to a remote server but that would be a very bad solution for me, because all other threads have to wait until the last thread has finished.
My question: Is there a possibility to configure a different DNS server and a different PROXY server for each URLConnection, for example something like:
URL url = new URL("http://www.sun.com");
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setProxyHost("proxy");
con.setProxyPort("3128");
con.setProxyUsername("user");
con.setProxyPassword("pass");
con.setDNS("85.27.63.2");Thanks in advance for your answers.
Kind regards,
Buliwyf

Mainly because it's in the spec. I did not figure out exactly why it is necessary to use different dns servers. Let me give you a quick glimpse what the application should do:
The application checks if a URL is still available and returns an xml file with a return code (401 for example), connection time, an extract of thesource code and other information. This event repeats periodically (every 10 s, 20 min...). Therefore the customer has a good overview about the availability of his websites.
The customer himself controls the process with a xml configuration file that is read on the startup of the application. In the xml file you can find information like: connection timeout, http proxy, https proxy, used user agents, prefered request method (post or get) and regretfully even the DNS server that should be used.
Regretfully I don't have a chance to get the dns removed from the spec. The GUI which delivers the xml is already implemented and won't be changed.

Error: Missing SRV record at DNS server - [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

in an attempt to transfer FSMO roles to the 2012r2 DC the first thing I ran was dcdiag /e /c /v and after correcting some minor errors, I came upon this one in the DNS portion where a SRV record is missing and I have no idea how to fix/remove this. there's
only two DCs, 200.5 and 200.6 where the former is a Hyper-V VM running 2012r2 and the latter is a physical 2003r2 machine. I was able to successfully raise the levels to 2003 and join the 2012r2 DC. this missing SRV record does not look fatal and only warrants
a warning from dcdiag, however I would like to fix this so there's no trouble down the road. I've tried ipconfig /registerdns, but no dice. here is the message I'm concerned about:
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
the bottom portion of the DNS section that contains this message is in the RReg section and is as follows:
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters

Hi Ace Fekay, thank you for your help. I hope you're still with me despite my lack of responding. I needed time to move the VPN server from the DC to a separate VM and then following your instructions to disable WINS Proxy and IP routing. Some of the delay
was when I had to restart the 2003r2 server after disabling those two items since that cause DNS queries to the Internet to go unresolved with only the 2012r2 server. That's been corrected, but running dcdiag /c /e /v still gives some DNS problems. Here's
the latest run of that...
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
Starting test: DNS
See DNS test in enterprise tests section for results
......................... CM-DC-NY01 passed test DNS
See DNS test in enterprise tests section for results
......................... CM-DC1-NY01 passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : cmedia
Starting test: CheckSDRefDom
......................... cmedia passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... cmedia passed test CrossRefValidation
Running enterprise tests on : cmedia.local
Starting test: DNS
Test results for domain controllers:
DC: cm-dc-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 2.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.6
DNS servers:
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
192.168.200.5 (CM-DC1-NY01) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
Matching CNAME record found at DNS server 192.168.200.6:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.pdc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.5:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.pdc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
DC: CM-DC1-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000010] Microsoft Hyper-V Network Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.5, 0000::0000:0000:0000:0000
DNS servers:
192.168.200.5 (CM-DC1-NY01) [Valid]
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 128.9.0.107 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 128.8.10.90 [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 198.32.64.12 (l.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12 [Err
or details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:1::803f:235 [Error details: 1460 (Type: Win32 - Description: This operation ret
urned because the timeout period expired.)]
DNS server: 2001:500:2::c (c.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2::c [Error details: 1460 (Type: Win32 - Description: This operation returned b
ecause the timeout period expired.)]
DNS server: 2001:500:2d::d (d.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2d::d [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:84::b (b.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:84::b [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:ba3e::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retu
rned because the timeout period expired.)]
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:c27::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retur
ned because the timeout period expired.)]
DNS server: 2001:7fd::1 (k.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fd::1 [Error details: 1460 (Type: Win32 - Description: This operation returned bec
ause the timeout period expired.)]
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 128.9.0.107 (b.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2f::f [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:3::42 [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fe::53 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:dc3::35 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 128.63.2.53 (h.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.112.36.4 (g.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.168.200.5 (CM-DC1-NY01)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS server: 192.168.200.6 (cm-dc-NY01.cmedia.local.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS delegation for the domain _msdcs.cmedia.local. is operational on IP 192.168.200.6
DNS server: 192.203.230.10 (e.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.228.79.201 (b.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.33.4.12 (c.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.36.148.17 (i.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.5.5.241 (f.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.58.128.30 (j.root-servers.net.)
All tests passed on this DNS server
DNS server: 193.0.14.129 (k.root-servers.net.)
All tests passed on this DNS server
DNS server: 198.41.0.4 (a.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.83.42 (l.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.91.13 (d.root-servers.net.)
All tests passed on this DNS server
DNS server: 202.12.27.33 (m.root-servers.net.)
All tests passed on this DNS server
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: cmedia.local
cm-dc-NY01 PASS PASS PASS PASS PASS WARN n/a
CM-DC1-NY01 PASS PASS PASS PASS PASS WARN n/a
......................... cmedia.local passed test DNS
Starting test: LocatorCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test LocatorCheck
Starting test: FsmoCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test FsmoCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
provided.
......................... cmedia.local passed test Intersite

SRP527W not acting a DNS Server/Proxy

Similar Messages

Maybe you are looking for