DNS fails using router IP address as DNS server address with static IP

This is my first experience with a Linksys router so it might be normal behaviour but just wanted to check. With a WRT54G2 router I have a few PC's I want to use static IP. Up till now with other brand routers including Belkin and Dlink, I have been able to just put the router IP address in as the address of the DNS server when I use static IP. This seemed to work initially with the Linksys but now for some reason, if I don't code the IP addresses of the DNS server provided by my ISP, DNS lookup fails.  If I use DHCP for the PC's there is no problem.
Is that normal behaviour or is there something wrong I am doing?
Thanks
Larry

I decided to upgrade my Linksys 54G router to a "Ultra RangePlus Wireless-N Broadband Router (WRT160N)Version 1" . I have had problems with the wireless (as far as I know just wireless portion) connection dropping. I have done some searching I was able to find some settings to try, and it did work better, but not for too long. I have this router within arm reach away, so it's not a distance issue. I have tried many things for about the last 6months or so.
As a last resort, and I do mean last resort and against my better judgement I purchased " Dual-Band Wireless-N Notebook Adapter (WPC600N) Version 1". I was hoping it was a compatibility issue, but there was no difference.
I have heard of trying older firmware, but I can't find any.
I have been a Linksys fan for quite sometime, but as of recently I am thinking of reconsidering if I can't get this resolved with out spending any more money.

Similar Messages

  • 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

  • I am trying to sync calendar and contacts on the BB Z10, using iCloud. What is the server address?

    I am trying to sync calendar and contacts on the BB Z10, using icloud, what is the server address?

    How Do I Get Rid Of The “Other” Data Stored On My iPad Or iPhone?
    http://tinyurl.com/85w6xwn
    With an iOS device, the “Other” space in iTunes is used to store things like documents, settings, caches, and a few other important items. If you sync lots of documents to apps like GoodReader, DropCopy, or anything else that reads external files, your storage use can skyrocket. With iOS 5/6/7, you can see exactly which applications are taking up the most space. Just head to Settings > General > Usage, and tap the button labeled Show All Apps. The storage section will show you the app and how much storage space it is taking up. Tap on the app name to get a description of the additional storage space being used by the app’s documents and data. You can remove the storage-hogging application and all of its data directly from this screen, or manually remove the data by opening the app. Some applications, especially those designed by Apple, will allow you to remove stored data by swiping from left to right on the item to reveal a Delete button.
     Cheers, Tom

  • Is it possible to use single ssl certificate for multiple server farm with different FQDN?

    Hi
    We generated the CSR request for versign secure site pro certificate
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}
    SSL Certificate for cn=abc.com   considering abc.com as our major domain. now we have servers in this domain like    www.abc.com,   a.abc.com , b.abc.com etc. we installed the verisign certificate and configured ACE-20 accordingly for ssl-proxy and we will use same certificate gerated for abc.com for all servers like www.abc.com , a.abc.com , b.abc.com etc. Now when we are trying to access https//www..abc.com or https://a.abc.com through mozilla , we are able to access the service but we are getting this message in certfucate status " you are connected to abc.com which is run by unknown "
    And the same message when trying to access https://www.abc.com from Google Chrome.
    "This is probably not the site you are looking for! You attempted to reach www.abc.com, but instead you actually reached a server identifying itself as abc.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of adgate.kfu.edu.sa. You should not proceed"
    so i know as this certficate is for cn=abc.com that is why we are getting such errors/status in ssl certficate.
    Now my question is
    1. Is is possible to  remove above errors doing some ssl configuration on ACE?
    2. OR we have to go for VerisgnWildcard Secure Site Pro Certificate  for CSR generated uisng cn =abc.com to be installed on ACE  and will be used  for all servers like  www.abc.com , a.abc.com etc..
    Thanks
    Waliullah

    If you want to use the same VIP and port number for multiple FQDNs, then you will need to get a wildcard certificate.  Currently, if you enter www.abc.com in your browser, that is what the browser expects to see in the certificate.  And right now it won't beause your certificate is for abc.com.  You need a wildcard cert that will be for something like *.abc.com.
    Hope this helps,
    Sean

  • My computer keeps saying "The server responded with "502" to operation CalDAVAccountRefreshQueueableOperation." When I use iCal.  Please help.

    Every time I use iCal, my computer says, "The server responded with
    “502”
    to operation CalDAVAccountRefreshQueueableOperation."
    Please help!!

    Same here....didn't see it within the first couple weeks of iCloud, but yesterday it popped up on both my Macbook and iMac.

  • Why doesn't my airport express router issue proper DNS server address to DHCP clients?

    I have an Airport express router (version 7.6.4).  It was configured to connect to internet via a cable modem, acting as a router with NAT. This means it obtians WAN address from cable modem, and in LAN it assumes IP address 10.0.1.1 as a gateway, and issue IP address to my 4-5 wireless clients (MBA, iPads, PCs) vi DHCP.
    However I recently encounter an issue, that the router no longer issues DNS server address obtained from Cable Modem(206.x.x.x) but instead tell every DHCP client to use router ip address (10.0.1.1) as DNS server. I was pretty sure before Dec 2013 it is issueing (206.x.x.x) to all DHCP clients.
    Apparently now the Airport express is acting as a DNS server or as a DNS cache. This works sporadically and very often result in long DNS look up or DNS look up failure.
    Is this a bug or is it supposed to do so?  Any configuration can turn it off so Airport express will issue Cable modem obtained DNS server to DHCP clients?
    My network otherwise works fine. for some of the Clients (e.g. one MBA) I configured DNS for it mannually and it's internet is working very smoothly.

    But this will be a problem for my ipad and iphone that uses wifi.
    These devices either allow full DHCP. If you need to mannually enter DNS server, you will need to turn entire IP configuration to mannual and that will be a problem for me.

  • WiFi only works close to router, DNS fail, Signal Bars present but Safari says no Internet, I've deleted and readded through to reset and full reset, I had no problem with 4.3.2 only 4.3.3 both my iPhone4 and my iPad2. I am now beside router - no problem

    Help
    WiFi only works close to router, DNS fail, Signal Bars present but Safari says no Internet, I've deleted and re-added through to reset and full reset, I had no problem with 4.3.2 only 4.3.3 both my iPhone4 and my iPad2. I am now beside router - no problem, but go 20 metres and WiFi becomes unstable. Only way to get either to work is disable WiFi either as a Hot Spot or turn it off and use the 3G connection. This worked with 4.3 &amp; 4.3.2 what has gone wrong? I raised it at the Apple Store in Belfast as a problem but was told that there was no problem with Apple but I must have a faulty router - yeah - that's a lot of faulty routers, my home, my office, my holiday home, Starbucks, my friends house, my son's house. I've tried all the 'fixes'. I think it is a plan to force us to buy Apple Routers

    Two ways out, I added two more Belkin Access Points in my house in Spain so that I'm not more than 10Mtrs away, (Reinforced Concrete & solar glass 2010)
    I bought 3 Apple Airports, 1 x Extreme and 2 x Express (1 as a hard wired AP, 1 as an extender) for my other house (Brick construction 1930's)
    Everthing now works perfectly, as I said 'an apple plot', so either blast them with signal or visit your nearest apple store.
    Early beta iOS5 (iPad) is also much inproved in Beta 3, I have not had any problem with 'Lion'
    Happy hunting!
    john

  • How to setup a static ip address and DNS on airport extreme using the iOS Airport Utility?

    I am at a location that only has wired ethernet.  The ethernet connection has a specific  Static IP address, subnet, gateway, and DNS setting.  I cannot seem to find how to enter DNS settings using the Apple Utility on an iPad. HELP!!!

    First, I am assuming that you are trying to administer your AirPort base station for a static IP address using the iOS version of the AirPort Utility ... correct?
    If so, then to do so:
    Start the AirPort Utility app on the iPad
    Select your base station.
    Select Edit
    Select Internet Connection
    Select Static
    Enter the appropriate IP address information
    Select Done
    Sorry, it does not appear that direct input for DNS IP addresses is an available option with this version of the iOS AirPort Utility app. Not sure why this was not included.

  • DNS failing to register

    Background
    all Server 2012 VMs...1 domain controller, multiple member servers.  I have only one member server that is having DNS issues.  The problem was first discovered while trying to gpupdate /force, which failed stating there's a lack of network connectivity
    with the domain controller, event ID 1129.  I looked in the event logs further and there were event ID 8020 "the system failed to register host (A AAA) resource records for network adapter with settings....", there were also events where the
    time service could not sync with the DC. 
    From there I dropped the server from the domain, and then rejoined it without issue.  It still was having the same errors.  I looked in the DNS Manager on the DC, and the record with that IP address had the wrong host name.  I deleted it,
    and attempted to have the server register the record.  I followed ipconfig /flushdns, and ipconfig /registerdns. Still having the same issues. 
    It is part of the domain, trust relationships seem fine.  Any thoughts?  I can't find anything anywhere on that event ID. 

    Seems like too few info to decide what is your problem. My very first guess is that there is error in VM settings. Make sure that VMs has disabled time synchronization with host. Secon problem may stem from possible port blocking (try without fw) and third
    problem in VM may be caused by wrongly setting IP DNS in NIC parameters.
    Also start with dcdiag to find the health of AD. Do not remember to delete DNS cache whenever you do any chnages is DNS settings.
    Here are references that may help:
    https://technet.microsoft.com/en-us/library/cc727335(v=ws.10).aspx
    If you use DHCP from network router (which is wrong configuration):
    https://support.microsoft.com/en-us/kb/2459530
    HTH
    Milos

  • Set up a proper live and local DNS behind a router

    Hello dear friends,
    I'm new to Snow Leopard Server and also i'm quite inexperienced in setting up DNS. We bought a Mac Pro for out small company along with Snow Leopard Server to become independent from our ISP, for some specific services like web hosting, mail and to bring up new services like Address book server, iCal server, FTP, Mobile access etc...
    So for me to do that i have to set up our own DNS first. We already bought our domain name (crisconsult.ro) and since then the site has been hosted on our ISP and then aliased to Apple. We also have our own (fix) public IP 80.86.123.116.
    Having installed SL Server and set-up, behind an Airport extreme router, the server was unable to pick up our name server which is ns.crisconsult.ro. Since the router is the first in the network, the server became second with a local IP 10.0.1.2. This is the same IP that the server automatically set up for DNS, BUT if i keep this ip on our name server (ns) i feel it's not good since:
    host ns.crisconsult.ro returns
    ns.crisconsult.ro has address 10.0.1.2
    and host 80.86.123.116 returns
    116.123.86.80.in-addr.arpa domain name pointer ns.crisconsult.ro.
    As i understand there should be our public IP (80.86.123.116), BUT all the tutorials on the net regarding setting up DNS in Leopard Server point that at DNS one should put the machine's own local IP and have the machine look at itself as DNS in network settings.
    So? Is there a local DNS and a public DNS to set up? What gives?
    I could really appreciate some help in configuring DNS, along to some good and real examples of DNS servers configured behind a router.
    Thanks,
    Andrei

    Andrei,
    I too, would love nothing more than to be able to use DNS on my 10.4, 10.5 & 10.6 servers. Unfortunately, the only way I have found to effectively wield a somewhat complete level of control over the bind DNS included with the server, is to abandon all usage of the Server Admin DNS control in favor of something like webmin. The good news is, webmin gives you a host of other features that I (sadly) don't expect to see within the Apple Server GUI any time soon.
    Bad news, is that the 'best practice' way of setting up a stable, functional DNS on a Mac Server seems to be: clean install, webmin install, and never, ever use the apple DNS interface. Similar rule applies to web server.
    I like to think the measure of a good admin is the ability to fix the problem(s) without having to reinstall completely. However, I can say from much experience and extensive googling, that what you are trying to do is a game of hopscotch in a minefield. You should be VERY familiar with the installation and setup process once you have your box configured the way you want it.
    Hopefully one day Apple will decide to take the bull by the horns and address teh fact that DNS is an integral part of a sever set up these days and provide us users with some of that Apple think-outside-the-box-so-you-dont-have-to product that they have been so well known for. I can't say whether they're in too much of a hurry deploying video iPods or super-duper mice that the server product that you and I would love to see work efectively simply doesn't.
    Sorry to get on a rant, I just want to save you some time that I lost figgerin' on this vexing enigma. I can use citations for my assertions if need be.
    -Chance

  • "Back to my Mac isn't working properly because your DNS server isn't responding. Contact your ISP for an alternate DNS server address, and enter it in Network Preferences".

    Hi, i am trying to setup back to my mac at home but I get the error "Back to my Mac isn't working properly because your DNS server isn't responding. Contact your ISP for an alternate DNS server address, and enter it in Network Preferences".
    There is no documentation on how to solve this anywhere.
    I have an Arris router set to bridged mode which is connected to a 5th generation airport extreme. I have tried using the google dns servers instead of the one assigned by the cable company in the AE but I still get the same error.
    Any help would be much appreciated
    Kenneth

    New to BTMM, I got stung today with the silly DNS problem message. Solution:
    1) Flush DNS cache with:
    dscacheutil -flushcache;sudo killall -HUP mDNSResponder
    2)System preferences > iCloud > untick BTMM then tick it again. The warning should have disappeared.
    Edit #1
    Apologies for the noise. The warning has come back
    Edit #2
    Just found out that BTMM is not compatible with double NAT. That's not helpful.
    http://support.apple.com/kb/TS1208

  • Can't delete grayed-out DNS server addresses

    I want to replace two grayed-out DNS server addresses from the Network panel (under the DNS tab in "Advanced…"), to replace them with OpenDNS settings. But they can't be selected/deleted. How do I get around this problem?

    That is correct - those are provided by your router and can not be deleted - you can add Open DNS servers (click the + sign) or log into the router admin page (I recommend this way) and have your router use the Open DNS servers fro everything on your network (this will change the grayed out ones)
    LN

  • 451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain

    Hi,
    I have two Exchange 2010 servers running on Windows 2008 Ent R2.
    These mail servers have been running fine for a few years.
    Today I noticed two things.
    1. users were telling me they were having delays receiving emails from outside of our own domain. The mail gets sent out, but it takes about 15-30 mins for users outside our our domain to get their mail. Mail sent from inside our domain gets delivered right
    away.
    2. An error message that I see when I go to Tools->Queue Viewer in EMC. The error is: 451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain. This error  shows up when you click on the "Queues" tab and then look at the
    "hub version 14" under "next hop domain" column. 
    I'm assuming these two things are related. I don't understand why the problem is just showing up now. As I said, mail delivery has been fine for a while and I haven't done any major updates to the server in a few months.
    Thanks for any ideas and suggestions as to what might be causing it and where I can look.
    Mike

    Hi,
    1. I replaced my Cert with the same exact cert from GoDaddy, just an updated expire date.
    2. We have two exchange servers.
    3. The message I am seeing now, is under "Last Error" for every queue (not individual messages).
    That error message is:  451 4.4.0 Primary Target IP address responded with 421 4.2.1 Unable to connect. Attempted failover to alternate host but that did not succeed.
    OR
    451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain. (This is the same error I mentioned earlier.
    I ran some tests on mxmailbox.com for my domain name.I got the following alerts back when running a DNS check.
    SOA Serial Number format is invalid. ns.rackspace.com Serial XXXXXXXX : Suggested serial format year was 1402 which is before 1970
    AND
    SOA Expire value out of recommended range.  ns.rackspace reported Expire 604800. Expire is recommeded to be between 1209600 and 2419200
    I use Rackspace DNS servers for External lookups.
    Does this point my mail delay problem to Rackspace or something local on my own machine?
    Thanks!
    Mike

  • Manually provided DNS server addresses are higher priority than DHCP's

    Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
    With the recent revelation of DNS server security issues, many have expressed a desire to use DNS servers they know to be secure rather than the servers specified by their routers via DHCP, which often are those of a particular ISP.
    When you manually enter a DNS server address in Mac OS X Leopard's Network preference pane, the manually entered address(es) appear below any DHCP-provided addresses (which are shown in grey as they are unchangeable), leading one to assume that DHCP-provided addresses always have priority over any a user may specify.
    However, a check of the /etc/resolv.conf file generated by Mac OS X shows that in fact user-provided DNS addresses will supercede any provided by DHCP.
    As an example, if your router promotes itself as a DHCP server, its IP address, say "192.168.0.253," will appear, greyed out, in the Network->Advanced->DNS preferences pane.
    If you then add, say, OpenDNS' addresses of "208.67.222.222" and "208.67.220.220," the preferences window will show:
    192.168.0.253 (greyed out)
    208.67.222.222
    208.67.220.220
    But the generated /etc/resolv.conf will show the order Mac OS X will actually reference the servers is:
    nameserver 208.67.222.222
    nameserver 208.67.220.220
    nameserver 192.168.0.253
    While this is non-intuitive, given how the addresses are displayed in the preference pane, it is exactly the way a user would hope things would work - allowing one to specify DNS servers to be used in lieu of any a router provides, especially handy if the router propagates the address of a DNS server that is having issues, that is untrusted or is simply overloaded or offline.
    Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.

    That's very good to KNOW.
    I figured it as such as I have some manual entries for the office and I don't use profiles, so it stays there when I go home.
    I notice a slow-down when office DNS entries are used at home -as one would suspect.
    I do like KNOWING that it's the case though - thanks for the info!
    Scott

  • Bridged gateway & router behind both show DNS requests

    May be nothing to this, as I found nothing on this exact issue, after searching web & some network tech forums.
    I've got an AT&T gateway that I connected wired WRT54GL behind it & put the Linksys in "DMZplus" mode, in the gatway's FW.  There's no true bridge mode on these gateways (same on 2 models - a 2Wire 3600HGV & Pace 3051NV).
    After putting a device (router) in DMZ mode, following commonly found instructions for disabling features in the AT&T gatway FW, it's supposed to "let everything connected to the DMZ device "pass through" the gatway's router / FW.
    BUT... after doing this, when run DNS Benchmark tool (GRC's), results show both Linksys DNS resolver addresses & the gatway (192.168.1.254 "homeportal Local Network Nameserver") are "doing DNS queries."  Both are shown in benchmark results as (actively) BEING used by the "system," indicated by "a solid green dot by nameserver entries," beside both the router's & gateway's DNS resolver addresses, in benchmark results (per GRC help docs for benchmark tool).
    Even when I switched to putting DNS addresses in Vista, under the connection's IPv4 setup, re ran benchmark, still shows the DMZ'd gateway's address as "System" nameserver, & shows benchmark results for it (192.168.1.254 "homeportal Local Network Nameserver") AND for DNS resolvers entered in the Linksys.
    What to make of this?  How to see if BOTH the router (or Windows) AND the DMZ'd gateway are ACTUALLY doing DNS queries?  Thanks.

    May be nothing to this, as I found nothing on this exact issue, after searching web & some network tech forums.
    I've got an AT&T gateway that I connected wired WRT54GL behind it & put the Linksys in "DMZplus" mode, in the gatway's FW.  There's no true bridge mode on these gateways (same on 2 models - a 2Wire 3600HGV & Pace 3051NV).
    After putting a device (router) in DMZ mode, following commonly found instructions for disabling features in the AT&T gatway FW, it's supposed to "let everything connected to the DMZ device "pass through" the gatway's router / FW.
    BUT... after doing this, when run DNS Benchmark tool (GRC's), results show both Linksys DNS resolver addresses & the gatway (192.168.1.254 "homeportal Local Network Nameserver") are "doing DNS queries."  Both are shown in benchmark results as (actively) BEING used by the "system," indicated by "a solid green dot by nameserver entries," beside both the router's & gateway's DNS resolver addresses, in benchmark results (per GRC help docs for benchmark tool).
    Even when I switched to putting DNS addresses in Vista, under the connection's IPv4 setup, re ran benchmark, still shows the DMZ'd gateway's address as "System" nameserver, & shows benchmark results for it (192.168.1.254 "homeportal Local Network Nameserver") AND for DNS resolvers entered in the Linksys.
    What to make of this?  How to see if BOTH the router (or Windows) AND the DMZ'd gateway are ACTUALLY doing DNS queries?  Thanks.

Maybe you are looking for