Dns client config

I have completed a new install of Arch and cannot resolve outside hostnames.  The dns is pointing to my isp's dns, do I need to run my own dns to resolve?  I can ping the isp's dns server so I know it's just a resolution issue.
nsswitch.conf has hosts: files dns
host.conf has order hosts,bind
I have searched the forums and come up with nothing.  Any help would be greatly appreciated.  Thank you.  -Alec

Thanks for your response, I have setup resolve.conf
search myhost.domain.com domain.com
ns1.myisp.com xx.xx.xx.xx
ns2.myisp.com xx.xx.xx.xx
Also the hosts file lists the nameservers.
But I still cannot resolve.

Similar Messages

  • If i have Dns Client service running, is it necessary to enable dns prefetch in the about:config section?

    I've been wondering this for a while and can't seem to find the answer.
    Whenever i set network.dns.disablePrefetch to true, the browser seems to load a bit more smoothly and even with the pref. disabled, the dns client service seems to still cache dns whenever i check on cmd using the ipconfig /displaydns command.
    Does this mean that the browser still fetches dns even with the pref disabled?

    I'm not really sure if it speeds up the loading process or not since it's a bit hard to tell but like i said, the loading is smoother.
    Is Dns Client service different from Dns prefetch?

  • JDeveloper 11.1.2.1.0 Can't edit subversion client config

    I'd like to change the subversion client config to enable auto-props but can't find an option to do this in JDeveloper. Tools->Preferences...->Versioning->Subversion->General only appears to have an option for modifying the server parameters. Anybody know how I can change the subversion client config through JDev?

    Makes sense. Editing the svn 'servers' file through JDev displays it's path at the top of editor:
    C:\Documents and Settings\BLACKADR\Application Data\JDeveloper\system11.1.2.1.38.60.81\o.jdeveloper.subversion
    and I can see that there is also a default 'config' file in this same folder so I guess this must be the one JDev will pick up. Will think about raising an enhancement request for an Edit "Client config" option in the JDev Preferences dialog. Thanks for your help.

  • DNS client in a non-global zone

    Hello,
    I want to configure only the non-global zone as a DNS client, with
    /etc/resolv.conf
    /etc/defaultdomain
    /etc/nsswitch.conf
    Is this ok or is this a global wide issue?
    -- Nick

    Yes. The /etc file system is private to each zone (both in the sparse and whole root models) so each zone can have it's own DNS settings (as well as private things like a different time zone and such).

  • Domain Controllers that are DNS servers DNS Client settings

    [Copying verbatim from a mail by Joe ]
    So I have been pinged by a few folks recently on configuration of client DNS settings on Domain Controllers that are also functioning as DNS Servers. Lots of debate. I understand there has been long time debate within MSFT as well.
    From http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx there
    is the quote
    "3.When referencing a DNS server on itself, a DNS client should always use a loopback address and not a real IP address."
    From http://www.microsoft.com/en-us/download/confirmation.aspx?id=9166 (Windows
    Server 2008 R2 Core Network Guide)
    "9.        In Preferred DNS server, type the IP address of your DNS server. If you plan to use the local computer as the preferred DNS server, type the IP address of the
    local computer.
    10.       In Alternate DNS Server, type the IP address of your alternate DNS server, if any. If you plan to use the local computer as an alternate DNS server, type the IP address of
    the local computer."
    From http://technet.microsoft.com/en-us/library/dd378900(v=ws.10).aspx (DNS:
    DNS servers on <adapter name> should include their own IP addresses on their interface lists of DNS servers)
    "The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to
    itself for name resolution, it can become an island and fail to replicate with other domain controllers. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should
    be configured only as a secondary or tertiary DNS server on a domain controller...
    Add the loopback IP address to the list of DNS servers on all active interfaces. The loopback IP address should not be the first server in the list."
    ESPECIALLY "For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only as a secondary or tertiary
    DNS server on a domain controller." and "Add the loopback IP address to the list of DNS servers on all active interfaces. The loopback IP address should not be the first server in the list."
    Why shouldn't loopback not be first, the justification is why you shouldn't only use loopback, not why it shouldn't be first.
    From http://technet.microsoft.com/en-us/library/ff807362(v=ws.10).aspx (DNS:
    DNS servers on <adapter name> should include the loopback address, but not as the first entry)
    "If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners. 
    The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to itself,
    or points to itself first for name resolution, this can cause a delay during startup. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only
    as a secondary or tertiary DNS server on a domain controller."
    This also seems like justification against only using loopback versus using it first.
    Are there any actual real documented issues for using loopback first and a remote DNS server second and perhaps third? If the local DNS server service isn't working yet (or at all), I would expect the DNS Client process
    to try to connect to it, fail, and then failover to the secondary just like I would expect it to failover if the remote DNS server was secondary and it was unavailable and it failed back to the loopback. Am I making a bad assumption?
    And by documented I don't mean random responses to questions on the internet or other such items. I mean a KB article or technet article or properly researched and tested other web article from a reliable resource.
    thanks, 
    joe

    As I understand it, the scenario whereby a DC could become an 'island' if it points only to itself, or to itself first, was repaired in the Windows Server 2003 product cycle. See
    http://support.microsoft.com/kb/275278 for information about this scenario.
    However, there is still a known problem of slow boot times that can occur. See
    http://support.microsoft.com/kb/2001093 for information about this. The scenario that is discussed assumes there is a power failure and servers shut down due to overheating while on backup power. When
    multiple servers come online simultaneously after power is restored, there can be a significant delay.
    The recommended configuration is one that avoids a single point of failure, but also tries to optimize the speed of resource record registration, so that Active Directory can properly synchronize.
    -Greg

  • New Domain controller, DNS client settings before FSMO transfer

    I recently promoted a new domain controller.  It is the fourth domain controller and third in the site.  I plan to decommission the other two domain controllers in the site leaving just the new one.   Right now the new domain controller points
    its tcp\ip client to the other other domain controller\DNS servers as primary and itself at the bottom.  The other domain controllers point to themselves as primary and the newest domain controller on the bottom of the list.  Clients on the network
    use the original domain controllers as DNS from DHCP first and then the new domain controller DNS.  Is it okay to transfer all the FSMO roles to the new domain controller or should I make all the DNS clients point to it first?

    Hi,
    It is possible to first change your FSMO roles and after this is done then point your DNS clients to the new DC. This should not be a problem.
    some interesting information about assigning your FSMO Roles: http://www.windowsdevcenter.com/pub/a/windows/2004/06/15/fsmo.html
    Hope this helps you out.

  • Q on Solaris 11.2 DNS Client

    Hi All,
    Pls note that the mailq command is found hangup whenever the DNS Client is being enabled in our Solaris 11.2 server.  So, do anyone have any clue on this behavior?
    Thanks & Regards

    Hi Carlos,
    Solaris 10 and Solaris 11 are "apples and oranges", to use the popular comparitive expression. In this case, it's more like "grapes and watermelons", or "strawberries and raisins" . .you get the idea : )
    This doc talks about it:
    http://www.oracle.com/technetwork/server-storage/solaris11/documentation/solaris11-whatsnew-201111-392603.pdf
    "System Configuration in the SMF repository
    Some basic system configuration has been migrated into the SMF system configuration
    repository with Oracle Solaris 11, as part of a wider move to reduce the number of
    configuration files that are located in /etc and to improve the management of configuration
    during system upgrade. . . . . ."
    and specifically on S11 name services:
    http://docs.oracle.com/cd/E23824_01/html/E24456/gliyc.html#gllcu
    It's a whole new world.

  • DNS Client Service Issues

    Hi all,
    We seem to be having some odd issues with about 50% of our Windows 7 clients.  I'll give you a brief run down of what is occurring.
    Server 2008 R2 Domain serving about 50 clients.  Having changed a static entry in DNS to point an A record to a new server, the Windows 7 clients randomly can't resolve the IP.
    So on testing using either the FQDN or just the host name the request doesn't resolve using ping.
    Tried using NSLOOKUP and NSLOOKUP resolves just fine.
    Tried ping again and no joy.  Turned off the DNS Client Service and instantly the host name resolved to the correct IP.
    Restart the DNS Client Service and there's about a 25% chance the hostname will no longer resolve.  On ALL of the PCs that have this issue.  Stopping or restarting the DNS Client  Service resolves the problem.
    Also it should be noted that running ipconfig /flushdns has no effect and the host still doesn't resolve to the IP.  ONLY stopping the DNS Client service on the Windows 7 PCs does the trick. 
    Your suggestions are most welcome!
    Thanks,
    Simon.

    Hi Yolanda,
    Nothing in any event log anywhere and I've checked all the AV logs and run scans already, drivers are up to date.  Also there is no firewalling at the client end.
    Had a read through the NRPT doc and I don't think that is relevant as the host they are trying to get to doesn't have anything different to anything else in the DNS Domain.  All hosts are of the form host.contoso.com.  All we've done is change
    the IP address on one of the hosts manually within DNS. 
    It is almost as if on a reboot, the DNS Client Service picks up an old copy of the cache and refuses to overwrite it.
    I'm considering changing the Parameters of the service to reduce the TTL of the cached entries from the default of one day to one hour and turn off caching of negative responses as follows:
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dnscache\Parameters]
    "MaxCacheTtl"=dword:e10
    "MaxNegativeCacheTtl"=dword:0
    Thanks,
    Simon.

  • DNS Client not Configured

    Hello,
    I have reviewed a number of other posts regarding this BPA error but have not found a specific solution.
    Receiving the BPA Error: The DNS Client is not configured to point to the internal IP Address of the Server
    If the DNS is currently functional, is this required? As a general practice, if it is working, don't change it....
    If required, can someone list the steps to change this?

    Hi:
    The reason the Server should be the DNS server is to maintain _internal_ DNS so each station can find the server and each other. The Internet will work if the setting on the station can find a DNS server that can find the upstream DNS servers.
    The way this is meant to work is the stations and the server query the DNS server on the Essentials server.  If it knows the name to IP translation, as it should for LAN queries it will provide the results.  If it does not, as it most likely would
    not in the case of a new internet search, is uses forwarders or root hints (look up those terms if you don't recognize them) to find the name to IP translation and send it back to the station.
    If you use DNS servers outside the LAN the usual results are slow startup times and slow network browsing.
    Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

  • DNS ZONE Config on CSS

    Hi All,
    Is it possible to config DNS ZONE config on CISCO CSS.
    Can anyone explain me what does this commands do
    dns-server zone 1 tier1 "primary"
    dns-server
    dns-record a <Zone Name> <External IP> 1 single kal-icmp <VIP> 254 sticky-disabled weightedrr 1

    How to Configure the CSS to Load Balance DNS Servers
    http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a00801d015a.shtml
    For example,Basically we need to enter the following commands:
    Configure the DNS server zone for zone-based DNS. Specify the zone, tier number, and an optional text description:
    - CSS (config)# dns-server zone 0 tier1 ""
    Configure the CSS to act as a DNS server:
    - CSS (config)# dns-server
    Add the DNS records as needed:
    - CSS (config)# dns-record a www.home.com 192.x.1.1 15 single kal-ap 172.x.25.1 50
    sticky-enabled
    Configure DNS as primary to point to itself:
    CSS (config)# dns primary 172.x.1.90
    (circuit VLAN1 - ip address 172.3x.1.90 / 24)
    This is just an example but it is basically all you need to configure DNS on the box.
    DNS configuration commands:
    http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_710/cmdrefgd/cmdglobc.htm#wp1104782
    A different use on the box for DNS would be basically to load balance the DNS traffic
    between DNS servers. This is however something different to configure on the box and more
    details can be found here:

  • Removing client-config.wsdd from axis.jar

    Hello
    I am working with websphere and under the WEB-INF/lib folder i have axis.jar. This jar contains client-config.wsdd file.
    This is causing some problems and now im told to remove client-config.wsdd file out of axis.jar and deploy it directly to <my_appName>.war/
    Does any one have experience with websphere? or how can i remove client-config.wsdd file from a jar file? do i have to unzip it to do that? where should i place client-config.wsdd file so it is in my .war/ for the application.
    Thanks

    Many questions leap to mind.
    1) Who told you that removing the JAR will remove that �problem, and why?
    2) Why is it so difficult to use WinZIP or any other tool to remove a file from a JAR?
    3) What has it to do with WSAS?
    4) Why don't you use the WSAS classpath settings to provide a file that overrides the one in AXIS?
    5) Who hired you?

  • EVENT 1006, DNS Client Events

    I have been getting these DNS client events And my internet connection has been limited and disconnected over and over again. My desktop (this event) is connected to my notebook computer that is connected to a wireless connection (Apt Managed) 

    Hi,
    This issue can occur by incorrect DNS settings. I suggest you perform the following steps to troubleshoot the issue.
    1. Click "Start", input "NCPA.CPL" (without quotation marks) and press Enter.
    2. Right click on the connection that you use for the local connection, and then click "Properties".
    3. Click to select "Internet Protocol Version 4 (TCP/IPv4)", and then click "Properties".
    4. In the Internet Protocol window, let's change the "Preferred DNS server" to 208.67.222.222
    5. Click 'OK' twice to complete the modification.
    If the issue persists, please repeat the steps and change the "Preferred DNS server" to 208.67.220.220.
    Kim Zhou
    TechNet Community Support

  • Advanced mode and automated client config..

    Hi,
    Is it possible to configure automated client config when server is in advanced mode?
    I have looked through the OD manual etc., but can only find info about automated client config for workgroup and standard install..
    Am I just looking the wrong places?
    Regards,
    Kenneth

    Hi
    You are looking in the right places. No its not possible, leastways not in the sense I think you mean? You can achieve a deep level of client config using Advanced but only in the sense of controlling aspects of what clients can or can't do as well as access to Server Resources amongst other things.
    You may have got a 'flavour' of what is achievable if you've been reading the Open Directory Admin Manual? You might also want to have a look at this:
    http://images.apple.com/server/macosx/docs/UserManagementv10.5.mnl.pdf
    Tony

  • DNS client service issue

    I’ve got a DNS client service issue:
    I have a webserver in my local Domain, which is accessible locally only.
    One client machine with Windows Server 2012 sometimes cannot access the websites situated on this local webserver. Its event viewer does not contain any issues. The machine can still access the internet. The thing I need to do then, is to restart the DNS client
    service on this Windows Server client. After that these local websites are reachable again. The DNS Server is installed on the DC.
    What approach could I follow to solve this issue?
    Patrick

    Are you using the fqdn (host.domain.tld), a single label name or a custom dns name?
    If you use the single label name, dns name resolution depends on the suffixes, make sure these are configured.
    If the issue occurs, you could use nslookup to check if the communication with all configured dns servers is working and the required records are there.
    Use ping to check if the correct ip with FQDN is returned. No FQDN implies netbios was used for name resolution - no good -> check the dns configuration
    If you use a custom dns name, check what IP it resolves (ping/nslookup); is it a server local IP? If not, check if the issue resolves by putting the dns alias in the hostsfile with a local ip (or 127.0.0.1 if the bindings for your site allow)
    The issue might also be solely related to the dns cache maintained by the service. You could check if ipconfig /flushdns resolves the issue to confirm. Their is not much configuration or debugging info available on this, but issues I've seen all boil down
    to dns servers not being corretcly configured on the client's ip settings.
    You could enable the DNS Client Events operational log (eventviewer->applications and services logs\Microsoft\Windows to maybe get more info on the issue.
    MCP/MCSA/MCTS/MCITP

  • Show lwapp client config

    In old IOS LAP, the command "show lwapp client config" showed the Static configuration of a LAP. Now in the last or new IOS this command is not availbale. How I can see the static configuration in the LAP ??
    New IOS:
    LAP1131#show lwapp client config
                            ^
    % Invalid input detected at '^' marker.
    Old IOS version:
    LAP#show lwapp ip config
    LWAPP Static IP Configuration
    IP Address         10.177.2.X
    IP netmask         255.255.255.224
    Default Gateway    10.177.2.X
    Primary Controller 172.166.1.X
    Thanks !

    What version are you running?  If its 5.2 or 6.0 the commands changed to CAPWAP (show capwap client config).

Maybe you are looking for