Is DNS down?

It seems that I am unable to use or ping my DHCP assigned DNS servers 213.120.234.58 and 213.120.234.26, it maybe that these servers are down or there is a routing problem from my local exchange (Ascot) to these servers.  Currently I cannot even do a nslookup bt.com but I can get arround if I know the correct IP address.
Of course I have contacted BT support and they have gone through their standard support flowchart and suggested that I put a pin in the side of the router and do a factory reset.  Actually I need to go up the road and put a pin in the side of the exchange and to a factory reset on the network.
This seems to be an intermittent thing, I have not kept detailed track of this but I think it seems to happen on Friday late afternoons.  
Is anyone else having this problem?
Are there alternate DNS servers that I can use?
On a side note it is ironic that if you download the BT desktop diagnostic tool (http://pbttbc.bt.motive.com/motivedocs/discus/BTBB​DesktopHelpInstall.exe) and try to install this, the install then needs to go on-line to get more components before you can use it....  So in order to use this you have to have it pre-installed before you have an issue....  Bizarre!
Thanks in advance,
/AGeezer

AGeezer wrote:
It seems that I am unable to use or ping my DHCP assigned DNS servers 213.120.234.58 and 213.120.234.26, it maybe that these servers are down or there is a routing problem from my local exchange (Ascot) to these servers.  Currently I cannot even do a nslookup bt.com but I can get arround if I know the correct IP address.
Of course I have contacted BT support and they have gone through their standard support flowchart and suggested that I put a pin in the side of the router and do a factory reset.  Actually I need to go up the road and put a pin in the side of the exchange and to a factory reset on the network.
This seems to be an intermittent thing, I have not kept detailed track of this but I think it seems to happen on Friday late afternoons.  
Is anyone else having this problem?
Are there alternate DNS servers that I can use?
On a side note it is ironic that if you download the BT desktop diagnostic tool (http://pbttbc.bt.motive.com/motivedocs/discus/BTBB​DesktopHelpInstall.exe) and try to install this, the install then needs to go on-line to get more components before you can use it....  So in order to use this you have to have it pre-installed before you have an issue....  Bizarre!
Thanks in advance,
/AGeezer
Hi.
Pimg is very often blocked, so doesn't specifically help in this case.
I assume that you can access websites at the moment, and frankly if "DNS" was down, or certain ones it could affect many 10s of 1000s of people - and hence there would be a lot of reports.
But if the problem appears to be around the same sort of time each week, then that seems like something else, possibly local to you as uou intimated - perhaps some form of congestion. As there was racing at Ascot this past week, maybe that has something to do with it - though wouldn't usually affect other weeks.
http://www.andyweb.co.uk/shortcuts
http://www.andyweb.co.uk/pictures

Similar Messages

  • Network Solutions DNS down...

    Network Solutions DNS is down again. I'm considering options. Anyone
    have any suggestions for good DNS providers? Somebody that is more
    reliable?
    Ken

    On Tue, 22 Oct 2013 17:31:55 GMT, Jim Henderson
    <[email protected]> wrote:
    >On Tue, 22 Oct 2013 17:17:02 +0000, KeN Etter wrote:
    >
    >> On Tue, 22 Oct 2013 16:54:30 GMT, KeN Etter
    >> <[email protected]> wrote:
    >>
    >>>Network Solutions DNS is down again. I'm considering options. Anyone
    >>>have any suggestions for good DNS providers? Somebody that is more
    >>>reliable?
    >>
    >> Just to clarify...I host all my own sites. I just need reliable Domain
    >> Registration and DNS.
    >>
    >> Ken
    >
    >dyn.com seems to be pretty reasonable and good. I've been using the free
    >dyndns address for a few years now.
    >
    >Jim
    I'll check on it.

  • DNS down, but com.apple.SystemStarter says "available"!

    After a power outage, many systems are having problems with DNS.  I booted an iMac and in the log I found:
    12-05-29 8:49:49 AM
    com.apple.SystemStarter[39]
    Checking if DNS is available.
    12-05-29 8:49:52 AM
    com.apple.SystemStarter[39]
    DNS seems to be available or we timedout while waiting for DNS. Starting services anyway
    12-05-29 9:45:06 AM
    com.apple.SystemStarter[42]
    Checking if DNS is available.
    12-05-29 9:45:08 AM
    com.apple.SystemStarter[42]
    DNS seems to be available or we timedout while waiting for DNS. Starting services anyway
    My guess is that the message was meant to say "unavailable".   Can anyone clarify this? 

    How are you connected?  Do you have a router that is supposed to supply DNS?  Or are you directly connected?

  • Default DNS grayed out in Network Preferences

    In my Network Preferences, my router address/gateeway is listed twice as a default DNS. Maybe once from Tiger and once more from Leopard?
    This is probably a Verizon thing
    The problem is that they are grayed out and cannot be removed by normal means AFAIK.
    My console reports that the same DNS is repeated - a minor but annoying item.
    It there any reason for me not to simply comment out one of these pesky DNS in the
    /etc/resolv.conf
    file?
    I have already added two more OpenDNS in the Network Preferences with no problem, and they properly show up in the resolv.conf file as 1 and 2, with the default DNS being 3 and 4.
    Why are these default DNS grayed out in Network Preferences?
    How did they get there in the first place?
    Is there a proper place to remove them or at least un-gray them?
    Will commenting out or removing one of the dupes in the resolv.conf file hose anything?

    xnav wrote:
    Have you got something like 'local DNS caching' turned on in the Verizon? Commenting out of .conf may not stick, I think DHCP will just rebuild it.
    I think it's the Verizon router offering the router IP as a fake DNS, which then passes onto the real Verizon DNS down the pipe. Verizon has one of those DNS that trap 404's and offer assistance.
    I think that Leopard looks for 2 DNS minimum and therefore takes the Verizon router number 2 times. It's the first time I have seen a router use its own IP as a DNS.
    When I switch to the Cable system, the duplicate fake DNS get replaced with the real cable DNS almost immediately, so you are right in that it is dynamic, and editing the conf file would do nothing.
    At least I now understand what's happening. It has to be that Leopard asks for 2 DNS or that Verizon router offers the same IP twice.
    I will have to look into the Verizon router a bit more to see if I can do something

  • Server 2012 X64 R2 DNS Server keeps shutting down after inplace upgrade from Server 2012 X64

    Hi,
    ever since upgrading from Server 2012 X64 to Server 2012 R2 X64 my dns server keeps shutting down every several minutes before having to do a restart.  When viewing the event log this is all I see..
    The DNS Server service terminated unexpectedly.  It has done this 497 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
    if I look in the Application Error Log,  I will also find the following:
    Faulting application name: dns.exe, version: 6.3.9600.17031, time stamp: 0x530871fb
    Faulting module name: dns.exe, version: 6.3.9600.17031, time stamp: 0x530871fb
    Exception code: 0xc0000005
    Fault offset: 0x000000000010b0e0
    Faulting process id: 0x1740
    Faulting application start time: 0x01cf531b2e3a7f5e
    Faulting application path: C:\Windows\system32\dns.exe
    Faulting module path: C:\Windows\system32\dns.exe
    Report Id: 90a4ab37-bf0e-11e3-9446-003048df3f03
    Faulting package full name:
    Faulting package-relative application ID:
    I have tried removing and then reinstalling the DNS Server role, but the same situation occurs..
    thanks,

    Hi,
    I'm going crazy,  I've upgraded my Server 2012 Standard to Server 2012 R2 Standard and now my DNS server keeps crashing since the in place upgrade.  I have finally narrowed it down to it only crashes after several minutes if I load the data from
    a file instead of the registry.  As a test I:
    -1- killed all my dns data,
    -2- uninstalled the dns server role
    -3- deleted the /windows/system32/dns directory
    -4- reinstalled the DNS server role
    -5- used the wizard to create a DNS server and a forward zone.
    everything works okay, no crashes,  then I change the advanced propertied of the DNS server to load from file, restart the DNS server and once again it crashes every 2 minutes..
    Please help,  this is killing me..
    thanks in advance..

  • External DNS Nightmare - Site is Down - Please Help!

    Can't figure this out, I did everything as the help file stated.
    The site is completely down as of now.
    domain:
    www.elitemmagym.com
    A records created at registrar for:
    www.elitemmagym.com
    elitemmagy.com
    IP pointed on both to 192.150.2.140 (north america)
    see screenshot:
    http://cl.ly/2X2z1r430H3S0T430z2a
    Then setup domain in BC admin, chose external DNS:
    http://cl.ly/0e0W2m2r322d350m191x
    It's been over an hour.
    The site was completely down within seconds of making these changes. It was up and functioning on the old server before this.
    Pinging and tracerouting the domain name shows that no record exists:
    http://cl.ly/010A0K3P0p0W2F3I2j0K
    HELP!

    Is support off on Friday nights?

  • Secondary DNS failing to redirect clients when Primary DNS goes down

    I have a single domain with two Windows 2008 servers, DC1 (physical) and DC2 (virtual).  Both servers run DNS and are GC servers, and the entire domain is on the same subnet (192.168.0.x). 
    All clients on the network are configured to use DC1 as primary DNS, DC2 as secondary DNS. 
    DHCP is enabled only on DC1.  (This might be part of the issue, not sure).
    The problem is that when DC1 goes down for a reboot or repair, we lose access to the internet from our clients.  Trying to pull up any website results in a "Page cannot be displayed" error.  DC2 is available during this time and can be
    pinged from any client but does not resolve DNS requests, even if I specify it as the primary DNS server on one of my workstations.  However I can log on to DC2 locally and browse the web. 
    Here are the results of a DCdiag /dnsall from DC2 (I bolded areas of concern):
    Directory Server Diagnosis
    Performing initial setup:
       * Connecting to directory service on server DC2.
       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=mydomain,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded
       Iterating through the sites
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=mydomain,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers
       Getting information for the server CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       Getting information for the server CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\DC2
          Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    Determining IP6 connectivity
    * Active Directory RPC Services Check
    ......................... DC2 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\DC2
          Test omitted by user request: Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Test omitted by user request: FrsEvent
          Test omitted by user request: DFSREvent
          Test omitted by user request: SysVolCheck
          Test omitted by user request: KccEvent
          Test omitted by user request: KnowsOfRoleHolders
          Test omitted by user request: MachineAccount
          Test omitted by user request: NCSecDesc
          Test omitted by user request: NetLogons
          Test omitted by user request: ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Test omitted by user request: Replications
          Test omitted by user request: RidManager
          Test omitted by user request: Services
          Test omitted by user request: SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: VerifyReferences
          Test omitted by user request: VerifyReplicas
          Starting test: DNS
    DNS Tests are running and not hung. Please wait a few minutes...
    See DNS test in enterprise tests section for results
    ......................... DC2 passed test DNS
       Running partition tests on : ForestDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : DomainDnsZones
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Schema
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : Configuration
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running partition tests on : mydomain
          Test omitted by user request: CheckSDRefDom
          Test omitted by user request: CrossRefValidation
       Running enterprise tests on : mydomain.com
          Starting test: DNS
    Test results for domain controllers:
     DC: DC2.mydomain.com
    Domain: mydomain.com
    TEST: Authentication (Auth)
    Authentication test: Successfully completed
    TEST: Basic (Basc)
                      Microsoftr Windows Serverr 2008 Standard 
    (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 [00000006] Intel(R) PRO/1000 MT Network Connection:
    MAC address is 00:0C:29:91:59:68
    IP Address is static
    IP address: 192.168.0.249
    DNS servers:
    192.168.0.105 (DC1.mydomain.com.) [Valid]
    127.0.0.1 (DC2) [Valid]
    The A host record(s) for this DC was found
    Warning: The AAAA record for this DC was not found
    [Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.) - mydomain.com]
                      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 Information:
    192.168.0.105 (DC1.mydomain.com.) [Valid]
    192.168.0.7 (<name unavailable>) [Invalid (unreachable)]
     Error: Forwarders list has invalid forwarder: 192.168.0.7 (<name unavailable>)
    TEST: Delegations (Del)
    Delegation information for the zone: mydomain.com.
    Delegated domain name: _msdcs.mydomain.com.
    DNS server: DC1.mydomain.com. IP:192.168.0.105 [Valid]
    TEST: Dynamic update (Dyn)
    Test record _dcdiag_test_record added successfully in zone mydomain.com
    Test record _dcdiag_test_record deleted successfully in zone mydomain.com
    TEST: Records registration (RReg)
    Network Adapter
    [00000006] Intel(R) PRO/1000 MT Network Connection:
    Matching CNAME record found at DNS server 192.168.0.105:
    a32fcfbd-16bb-4697-a23d-20fc3b8c274c._msdcs.mydomain.com
    Matching A record found at DNS server 192.168.0.105:
    DC2.mydomain.com
    Warning:
    Missing AAAA record at DNS server 192.168.0.105:
    DC2.mydomain.com
    [Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
    Matching  SRV record found at DNS server 192.168.0.105:
    _ldap._tcp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _ldap._tcp.ac09921d-4553-475e-b25c-059742ac0552.domains._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _kerberos._tcp.dc._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _ldap._tcp.dc._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _kerberos._tcp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _kerberos._udp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _kpasswd._tcp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _ldap._tcp.Default-First-Site-Name._sites.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _kerberos._tcp.Default-First-Site-Name._sites.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _ldap._tcp.gc._msdcs.mydomain.com
    Matching A record found at DNS server 192.168.0.105:
    gc._msdcs.mydomain.com
    Warning:
    Missing AAAA record at DNS server 192.168.0.105:
    gc._msdcs.mydomain.com
    [Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
    Matching  SRV record found at DNS server 192.168.0.105:
    _gc._tcp.Default-First-Site-Name._sites.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.105:
    _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.mydomain.com
    Matching CNAME record found at DNS server 192.168.0.249:
            a32fcfbd-16bb-4697-a23d-20fc3b8c274c._msdcs.mydomain.com
    Matching A record found at DNS server 192.168.0.249:
    DC2.mydomain.com
    Warning:
    Missing AAAA record at DNS server 192.168.0.249:
    DC2.mydomain.com
    [Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
    Matching  SRV record found at DNS server 192.168.0.249:
    _ldap._tcp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _ldap._tcp.ac09921d-4553-475e-b25c-059742ac0552.domains._msdcs.mydomain.com
                 Matching 
    SRV record found at DNS server 192.168.0.249:
    _kerberos._tcp.dc._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _ldap._tcp.dc._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _kerberos._tcp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _kerberos._udp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _kpasswd._tcp.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _ldap._tcp.Default-First-Site-Name._sites.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
               Matching 
    SRV record found at DNS server 192.168.0.249:
    _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _kerberos._tcp.Default-First-Site-Name._sites.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _ldap._tcp.gc._msdcs.mydomain.com
    Matching A record found at DNS server 192.168.0.249:
    gc._msdcs.mydomain.com
    Warning:
    Missing AAAA record at DNS server 192.168.0.249:
    gc._msdcs.mydomain.com
    [Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
    Matching  SRV record found at DNS server 192.168.0.249:
    _gc._tcp.Default-First-Site-Name._sites.mydomain.com
    Matching  SRV record found at DNS server 192.168.0.249:
    _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.mydomain.com
    Warning: Record Registrations not found in some network adapters
    TEST: External name resolution (Ext)
    Internet name www.microsoft.com was resolved successfully
    Summary of test results for DNS servers used by the above domain
    controllers:
    DNS server: 192.168.0.7 (<name unavailable>)
    1 test failure on this DNS server
    PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.0.7              
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
    DNS server: 192.168.0.105 (DC1.mydomain.com.)
    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.mydomain.com. is operational on IP 192.168.0.105
    DNS server: 192.168.0.249 (DC2)
    All tests passed on this DNS server
    Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
    Summary of DNS test results:
    Auth Basc Forw Del  Dyn  RReg Ext
    Domain: mydomain.com
    DC2                      
    PASS WARN FAIL PASS PASS WARN PASS
    ......................... mydomain.com failed test DNS
          Test omitted by user request: LocatorCheck
          Test omitted by user request: Intersite

    Looks like it may be trying to forward to a machine that's down (DC1 and another 192.168.0.7) and root hints aren't available.
    Check out this article:
    http://technet.microsoft.com/en-us/library/ff807391(v=ws.10).aspx
    See if you can enable DNS access through the firewall to the Internet if it's not already available.  Try to match whatever forwarder settings are on DC1, or remove them entirely and let the server resolve DNS from Internet root servers.  Alternativly,
    you could change your forwarder to a public DNS server you have access to, your ISP should supply this or you could test with something common like 4.2.2.2.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • Severe Site Slow-Down with multiple DNS/Sites

    Alright.. this is a bit of a strange situation, any help is appreciated because I'm pretty much out of troubleshooting options.
    Mac OS X Server hosting a few important sites and then several "redirect" sites.
    - A PHP/MySQL system
    - 2 normal PHP/MySQL websites
    - 8 Redirects (domain.bz, domain.biz, domain.name, etc..)
    The redirects are set up like so:
    - A DNS entry with a "www" alias pointing to the local machine.
    - A site with a .html file containing a meta-refresh to domain.com
    The Redirects work just fine when they are enabled, www.domain.biz goes to www.domain.com, etc.. however, the 3 sites that run on the server experience severe slow-down to the point of not even loading.
    Normally the sites are blazingly fast..
    Anyway, if the redirect site entries are disabled, the slow-down disappears.
    As an added oddity.. if Safari is experiencing the slowdown, but I cancel the site load.. the site pulls up missing images/css in varying degrees, depending on when I cancel, so it's like something is "hanging".
    There's nothing apparent in the error logs other than a report that 'there is a mismatch between the domain name and reverse DNS' etc.. 'may cause some services to not work properly'.

    Nevermind, I found the problem.
    The performance cache was enabled for the redirect sites.

  • Nslookup: DNS request timed out. time out was 2 seconds. (When the primary DNS is down)

    Hi All,
    I have set up 2 Windows Server 2012 domain controllers (DCA & DCB). DCA points at DCB as the primary DNS, and itself as the alternate DNS. DCB points at DCA as the primary DNS, and itself as the alternate DNS.
    When both DCs are running and if I do an nslookup on DCA: The result is as follows:
    Default Server: dcb.testdomain.com
    Address: 30.30.30.2
    nslookup on DCB:
    Default Server: dca.testdomain.com
    Address: 30.30.30.1
    Client PC (Windows 7 Pro):
    1st DNS : 30.30.30.31
    Alternate DNS: 30.30.30.32
    nslookup on the client PC
    Default Server: dca.testdomain.com
    Address: 30.30.30.1
    Up to here everything is fine. Now if I turn off DCA, and do an nslookup, the result is as follows:
    DCB nslookup:
    DNS request timed out.
           time out was 2 seconds.
    Default Server Unknown
    Address: 30.30.30.31
    Client PC nslookup:
    DNS request timed out.
           time out was 2 seconds.
    Default Server Unknown
    Address: 30.30.30.31
    I waited for more than 15 minutes an tried again, it didn't help.
    I have been reading a few similar posts on this matter, but couldn't find the answer.
    I would  expected it to display the DCB when I do an nslookup.
    Question 1: Shouldn't that display DCB rather than displaying a time out message when I do nslookup?
    Question 2: The fact that it displays a time out message, does it mean that more configuration needs to be done? If so please kindly advice what needs to be done. 
    I did an ipconfig /displaydns command. I realized that the order of DNS have changed on both DCB and the Client PC:
    Now, they both display DCB on the top of the list, whereas they were displaying DCA on the top of the list prior to the shut down.
    Question 3: Does it mean that the Client PC now knows that the 1st DNS is down and so it's using the 2nd DNS?
    If so, why does the nslookup display the time out message?
    Question 4: Is it possible to configure either of DNS Server or the DNS client, so it displays the 2nd DNS when the first DNS is not accessible and when I do nslookup?
    Thank you for. 

    Hi Ton_2013,
    Based on my understanding, the issue we are experiencing is that: when the primary DNS server is down, the result of the tool Nslookup is to diaplay the time out message at first. Right?
    Based on my knowledge, timed out message is means that the server did not respond to a request after a certain amount of time and a certain number of retries. Because the primary DNS server is down, it can't respond to this request and time is out. When
    the primary DNS server can't respond, the secondary DNS server works to ensure effective work. And the order is changed as you said.
    As to the reason why the result is still the same even when the order has changed, we can try to use Network Monitor to capture network traffic and view and analyze it to find the cause. And the cause may be the cache. For your information, please refer
    to the following link to download the tool Network Monitor:
    http://www.microsoft.com/en-hk/download/details.aspx?id=4865
    Regards,
    Lany Zhang

  • DSL Down - Looks Like a DNS Issue

    Hi Everyone,
    My DSL service has been down for 36 hours now and while Verizon is looking into the issue, I'd like to see if this community has any ideas as to what's going on.  Here's the story:
    My Internet access went down at midnight two nights ago.  I have two computers and both lost their connection, so I'm confident that it's not an issue with either computer.  I have an Actiontec modem/wireless router from Verizon.  I have rebooted the modem, which usually resolves any issues, but in this case it didn't help.  When I do an ipconfig, the DNS Suffix shows as domain_not_set.invalid, which I don't believe I've ever seen before.  I'm unable to ping any sites and nslookup reports DNS failures.
    Verizon is sending me a new modem, but I tried using my old Westell modem from Verizon and I'm seeing the exact same issues, so I'm thinking it's not a modem issue.
    Verizon has tested my line multiple times and says everything seems fine.  The issue has now been escalated to their central office to see if there is an issue there.
    Since Verizon hasn't been all that helpful to date, I'm wondering if anyone has had a similar issue and can point me in the right direction.  If the central office doesn't see an issue, the next step is for a tech to come for a visit. 
    Thanks in advance.
    Edit: I should also mention that while on the phone with Verizon I reset the modem, so it's back to the factory defaults.

    Oh yes, it has nothing to do with you or me or any computer, I myself am experiencing the second outage in less than a week.  Mine has been down AGAIN since sometime last night.  I was told when I called on Monday that nearly everyone in my area code had no service, that was an equipment problem.  I finally got a call on Tuesday, an automated message, saying that is had been resolved, and so it had.  For less than 2 days.  Now it's out again and I see nothing at all about it here on this website.  I have waited all day to use my husband's wireless card so I could catch on my stuff and also come here to see if there were some answers, but of course there are none.  Big surprise.  To say that I am unhappy is the understatement of the month.  This is unacceptable service and it is especially galling that nothing that I have seen is giving customers explanations for this latest outage.  I would like to see someone from Verizon explain what is going on here in my part of Southern California about why we keep losing our DSL service.

  • Trying to lock down DNS server settings to force use of OpenDNS

    I'm trying to lock down my time capsule on my home network to only allow outgoing DNS traffic to go through OpenDNS. I  have an 18 year old son, with his own computer, who bypasses my OpenDNS by entering the DNS settings for Google on his Windows 7 machine. I have no control over his machine, only my router.
    A discussion on the OpenDNS forums mentions blocking port 53 and forcing all DNS traffic through the OpenDNS server settings I've entered into my router, but I can't see any way to do this on the time capsule. Am I missing something?

    There is nothing you can do.. TC do not have access to firewall.. at least for ipv4.
    You need a much better router.. bridge the TC and grab a Netgear WNDR3800 and run Gargoyle firmware. The power will be put back in your hands.. then he will buy his own 3G connection.. maybe at 18 it is rather too late.

  • Exchange 2013 Split DNS, how to get WAN clients to use public Split DNS IP when inter-office link is DOWN?!

    Hello,
    I have an Exchange 2013 deployment and a LAN/WAN setup, we have many small remote WAN linked offices that can resolve to the Exchange Server's internal IP.
    Outlook clients in remote WAN offices work fine as long as the link is UP since the Split Brain DNS for Exchange will resolve the internal clients to the internal IP of the Exchange server, Outlook connects up without issues.
    However, in the event of loosing connection to our remote sites, they will no longer be able to resolve to the internal Exchange IP, but they still have a backup public internet that they can use. So should the inter-office connectivity fail we have it setup
    so clients in remote offices can still browse the internet, etc.
    However, their Outlook fails to connect because it has a cached DNS record for our Split Brain Exchange DNS setup and tries to resolve it to its internal IP, instead of refreshing the cache and grabbing the public IP of the Exchange server since now they
    would be resolving it over the public internet.
    Is there anything I can do with my existing configuration to allow the client to pick up the public IP of the Split DNS setup when our inter-office connection is down and the client is no longer able to use the internal IP they have cached for Exchange?
    I guess I could lower the TTL on the DNS record to something like 1 minute so it does not cache the DNS record / IP for long? Is this the best approach?

    http://public.wsu.edu/~brians/errors/lose.html
    I would suggest that the best approach is to either improve the reliability of the WAN link or to configure DNS to always use the Internet path.  You might want to work with your network guy, perhaps there's a way to have your gateways automatically
    switch to an Internet VPN backup when the WAN link is down or something like that.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • DNS Service DOWN ! Someone plz explain to me why !

    Hi,
    Please, can someone explain to me why i receive this message :
    Server Server_Name BorderManager X.X.X.X DNS (Domain Name Service)
    SVCDOWN
    at 10:20:34
    And when i check the status of the DNS at the proxy console all my DNS
    are
    up and running ???
    What's going here ? And then i get the message that the DNS service is
    back
    online..
    Thanks in advance. !!!
    K. Chabot

    One thing that i forgot to say, we use a software called What's Up tomonitor all our servers, Pix, router, etc....
    Everytime i load named.nlm on a server and than i start monitoring it,
    what's up is always telling me that the service is down after a while,
    but
    in fact the service is up. I'm wondering if named doesn't refresh or
    do
    something that what's up could interpret as a down and re-up again.
    Any thought about this ?
    By the way, i did roll back to 5.53 for the tcp like you suggested, @
    first,
    i got a fatal warning that a critical error happened and i couldn't
    access
    any nic card bind to tcp without an error, so i just re-initialize the
    interface and reboot the server. It's now working, and i hope for a
    long
    long time !
    Did you have any issues regarding the tcpip 5.93 with border manager
    3.6 ?
    Isn't novell gonna patch this in the next service pack or do we need
    to back
    it up before any future service pack ?
    Again Craig, thanks a lot for your help !
    K. Chabot
    "K. Chabot" <[email protected]> wrote in message
    news:AR77b.22112$[email protected]..
    > Named i mean.
    >
    > "K. Chabot" <[email protected]> wrote in message
    > news:6R77b.22111$[email protected]..
    > > Yes Names was running on that server.
    > >
    > > "Craig Johnson" <[email protected]> wrote in message
    > > news:[email protected]..
    > > > Are you trying to run NAMED on that server by any chance?
    > > >
    > > > Craig Johnson
    > > > Novell Support Connection SysOp
    > > > *** For a current patch list, tips, handy files and books on
    > > > BorderManager, go to http://nscsysop.hypermart.net ***
    > > >
    > >
    > >
    >
    >

  • Primary DNS resolution slow if PDC role DC is down

    Hello,
    In my environment I'm running purely Windows Server 2012 in a two site environment.  I run a single domain infrastructure with my main site that has 2 domain controllers (one has all FSMO roles), and a second site which has a single domain controller.
     I've been looking all over the forums for a related topic, but haven't read something anything that fits my scenario.  Basically what happens is, if the DC that has FSMO roles (specifically PDC) goes offline, or if I were to turn the DNS service
    off, all devices would take forever for DNS resolution.  Another scenario (which is essentially the same) is if the VPN tunnel between the two sites goes down, all clients at site 2 would take awhile for DNS resolution.  If those clients launch their
    browser any website they go to takes 5-10 seconds to load.  They could reboot their PC, and do ipconfig /flushdns, and even though those clients DNS settings point to the DC at site 2 as primary DNS, it takes awhile.  As soon as the PDC server is
    restored everything is back to normal.  Quite frequently the VPN tunnel will go down leaving very slow responses at site 2.  Oddly enough is, if the tunnel were to go down, and I logged into the DC at site 2, if I were to ping various domains the
    response would take 5 or so seconds.  Is this normal to occur?  If not, how could I possibly remedy this?  My assumption is that, if the primary DNS were to go down, or in this case the PDC server goes down, one of the secondary servers would
    kick in.  I appreciate any light you can shed on this issue.
    Ken

    I agree with Meinolf. It's not always the DNS or PDC or whatever DC is in question's, fault. A lot of it is due to the client side resolver algorithm. Here's more specifics on how the whole process works - and note that this applies to all operating systems,
    Windows, Linux, Unix, BEOS..... because they all follow the RFCs defining how client side resolvers work.
    This blog discusses:
    WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
    Client side resolution process chart.
    The DNS Client Side Resolver algorithm.
    If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
    DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
    Client side resolution process chart
    Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM  1764  1
    http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm.aspx
    DNS Clients and Timeouts (Part 1 & Part 2), karammasri [MSFT] Dec 2011 6:18 AM
    http://blogs.technet.com/b/stdqry/archive/2011/12/02/dns-clients-and-timeouts-part-1.aspx
    http://blogs.technet.com/b/stdqry/archive/2011/12/15/dns-clients-and-timeouts-part-2.aspx
    DOMAIN NAMES - CONCEPTS AND FACILITIES - Dicusses local resolvers.
    http://tools.ietf.org/html/rfc882
    =============
    To add on how the client resolver picks a nameserver, below is a link to a discussion that points out the following - and please note, the operative point in the first bullet point indicates "equivalent," meaning that all DNS servers you enter into a NIC,
    must all reference the same exact data, so you can't mix nameserver with different data and expect the client to try all of them.
    •by RFC, all nameservers in a zone's delegation are equivalent
    •they are indistinguishable to the client
    •clients are allowed to choose the NS to query with whichever policy they wish
    •if any picked server fails to respond (e.g. "ns3"), then the next server is picked among the remaining set (e.g. ns1 and ns2) according to the policy
    •often clients use sophisticated policies that "score" servers and pick more often the ones that replied faster
    •as a by-product, in practice this policy makes caches favor "nearest" servers
    That was quoted from:
    When is a secondary nameserver hit?
    http://serverfault.com/questions/130608/when-is-a-secondary-nameserver-hit
    ===============
    So you have to check when the first DNS goes down, not all directory enabled apps can handle it. opened.
    Another issue is the client has bounded to the logon server during the DC Locator process. That's difficult to mess with other than restarting the machine...
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

  • Change DNS host name automatically when one device is down

    Hi all
    I am first copying below the question which I have posted in a thread related to DNS few days back .
    You cannot vote on your own post                    
    Hi
    our network team has setup Bluecoat proxy server in our main office and DR site . We have configured GPO to populate the details of proxy server hostname in the proxy setting  eg : Proxy server .  IP1 is the IP address for the device in Head office
    and IP2 is the IP address assigned for device in DR site. currently  we have given a DNS entry as
    Proxyserver - IP1.
    So DNS resolves the IP address of device in Head office and authentication and internet access works.
    But we want to use the DR device  to be used automatically   (only )when head office device is not reachable. But how to configure the settings for DNS I am not sure.
    I don't want to use round robin as it will send the traffic to both head office and DR in a load balancing fashion .
    for this request I had received an advice to use a script to monitor the first device continuously and if not reachable  then change the Hostname in DNS to that of second device  .
    Let me know if anyone can help me on this.
    Thanks in advance
    Midhin 

    Hi Midhin,
    Agree with Jrv, I also recommend you can consult proxy vendor for a better solution.
    In addition, if you still want to update host name in DNS via Powershell, please refer to the script to update A record in DNS:
    $Zone = "dns zone"
    $oldobj = Get-DnsServerResourceRecord -ZoneName $Zone -RRType "A" -Name "hostname"
    $newobj = Get-DnsServerResourceRecord -ZoneName $Zone -RRType "A" -Name "hostname"
    $NewObj.RecordData.IPv4Address = "newipaddress"
    Set-DnsServerResourceRecord -NewInputObject $NewObj -OldInputObject $OldObj -ZoneName $Zone
    If there is anything else regarding the powershell script issue, please feel free to post back.
    Best Regards,
    Anna Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Maybe you are looking for