Delegating URL in dns server

I have configured active directory on windows server 2012, as a example.in. I have another server configured for my website www.example.in. Now i have problem here that whenever i type this url it says that the webpage not found. after troubleshooting i
found that my DNS is resolving this id as a domain controller server, not to my web server
Can any one help me to add this entry in DNS server to reslove this.
Thanks in advance

You can address this two ways.
1) in your dns zone on your local DNS server /domain controller add an "a record" for www or whatever is directing wrong and put in the ip address of the external web server, you can get this by going to a external site and ping the name or doing a dns look
up.
2) you may be able to use conditional forwarder create one with the full url of your website <a href="http://www..com">www.<site>.com and tell it which dns server you want to use to resolve in your case it would be the external dns host for your domain.
Option 1 is normally how we address, I threw in option 2 as an after thought. Option 1 is simpler too.

Similar Messages

  • 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.

  • Delete the DNS delegations pointing to this server

    Good morning,
    I'm getting ready to decommission my Windows Server 2008 R2 server and replace it with a Windows Server 2012 R2 (completely new hardware).  After I decommission my current DC I will reboot it, change its IP address and name and then reboot it again.
     I am then going to give the new server the old IP and name of my old DC (so basically the name and IP address of the active DC will not change).  I'll then promote this server back into the domain.   Since the new DC in the end will have the
    same IP and NAME as the old DC, should I uncheck the "Delete the DNS delegations pointing to this server" when I decommission the old DC since the new one would have the same name?  Thanks!

    You can uncheck it and then promote it. Once done, make sure that the new DC is set under
    Name Servers tab in your zones properties.
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • 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.

  • Modem AEBS Laptop. Which of those should have DNS server details set?

    Hi,
    I have a modem which is connected to an AEBS. And the AEBS connects via air to my laptop. Which of these three things should have the DNS server IP addresses, supplied by my ISP, set in them, and which shouldn't?
    The modem has a web page based set up, which has a DNS set up available. It seems to have a mind of its own and ignore my settings -- resets to what it was before (which isn't the case of other settings for the modem)
    The base station in its set up has DNS server IP address fields, which was already filled in (automatically possibly -- I can't remember) with my ISP's DNS addresses.
    And there's the places for DNS addresses in the Network in System Preferences. This was empty but I've now put in my ISPs settings there. Either way, with or without, doesn't seem to make any difference.
    Can anyone tell me where there is info online about where to put DNS info correctly for a modem > AEBS > computer set up please? Or maybe someone knows?
    TIA,
    John.

    I never set the DNS servers on any client computer, Mac or Windoze. Note that in the DNS Servers: section of the Network Preferences it says (Optional). I suggest you leave that space blank.
    Similarly, if you are using your AEBS as your gateway router and your Internet connection to your is configured Using DHCP there is no need (and no benefit) to predefining the DNS servers.
    If you have a situation where you must pre-set the DNS servers IP addresses, then I would do it only in the AEBS.
    BTW, I assume this is in conjunction with your other thread about the AEBS crapping out every few hours while downloading files. Remember that DNS is used only to resolve names to IP addresses as in each time you call up a different URL. DNS doesn't enter the picture in the middle of any other kind of transaction. I suspect that DNS is not your problem in this case.

  • Use of Public DNS Server

    I have an iMac, Mac Mini and a Macbook Pro connected to a Airport Extreme Base Station. I normally use a Public DNS Server and I am not sure where to put the DNS URLs. Do I put them on the individual computers or is there somewhere in the Airport Extreme Base Station that they go? where ever they belong please provide location and instructions. Thanks.

    Configuring the AirPort Extreme with the DNS makes it so that you do not have to configure each individual computer on the WLAN, the DNS settings will be handed down to the devices when they are given their internal IPs, but as long as the base station does not have a competing/conflicting DNS setup, configuring each individual device, as suggested by Carolyn, works also.
    However, something strange can happen sometimes when you use a public DNS setup. I use the one Carolyn suggests, OpenDNS, but I cannot access any of the webpages of my ISP with this configuration. I have Todo en Uno (All in One), a service that provides cable, telephone and internet service from my local cable company, CableVisión. So with the OpenDNS setup I cannot configure the digital options for my telephone service, such as blocking and unblocking Int'l long Distance calls. I have to remove the OpenDNS setting to do so. But I created a work around using Locations in the Network settings. I have one Location with my ISP's DNS settings and another Location with OpenDNS settings. I can quickly switch between the two when I need to access my ISP's website.
    Dah•veed

  • DNS Server does not resolve new generic Top Level Domain names- CNR configuration issue?

    Hi all,
    I am not sure if this is the correct community to post this question, but I will give it a try. I noticed that the users of my network cannot resolve web sites using new top level domain names, like ".education", ".international", etc. I have an internal DNS server made by Infoblox and a Cisco CNR v6.3.3.1 as an external DNS server. Infoblox uses CNR as its forwarder and CNR uses the root DNS servers for queries.
    I would think that CNR was the problem because it is an obsolete product but after speaking with a fellow engineer at another organization where they still use an older version of CNR than mine, they have no problems at all. So now I am thinking it is a setting either on Infoblox, or on CNR I need to change. I can see Infoblox is forwarding the requests to CNR but that's about it. I am not sure if CNR is discarding the request. When I do an nslookup from a PC in my network it does not matter if I set my DNS server to be the Infoblox or the CNR. Neither resolves the URL.
    Then again, no matter what I lookup using the CNR as my DNS, I only get a response with the root DNS names and IPs!
    Any help is appreciated!

    Hi Constantinos,
    Have you taken a look at the infoblox community site?  We've just reposted your question there and alerted some internal SMEs that should provide a solution soon.  
    https://community.infoblox.com/forum/ddi/dns-server-does-not-resolve-new-generic-top-level-domain-names-cnr-configuration-issue
    Best,
    Eric

  • DNS Server Infrastructure Design

    Good day IT Folks,
    Currently I'm on the planning stage of designing DNS infrastructure of our company. I've read a lot of reading materials available online about DNS. According to what I've gathered, two (2) DNS server is the minimum and three (3) is the recommended for the
    usual set up of DNS. What I want to my DNS infrastructure is to have two (2) DNS servers for my LAN (internal network) and one (1) DNS for my LAN-to-Internet connection (external network).
    The two (2) DNS servers will resolve LAN request and will forward requests to the another one (1) DNS server if internet-related sites is requested. I would like to ask for your help to give me insights how am I going to do this, where to start and what
    are the things I should consider.
    Thanks.
    akosijesyang - the conqueror

    You could go with a secure design such as the following (click on it to open a larger image in a new page):
    See if the following threads help:
    Technet Thread: Problem with Windows 2008 R2 Dns Server getting SERVFAIL resolving one domain, 1/18/2012
    Includes a secure DNS forwarder in the DMZ image
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/b00fc041-ba44-45b6-a8a1-a00374a20edf
    Technet Thread: DNS Structure to rebuild efficiently - Question about the resolution process, 10/27/2011
    Includes a secure DNS forwarder in the DMZ image
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/3a5fb6ac-6ab7-45b1-abab-e0d928a7e06c
    Good discussion on DMZ secured resolver design, and the use of "Unbound DNS Resolver (http://unbound.net/) to use on your DMZ DNS server instead of Windows DNS. (Note: IMHO, for AD, I would rather use Windows DNS. - Ace)
    Technet Thread: W2003 DNS cache snooping vulnerability for PCI-DSS compliance, 10/10/2011
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/67e9189b-606a-40d2-9944-8b4c7d084017/
    And dealing with internal and external names:
    Can't Access Website with Same Name (Split Zone or no Split Brain)
    Published by Ace Fekay, MCT, MVP DS on Sep 4, 2009 at 12:11 AM  1278  0
    Note - In an AD same name as the external name (split zone) scenario, if you don't want to use WWW in front of URL, such as to access it by
    http://domain.com, then scroll down to "So you don't want to use WWW in front of the domain name"
    http://msmvps.com/blogs/acefekay/archive/2009/09/04/split-zone-or-no-split-zone-can-t-access-internal-website-with-external-
    name.aspx
    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
    This post is provided AS-IS with no warranties or guarantees and confers no rights.

  • Acquiring DNS server

    I am trying to replace a gen 1 time capsule with a gen 2 time capsule. Initially it wouldn't obtain dns server numbers from the cable modem. It reported no internet connection. I then copied the DNS server ID from the porfile of the older time capsule and entered it on the new one. After that the time capsule reports an internet connection, but won't actually resolve any urls. Reconnecting the old time capsule then allowed me to restore connectivity (with the new capsule unplugged.
    I think this is in part a cable modem problem, but sould be appreciative of any suggestions.
    thanks

    How are your DNS addresses served from your ISP? Dynamic or static? I would try resetting the TC and setting it up as new - if you can get an internet connection from your modem directly to your Mac then there should be no issues in assigning DNS to the new TC?

  • Dns server for specific domain

    Is there a way to define a dns server for a specific domain?
    I'm setting up a develop machine with an amp stack and i want to redirect all urls with a specific domain (i.e. project.dev) to 127.0.0.1.
    I've done this on OSX with dnsmasq configured in this way:
    # dnsmasq.conf
    address=/.dev/127.0.0.1
    listen-address=127.0.0.1
    port=35353
    and adding a dev file in /etc/resolver with this content
    # /etc/resolver/dev
    nameserver 127.0.0.1
    port 35353
    but this in arclinux with dhcpd doesn't work.
    I've tested dnsmasq with
    dig [email protected] -p 35353
    and it works (the address returned is 127.0.0.1) so the problem is the resolver.
    I've also tried either put into /etc/resov.conf.head this:
    # /etc/resolv.conf.head
    nameserver 127.0.0.1
    port 35353
    and configure dnsmasq with the default 53 port without luck.
    This is my /etc/resolv.conf
    # /etc/resolv.conf
    nameserver 127.0.0.1
    nameserver 192.168.0.1

    On linux you should simply run all dns request through one nameserver that forwards everything it doesn't understand. [Edit: You can do that with dnsmasq.] Another simple way to create a local developer zone would be to use wildcard_dns_proxy instead.
    Last edited by progandy (2015-03-03 17:20:29)

  • 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.

  • What is the .mac dns server ?

    Hello,
    I created website using iWeb and uploaded it to my .mac ( or now mobileme? ) account. The company that I bought the domain name from said that they need the dns server (nameserver) for my site? Does anybody know what this is or how I find it?
    In case it is relevant, here is the URL.
    http://web.mac.com/docrick/iWeb/EMSTPERM/Home.html
    Thanks a lot!

    What you need to tell your domain registrar is to go the DNS settings in your account and then change from the current settings and forward www using the CNAME option and then forward to web.me.com. That is all you need to do and they DO NOT need any further information than this.
    Do they offer the CNAME option? Ask them this next time. If not, then you can ask him to use framed web forwarding and to forward your domain name to web.me.com/username/sitename and that will work.
    If they are not helpful, then my advice would be to change and go somewhere else. It is easy to do and go somewhere like GoDaddy that do provide these services.

  • 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

  • Moving from Exchange 2007 to 2013 (leaving the DNS Server for it's own dedicated server)

    Hello! I am quite new to Exchange and Server management in general. I will do my best to explain my situation.
    I am looking to move my Exchange server off of our DNS server. When we installed them on the same server, we did not have the funds to buy 2 separate servers. I am told that it is best to separate the two. I have followed the Microsoft instructions for installing
    the prerequisites for Exchange 2013 on a 2012 R2 server, and i am at the point where it wants me to configure AD LDS. As I have active directory running on the current server, I was a little hesitant to just install it without understanding what i am doing.
    After the AD LDS is configured, I believe i can move forward with installing Exchange 2013 (all 3 roles will be hosted on the new server), export the mailboxes from 2007 server and import them into the new Exchange 2013 server. After 2013 is up and stable,
    I plan on removing 2007 from the old server (DNS server).
    What are my next steps after importing the mailboxes? Am i missing important details that I need to change or migrate?
    My biggest fear is that nothing works after the installation and moving the mailboxes over. For that case, it makes sense to keep 2007 installed as a fallback for when my installation fails and all i have lost is just my time :)
    Current Server:
    Windows Server 2008 Standard (64 bit)
    1. Roles: Active Directory, DNS, IIS
    2. Software: Exchange 2007
    New Server:
    Windows 2012 R2 Server
    1. Roles: ???
    1. Software to install: Exchange 2013
    Thank you for any help you can provide!

    These are good resources, but i am still caught up with the active directory issue.  Am I able to keep the old Domain/DNS/Active directory on it's current server and move Exchange 2007 off onto a new server (with Exchange 2013)?
    In the first example, he is moving everything (domain controller, exchange, users, etc) onto a different server and decommissioning it.I've been told that it would be better practice to keep the domain and exchange on 2 different servers. Is this true?
    I go to run commands like:
    .\setup /PrepareAD /OrganizationName: orgname /IAcceptExchangeServerLicenseTerms
    on the new exchange server, as a prerequisite and it doesnt recognize the command - even after following the steps before. Is this because the new server is not a domain controller? does it have to be? What are the best practices for setting up a server(s)
    with exchange + domain controller?
    Thanks for responding.

  • Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding [and I'm at my wit's end!]

    I originally posted this question to the community section and was advised to post it here.  Please bear with me as this will be a long post.  I'm including the scenarios involving this reoccurring issue, the trouble shooting steps I've already
    taken and the results of several diagnostic tools and logs.
    I have a Sony VAIOS VPCEBB33FM lap top since 2011.  I have had this issue on an off for a long time.  I'm at my wit's end.  Any new insights or suggestions would be greatly appreciated.
    Scenario Details
    1)  Some times it's on and off through out the day, sometimes it won't work all day, and once in a while it will work fine for the entire day.
    2)  I've had this issue across several wireless services, Clear Network accessed with WiMax, Library Wi-fi, Comcast cable internet using wireless router and Wi-fi, and Comcast Xfinity Wi-Fi, to name a few examples.
    3)  Other devices in the household or library will work with no problems such as my smart phone or my roommates' laptops or desktop computers.
    4) Once in a while,  the built-in wireless adapter is not found and I have to reinstall the driver.  Also the diagnostic tool has had to reset my adapter on an increasing basis.
    5)  I had my hard drive replaced in December 2014 and my system restored from the System Restore disks that came with it when I bought the laptop.  Even though I've been online on an infrequent basis it worked just fine for a while. Now that
    I've been online a bit more I'm having the same issues again.
    Below are my attempts at trouble shooting so far but I still have not been able to consistently resolve my DNS issues
     1) Restarting my adapter
     2) Turning off my laptop and removing the power supply for 5-10 minutes before turning it back on.
     3)  Using the IP Config in Command Prompt
         ipconfig /flushdns
         ipconfig /registerdns
         ipconfig /release
         ipconfig /renew
     4) Using the NetSh reset in Command Prompt and restarting my laptop
         netsh int ip reset c:\resetlog.txt
         netsh winsock reset
         ipconfig /flushdns
         [restart laptop]
     5)  Configuring the TCP/IP in several settings
        Select Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
        I have used the following settings:
           a) Obtain an DNS server address automatically
           b) OpenDNS
               208 67 222 222
               208 67 220 220
           c) Google DNS
               8 8 8 8
               8 8 4 4
     6) Updating the driver for my Intel Centrino(R) Advanced-N 6250 AGN and Intel Centrino(R) WIMAX 6250 from the Intel website previous having my laptop wiped clean in 2014.  It still did not resolve the issue.  My laptop
    manufacturer as not come up with an driver update for my adapter since 2010.  I haven't tried to update the adapter driver from Intel's website since having my laptop repaired due to the fact that Intel strongly recommending using the manufacturer's updates
    instead and frankly it didn't make much of a difference when I did it the first time.
     7) The last one I've tried as of today is going into Services and changing the start up type to automatic for the following:
           Computer Browser [changed from manual to automatic]
           DHCP Client [already set to automatic]
           DNS Client [already set to automatic]
           Network Connections [already set to automatic]
           Network Location Awareness [changed from manual to automatic]
           Remote Procedure Call (RPC) [already set to automatic]
           Server [already set to automatic]
           TCP/IP Netbios helper [already set to automatic]
           Workstation [already set to automatic]
    ...and I'm still having DNS issues.
    My only guessing are that my laptop came with a lemon adapter that needs to be replaced, some advanced setting(s) that I'm not aware off, or my firewall/anti-virus is interfering. I've used Symmantic Anti-virus and Firewall in the past and currently
    Avast Anti-Virus with Microsoft Network Firewall.  I've had DNS issues with both anti-virus/firewall set ups.
    Below are the results from the diagnostics and tests that I've ran.
    Windows Network Diagnostics
    Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding Detected Detected
    Contact your network administrator or Internet service provider (ISP) Completed
    Windows can't communicate with the device or resource (DNS server). The computer or service you are trying to reach might be...
    Details about network adapter diagnosis:
    Network adapter Wireless Network Connection driver information:
       Description . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6250 AGN
       Manufacturer  . . . . . . . . . : Intel Corporation
       Provider  . . . . . . . . . . . : Intel
       Version   . . . . . . . . . . . : 13.2.1.5
       Inf File Name . . . . . . . . . : C:\Windows\INF\oem17.inf
       Inf File Date . . . . . . . . . : Monday, June 14, 2010  9:05:44 AM
       Section Name  . . . . . . . . . : Install_MPCIEX_GEN_6250_AGN_2x2_HMC_WIN7_64_MOW
       Hardware ID . . . . . . . . . . : pci\ven_8086&dev_0087&subsys_13018086
       Instance Status Flags . . . . . : 0x180200a
       Device Manager Status Code  . . : 0
       IfType  . . . . . . . . . . . . : 71
       Physical Media Type . . . . . . : 9
    Informational Diagnostics Information (Wireless Connectivity)
    Details about wireless connectivity diagnosis:
    Information for connection being diagnosed
     Interface GUID: 70a0781d-6329-45e4-8d7c-34aeca294c39
     Interface name: Intel(R) Centrino(R) Advanced-N 6250 AGN
     Interface type: Native WiFi
    Connection incident diagnosed
     Auto Configuration ID: 1
     Connection ID: 1
    Connection status summary
     Connection started at: 2015-03-07 19:57:14-186
     Profile match: Success
     Pre-Association: Success
     Association: Success
     Security and Authentication: Success
    List of visible access point(s): 22 item(s) total, 22 item(s) displayed
            BSSID        BSS Type PHY    Signal(dB)    Chnl/freq    SSID
    60-02-92-C6-D3-E8    Infra     <unknown>    -62        11     HOME-C7D4-2.4
    60-02-92-A1-75-E0    Infra     <unknown>    -58        6     HOME-B917-2.4
    00-1D-D5-D5-34-F0    Infra     <unknown>    -73        6     HOME-34F2
    60-02-92-A1-75-E1    Infra     <unknown>    -58        6     (Unnamed Network)
    06-1D-D5-D5-34-F0    Infra     <unknown>    -78        6     xfinitywifi
    C4-27-95-C9-C4-2D    Infra     <unknown>    -57        1     HOME-C42D
    02-1D-D5-D5-34-F0    Infra     <unknown>    -74        6     (Unnamed Network)
    00-0D-97-07-E0-79    Infra     g    -75        6     (Unnamed Network)
    00-1D-CF-2A-44-C0    Infra     <unknown>    -86        6     HOME-44C2
    02-1D-CF-2A-44-C0    Infra     <unknown>    -86        6     (Unnamed Network)
    F8-E4-FB-3C-87-A2    Infra     <unknown>    -89        6     YVNM7
    06-1D-CF-2A-44-C0    Infra     <unknown>    -87        6     xfinitywifi
    0C-F8-93-7A-13-50    Infra     b    -87        6     PKennedy
    06-F8-93-7A-13-50    Infra     b    -89        6     xfinitywifi
    02-F8-93-7A-13-50    Infra     b    -87        6     (Unnamed Network)
    E0-88-5D-C8-A9-DC    Infra     <unknown>    -80        1     HOME-A9DC
    E2-88-5D-C8-A9-DD    Infra     <unknown>    -79        1     (Unnamed Network)
    16-CF-E2-43-0B-30    Infra     <unknown>    -88        1     xfinitywifi
    60-02-92-F0-A8-C0    Infra     <unknown>    -90        11     HOME-96A6-2.4
    60-02-92-C6-D3-E9    Infra     <unknown>    -63        11     (Unnamed Network)
    02-1D-D4-EB-87-00    Infra     <unknown>    -88        11     (Unnamed Network)
    06-1D-D4-EB-87-00    Infra     <unknown>    -88        11     xfinitywifi
    Connection History
     Information for Auto Configuration ID 1
      List of visible networks: 13 item(s) total, 13 item(s) displayed
      BSS Type PHY    Security    Signal(RSSI)    Compatible    SSID
      Infra     <unknown>    Yes        63    Yes        HOME-C7D4-2.4
      Infra     <unknown>    Yes        70    Yes        HOME-B917-2.4
      Infra     <unknown>    Yes        43    Yes        HOME-34F2
      Infra     <unknown>    Yes        70    Yes        (Unnamed Network)
      Infra     <unknown>    No        40    Yes        xfinitywifi
      Infra     <unknown>    Yes        71    Yes        HOME-C42D
      Infra     g    No        43    Yes        (Unnamed Network)
      Infra     <unknown>    Yes        28    Yes        HOME-44C2
      Infra     <unknown>    Yes        20    Yes        YVNM7
      Infra     b    Yes        21    Yes        PKennedy
      Infra     <unknown>    Yes        33    Yes        HOME-A9DC
      Infra     <unknown>    Yes        35    Yes        (Unnamed Network)
      Infra     <unknown>    Yes        16    Yes        HOME-96A6-2.4
      List of preferred networks: 3 item(s)
       Profile: xfinitywifi
        SSID: xfinitywifi
        SSID length: 11
        Connection mode: Infra
        Security: No
        Set by group policy: No
        Connect even if network is not broadcasting: No
        Connectable: Yes
       Profile: HTC Portable Hotspot 9F50
        SSID: HTC Portable Hotspot 9F50
        SSID length: 25
        Connection mode: Infra
        Security: Yes
        Set by group policy: No
        Connect even if network is not broadcasting: No
        Connectable: No
         Reason: 0x00028002
       Profile: belkin.332
        SSID: belkin.332
        SSID length: 10
        Connection mode: Infra
        Security: Yes
        Set by group policy: No
        Connect even if network is not broadcasting: No
        Connectable: No
         Reason: 0x00028002
     Information for Connection ID 1
     Connection started at: 2015-03-07 19:57:14-186
      Auto Configuration ID: 1
      Profile: xfinitywifi
      SSID: xfinitywifi
      SSID length: 11
      Connection mode: Infra
      Security: No
      Pre-Association and Association
       Connectivity settings provided by hardware manufacturer (IHV): No
       Security settings provided by hardware manufacturer (IHV): No
       Profile matches network requirements: Success
       Pre-association status: Success
       Association status: Success
        Last AP:  06-1d-d5-d5-34-f0
      Security and Authentication
       Configured security type: Open
       Configured encryption type: None
       802.1X protocol: No
       Key exchange initiated: Yes
        Unicast key received: No
        Multicast key received: No
       Number of security packets received: 0
       Number of security packets sent: 0
       Security attempt status: Success
     Connectivity
       Packet statistics
        Ndis Rx: 2068
        Ndis Tx: 2543
        Unicast decrypt success: 0
        Multicast decrypt success: 0
        Unicast decrypt failure: 0
        Multicast decrypt failure: 0
        Rx success: 3954
        Rx failure: 0
        Tx success: 537
        Tx failure: 4
        Tx retry: 2
        Tx multiple retry: 2
        Tx max lifetime exceeded: 0
        Tx ACK failure: 18
       Roaming history: 0 item(s)
    InformationalDiagnostics Information (Wireless Connectivity)
    Details about wireless connectivity diagnosis:
    For complete information about this session see the wireless connectivity information event.
    Helper Class: Auto Configuration
     Initialize status: Success
    Information for connection being diagnosed
     Interface GUID: 70a0781d-6329-45e4-8d7c-34aeca294c39
     Interface name: Intel(R) Centrino(R) Advanced-N 6250 AGN
     Interface type: Native WiFi
    Result of diagnosis: There may be problem
     Network Connection details from Command Prompt  (some info hidden for security reasons)
    Connection-specific DNS Suffix:
    Description: Intel(R) Centrino(R) Advanced-N 6250 AGN
    Physical Address: ‎00-23-15-54-19-B8
    DHCP Enabled: Yes
    IPv4 Address: 192.168.X.XX
    IPv4 Subnet Mask: 255.255.XX.X
    Lease Obtained: Saturday, March 07, 2015 7:57:14 PM
    Lease Expires: Saturday, March 07, 2015 8:24:44 PM
    IPv4 Default Gateway: 192.168.X.X
    IPv4 DHCP Server: 192.168.X.X
    IPv4 DNS Servers: 75.75.75.75, 75.75.76.76
    IPv4 WINS Server:
    NetBIOS over Tcpip Enabled: Yes
    Link-local IPv6 Address: fe80::b8de:3ac9:e166:XXX%XX
    IPv6 Default Gateway:
    IPv6 DNS Server:
    Results of Ping and Trace Route in Command Prompt
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    C:\Windows\system32>ping 127.0.0.1
    Pinging 127.0.0.1 with 32 bytes of data:
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Ping statistics for 127.0.0.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    C:\Windows\system32>ping www.youtube.com
    Pinging youtube-ui.l.google.com [173.194.121.6] with 32 bytes of data:
    Reply from 173.194.121.6: bytes=32 time=24ms TTL=55
    Reply from 173.194.121.6: bytes=32 time=19ms TTL=55
    Request timed out.
    Request timed out.
    Ping statistics for 173.194.121.6:
        Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 19ms, Maximum = 24ms, Average = 21ms
    C:\Windows\system32>ping 74.125.239.34
    Pinging 74.125.239.34 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Reply from 74.125.239.34: bytes=32 time=3286ms TTL=50
    Request timed out.
    Ping statistics for 74.125.239.34:
        Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 3286ms, Maximum = 3286ms, Average = 3286ms
    C:\Windows\system32>ping www.hotmail.com
    Pinging dispatch.kahuna.glbdns2.microsoft.com [65.55.157.204] with 32 bytes of data:
    Reply from 65.55.157.204: bytes=32 time=111ms TTL=237
    Request timed out.
    Request timed out.
    Reply from 65.55.157.204: bytes=32 time=1537ms TTL=237
    Ping statistics for 65.55.157.204:
        Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 111ms, Maximum = 1537ms, Average = 824ms
    C:\Windows\system32>ping 207.46.11.236
    Pinging 207.46.11.236 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 207.46.11.236:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    C:\Windows\system32>tracert www.youtube.com
    Tracing route to youtube-ui.l.google.com [173.194.121.5]
    over a maximum of 30 hops:
      1    19 ms    13 ms    17 ms  xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
      2    13 ms    13 ms    27 ms  ae-14-32767-ar03.newcastle.de.panjde.comcast.net [68.85.192.205]
      3    20 ms    26 ms    21 ms  he-5-10-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.249]
      4    18 ms    34 ms    22 ms  he-0-13-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.86.50]
      5    19 ms    18 ms    18 ms  50-248-116-190-static.hfc.comcastbusiness.net [50.248.116.190]
      6    35 ms    18 ms    18 ms  209.85.249.217
      7    21 ms    19 ms    19 ms  72.14.233.93
      8     *        *        *     Request timed out.
      9     *     2509 ms   677 ms  iad23s25-in-f5.1e100.net [173.194.121.5]
    Trace complete.
    C:\Windows\system32>tracert 74.125.239.34
    Tracing route to nuq04s19-in-f2.1e100.net [74.125.239.34]
    over a maximum of 30 hops:
      1    54 ms    23 ms    12 ms  xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
      2    22 ms    19 ms    17 ms  ae-14-32767-ar03.newcastle.de.panjde.comcast.net[68.85.192.205]
      3    19 ms    19 ms    18 ms  he-5-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.166.121]
      4    18 ms    18 ms    18 ms  he-0-15-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.85.74]
      5    19 ms    18 ms    22 ms  50-248-116-190-static.hfc.comcastbusiness.net [50.248.116.190]
      6    22 ms    36 ms    19 ms  209.85.249.217
      7    26 ms    23 ms    25 ms  209.85.143.112
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10   972 ms     *        *     216.239.51.97
     11   148 ms    97 ms    95 ms  216.239.46.241
     12   324 ms   130 ms   432 ms  209.85.246.252
     13     *        *        *     Request timed out.
     14  1403 ms   101 ms   126 ms  nuq04s19-in-f2.1e100.net [74.125.239.34]
    Trace complete.
    C:\Windows\system32>tracert www.hotmail.com
    Tracing route to dispatch.kahuna.glbdns2.microsoft.com [65.55.157.144]
    over a maximum of 30 hops:
      1    13 ms    13 ms    25 ms  xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
      2    13 ms    15 ms    13 ms  ae-14-32767-ar03.newcastle.de.panjde.comcast.net[68.85.192.205]
      3    20 ms    19 ms    17 ms  he-5-13-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.145]
      4    17 ms    20 ms    20 ms  he-0-13-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.86.50]
      5    17 ms    18 ms    38 ms  as8075-2-c.ashburn.va.ibone.comcast.net [173.167.58.82]
      6    18 ms    18 ms    36 ms  ae4-0.ash-96cbe-1a.ntwk.msn.net [207.46.36.172]
      7     *        *        *     Request timed out.
      8     *     2191 ms    35 ms  ae0-0.atb-96cbe-1b.ntwk.msn.net [191.234.81.167]
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11    86 ms    84 ms    84 ms  ae4-0.lax-96cbe-1a.ntwk.msn.net [191.234.83.150]
     12    86 ms    86 ms    87 ms  ae9-0.by2-96c-1a.ntwk.msn.net [207.46.42.176]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17    87 ms    84 ms    85 ms  origin.by173w.bay173.mail.live.com [65.55.157.144]
    Trace complete.
    C:\Users\C.Cunningham>tracert 207.46.11.236
    Tracing route to origin.by181w.bay181.mail.live.com [207.46.11.236]
    over a maximum of 30 hops:
      1    16 ms    16 ms    19 ms  xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
      2    18 ms    13 ms    13 ms  ae-14-32767-ar03.newcastle.de.panjde.comcast.net[68.85.192.205]
      3    21 ms    19 ms    21 ms  he-5-12-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.141]
      4    18 ms    21 ms    18 ms  he-0-13-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.86.50]
      5     *        *        *     Request timed out.
      6     *        *        *     Request timed out.
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20     *        *        *     Request timed out.
     21     *        *        *     Request timed out.
     22     *        *        *     Request timed out.
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *        *        *     Request timed out.
     26     *        *        *     Request timed out.
     27     *        *        *     Request timed out.
     28     *        *        *     Request timed out.
     29     *        *        *     Request timed out.
     30     *        *        *     Request timed out.
    Trace complete.
    Results of Intel WiFi Manual Diagnostics
    Test Name                 Test Result   Test Summary
    Hardware Test           Passed        Wireless Hardware is enabled
    Driver Test                 Passed        Diver is loaded. NETwNs64 Version 13.3.0.24
    Radio Test                  Passed       Radio is ON
    Scan Test                   Passed       There are 25 Networks available to connect
    Association Test        Passed       Associated
    Authentication Test   Passed       Authenticated
    Signal Test                Passed       Signal Quality: Poor
    Ping Test                  Failed          No Reponse: default gateway, DHCP server
    I hope this information is enough to get to the root of this problem once and for all.  Please let me know if you any other information such as event logs or statistics. 
    Thanks in advance.

    Results of Intel WiFi Event View Log (I deleted some lines since there were basically repeats of the same messages)
    #Event  Source  Time     
    Error Severity    Domain               
    User      Description
    45           EvtEngine           
    3/8/2015 20:40  Success               
    Connection         SYSTEM               
    iAMT - Failed to read Windows Events Log
    46           S24EvMon          
    3/8/2015 20:41  Information       
    AppDriver          
    SYSTEM               
    Getting List of adapters.
    47           S24EvMon          
    3/8/2015 20:41  Information       
    AppDriver          
    SYSTEM               
    Intel adapter(s) found.
    156         S24EvMon          
    3/8/2015 20:47  Information       
    Driver    SYSTEM               
    AddToExclude 06:1d:d5:d5:34:f0 xfinitywifi 6 WEV_EXCLUDE_LIST_REASON_802_11_AUTH_FAILURE
    157         S24EvMon          
    3/8/2015 20:47  Information       
    Driver    SYSTEM               
    ATC 06:1d:cf:2a:44:c0 xfinitywifi 6 RSSI=-88
    158         S24EvMon          
    3/8/2015 20:47  Error     
    Driver    SYSTEM               
    AssociationFailure 06:1d:cf:2a:44:c0 xfinitywifi 6 CNCT_GENERAL_FAILURE
    159         S24EvMon          
    3/8/2015 20:47  Information       
    Driver    SYSTEM               
    AddToExclude 06:1d:cf:2a:44:c0 xfinitywifi 6 WEV_EXCLUDE_LIST_REASON_802_11_ASSOC_FAILURE
    160         S24EvMon          
    3/8/2015 20:47  Information       
    Driver    SYSTEM               
    ATC 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-79
    161         S24EvMon          
    3/8/2015 20:47  Success               
    Driver    SYSTEM               
    RxAuthSuccess 06:1d:d5:d5:34:f0 6
    162         S24EvMon          
    3/8/2015 20:47  Success               
    Driver    SYSTEM               
    RxAssocResp 06:1d:d5:d5:34:f0 6 -77
    163         S24EvMon          
    3/8/2015 20:49  Information       
    TCP/IP  SYSTEM               
    VoIP: Got link down - deleting flows .
    164         S24EvMon          
    3/8/2015 20:49  Information       
    Driver    SYSTEM               
    ATC 06:1d:d4:eb:87:00 xfinitywifi 11 RSSI=-88
    165         S24EvMon          
    3/8/2015 20:49  Error     
    Driver    SYSTEM               
    AssociationFailure 06:1d:d4:eb:87:00 xfinitywifi 11 CNCT_GENERAL_FAILURE
    166         S24EvMon          
    3/8/2015 20:49  Information       
    Driver    SYSTEM               
    AddToExclude 06:1d:d4:eb:87:00 xfinitywifi 11 WEV_EXCLUDE_LIST_REASON_802_11_ASSOC_FAILURE
    167         S24EvMon          
    3/8/2015 20:49  Information       
    Driver    SYSTEM               
    ATC 06:1d:d4:eb:87:00 xfinitywifi 11 RSSI=-89
    168         S24EvMon          
    3/8/2015 20:49  Error     
    Driver    SYSTEM               
    AssociationFailure 06:1d:d4:eb:87:00 xfinitywifi 11 CNCT_GENERAL_FAILURE
    169         S24EvMon          
    3/8/2015 20:49  Information       
    Driver    SYSTEM               
    AddToExclude 06:1d:d4:eb:87:00 xfinitywifi 11 WEV_EXCLUDE_LIST_REASON_802_11_ASSOC_FAILURE
    170         S24EvMon          
    3/8/2015 20:49  Information       
    Driver    SYSTEM               
    ATC 06:1d:d4:eb:87:00 xfinitywifi 11 RSSI=-90
    171         S24EvMon          
    3/8/2015 20:49  Error     
    Driver    SYSTEM               
    AssociationFailure 06:1d:d4:eb:87:00 xfinitywifi 11 CNCT_GENERAL_FAILURE
    172         S24EvMon          
    3/8/2015 20:49  Information       
    Driver    SYSTEM               
    ATC 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-82
    173         S24EvMon          
    3/8/2015 20:49  Success               
    Driver    SYSTEM               
    RxAuthSuccess 06:1d:d5:d5:34:f0 6
    174         S24EvMon          
    3/8/2015 20:49  Success               
    Driver    SYSTEM               
    RxAssocResp 06:1d:d5:d5:34:f0 6 -81
    175         S24EvMon          
    3/8/2015 20:50  Information       
    Driver    SYSTEM               
    AddToExclude 06:1d:d5:d5:34:f0 xfinitywifi 6 WEV_EXCLUDE_LIST_REASON_802_11_AUTH_FAILURE
    176         S24EvMon          
    3/8/2015 20:50  Information       
    Driver    SYSTEM               
    ATC 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-79
    177         S24EvMon          
    3/8/2015 20:50  Success               
    Driver    SYSTEM               
    RxAuthSuccess 06:1d:d5:d5:34:f0 6
    178         S24EvMon          
    3/8/2015 20:50  Success               
    Driver    SYSTEM               
    RxAssocResp 06:1d:d5:d5:34:f0 6 -80
    179         S24EvMon          
    3/8/2015 21:03  Information       
    Driver    SYSTEM               
    RoamTrigger 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-81 MisBcn=8 RSSITh=-85 Roam Other Reason
    186         S24EvMon          
    3/8/2015 21:21  Information       
    General               
    SYSTEM               
    DeviceIoCtrlS24NDIS: (2) Failed to send OID 0xff100055 to driver. Error - 31
    187        
    S24EvMon          
    3/8/2015 21:21  Information       
    General               
    SYSTEM               
    DeviceIoCtrlS24NDIS - Dot11ExtNicSpecificExtension failed (31)

Maybe you are looking for