DNS upgrade issues, bind9.5.0

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

dns issues

Just recently we have been having some dns issues. Some websites won't work i.e. (www.msn.com, aimexpress.aim.com...) I have manually put A records in my named.db file and in the hosts file to try to get it to work but still they do not work. I have looked up updating my named.ca file for the...

2. Ubuntu

Linux Redhat ES 4.0 - DNS Config Issues

Hello all, I've a very strange thing hapenning in my Sys, I've configured the IP, DNS eveything for my internat connection, but Im only able to browse Redhat.com websites. I cant open anyother site!!! :eek: Im sure the internet is configured 'coz it displays the list of avail updates for...

3. Cybersecurity

Dns cache poisoning upgrade to bind9.5.0p2

Hi again guys, It seems this is a global thing affecting all the DNS bind versions prior to July 28 2008. I have my work cut out for me very soon, I see at least a handful of servers in my list that either need to patching or upgrading. How many of you guys are affected? Anybody successfully...

4. UNIX and Linux Applications

bind9 with ldap using dlz

Hello guys, can anyone help me with the below error I'm getting from bind9? I'm trying to make bind read all the zone info from openldap, I have already created the schema and I've put some info into the ldap. I have also tried to google the error with no success. I'm aware there is an problem...

5. Solaris

Solaris 10 - DNS / Issues / Help

Hi all Long time no speak, I hope you are all well. Im looking at a DNS issue here and reckon Igot a AD / DNS server issue elsewhere but need to rule out the configuration of my two server's first. IVe got the nameserver enteries in /etc/resolv.conf and dns in the /etc/nsswitch.conf ...

6. UNIX for Dummies Questions & Answers

DNS on Unix box issues

Hi Guys, Just wanted to seek your assistance on an issue encountered with one of our client DNS server query. we have 2 sets of DNS servers.. internal and external. For Internal to reach the external DNS server (DMZ) it has to go through 2 FWs. Current settings: - FW rules for Internal...

7. Solaris

Bind9 DNS on Solaris 10 x4270 & CPU usage

I have configured a Bind9 DNS on a X4270 machine with Solaris10 I am excuting some repformance tests with DNSPERF tool and maximun CPU usage is 23%. I have seen with prstat -L -p PID that named process usses only 2 of the 8 available CPU at the same time although threads for all CPUs exist....

8. Red Hat

DNS Server Setup Centos 6.5 Issues

I am having a bit of trouble getting my CENTOS 6.5 DNS server to work correctly in our testlab environment. Lab network is 10.8.0.0/24 in which we all access from 10.7.0.0.0/24 && 10.0.0.0/24. Here are my configs: options { listen-on port 53 { 127.0.0.1; 10.8.0.19;}; #listen-on-v6 port 53 {...

9. IP Networking

Bind9 DNSSEC and rollerd

Hi all, I've a litte problem to get rollerd running and signing my zones if the ZSK of my zones are near expiring or expired. rollerd is running but do nothing startet with: /usr/bin/perl /usr/sbin/rollerd -rrfile /etc/bind/all.rollrec -directory /etc/bind -logfile /dev/stdout ...

LEARN ABOUT CENTOS

ipa-client-automount

ipa-client-automount(1) 					 IPA Manual Pages					   ipa-client-automount(1)

NAME

       ipa-client-automount - Configure automount and NFS for IPA

SYNOPSIS

       ipa-client-automount [OPTION]... <location>

DESCRIPTION

       Configures automount for IPA.

       The automount configuration consists of three files:

       o      /etc/nsswitch.conf

       o      /etc/sysconfig/autofs

       o      /etc/autofs_ldap_auth.conf

       By  default  this will use DNS discovery to attempt to determine the IPA server(s) to use. If IPA servers are discovered then the automount
       client will be configured to use DNS discovery.

       If DNS discovery fails or a specific server is desired, use the --server option.

       The default automount location is named default. To specify a different one use the --location option.

       The IPA client must already be configured in order to configure automount. The IPA client is configured as part of a server installation.

       There are two ways to configure automount. The default is to use sssd to manage the automount maps. Alternatively autofs can configured	to
       bind to LDAP over GSSAPI and authenticate using the machine's host principal.

       The nsswitch automount service is configured to use either sss or ldap and files depending on whether SSSD is configured or not.

       NFSv4 is also configured. The rpc.gssd and rpc.idmapd are started on clients to support Kerberos-secured mounts.

OPTIONS

       --server=SERVER Set the IPA server to connect to

       --location=LOCATION
	      Automount location

       -S, --no-sssd
	      Do not configure the client to use SSSD for automount

       -d, --debug
	      Print debugging information to stdout

       -U, --unattended
	      Unattended installation. The user will not be prompted

       --uninstall
	      Restore the automount configuration files

FILES

       Files that will be always be configured:

	      /etc/nsswitch.conf

       Files that will be configured when SSSD is the automount client (default):

	      /etc/sssd/sssd.conf

       Files that will be configured when using the ldap automount client:

	      /etc/sysconfig/autofs

	      /etc/autofs_ldap_auth.conf

EXIT STATUS

       0 if the installation was successful

       1 if an error occurred

IPA
								    May 25 2012 					   ipa-client-automount(1)