DNS Service not Start in RHEL 6.4 64 bit Post: 302880961

Sponsored Content

Operating Systems Linux Red Hat DNS Service not Start in RHEL 6.4 64 bit Post 302880961 by Chintanghanti on Wednesday 25th of December 2013 05:29:50 AM

12-25-2013

Registered User

DNS Service not Start in RHEL 6.4 64 bit

Hi All,

I am new to linux and i am configuring DNS server but while i restart service it shows below given error. Please help to solve this error.

Code:

[root@rhel64 named]# /etc/init.d/named restart
Stopping named:                                            [  OK  ]
Generating /etc/rndc.key:
                                                           [  OK  ]
Starting named:
Error in named configuration:
zone localhost/IN: loaded serial 42
zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
ict.org:33: icte_oracle_9.ict.org: bad owner name (check-names)
ict.org:36: icte_nt01.ict.org: bad owner name (check-names)
ict.org:37: icte_nt02.ict.org: bad owner name (check-names)
ict.org:38: icte_nt03.ict.org: bad owner name (check-names)
zone ict.org/IN: loading from master file ict.org failed: bad owner name (check-names)
zone ict.org/IN: not loaded due to errors.
_default/ict.org/IN: bad owner name (check-names)
ict.ac.in:36: linux_db01.ict.ac.in: bad owner name (check-names)
ict.ac.in:69: icte_oracle_9.ict.ac.in: bad owner name (check-names)
ict.ac.in:72: icte_w2k02.ict.ac.in: bad owner name (check-names)
ict.ac.in:75: icte_nt01.ict.ac.in: bad owner name (check-names)
ict.ac.in:76: icte_nt02.ict.ac.in: bad owner name (check-names)
ict.ac.in:77: icte_nt03.ict.ac.in: bad owner name (check-names)
ict.ac.in:78: icte_nt04.ict.ac.in: bad owner name (check-names)
ict.ac.in:80: cont_edu.ict.ac.in: bad owner name (check-names)
zone ict.ac.in/IN: loading from master file ict.ac.in failed: bad owner
zone ict.ac.in/IN: not loaded due to errors.
_default/ict.ac.in/IN: bad owner name (check-names)
icte.ac.in:103: hr_ict.icte.ac.in: bad owner name (check-names)
zone icte.ac.in/IN: loading from master file icte.ac.in failed: bad owner na
zone icte.ac.in/IN: not loaded due to errors.
_default/icte.ac.in/IN: bad owner name (check-names)
zone iiitv.icte.ac.in/IN: loaded serial 20130806
zone icte.edu/IN: loaded serial 20100603
dns_rdata_fromtext: 10.100:15: near 'icte_nt01.icte.ac.in.': bad name (check
dns_rdata_fromtext: 10.100:16: near 'icte_nt02.icte.ac.in.': bad name (check
dns_rdata_fromtext: 10.100:17: near 'icte_nt03.icte.ac.in.': bad name (check
zone 168.192.in-addr.arpa/IN: loading from master file 10.100 failed: bad name (c
zone 168.192.in-addr.arpa/IN: not loaded due to errors.
_default/168.192.in-addr.arpa/IN: bad name (check-names)
                                                           [FAILED]

Last edited by Scott; 12-25-2013 at 06:31 AM.. Reason: Use code tags, please...

Chintanghanti

View Public Profile for Chintanghanti

Find all posts by Chintanghanti

10 More Discussions You Might Find Interesting

1. Solaris

How to be sure the dns service is running ?

Well, i changed my lan card and finally i got it up and running, i have /etc/resolv.conf with domain xxx.xxx nameserver xxx.xxx.xxx.xxx and it was working with me earlier with the old lan card, with the new one i added it ip using auto-dhcp and its received an ip from my dhcp and it can ping...

2. Shell Programming and Scripting

Start a service as user

Hi I need a service to be start as user after a reboot. My script in /etc/init.d contain the following: start() { su - $USER cd ${INSTALL_PATH}/bin ./MyApp -X exit return 0 } This function stops after su - $USER, I get user shell, and only if I manualy...

3. AIX

Q: how to start a service when system start

As topic, assume we have a service called "blahservice" and we can start it by: startsrc -s blahservice what is the best practice to run such command when system start? - directly use mkitab to add it into /etc/inittab or - drop startup scripts in /etc/rc.d/rcX.d I know they...

4. UNIX for Advanced & Expert Users

Get an error while trying to start DNS server

Hi Guys, I am trying to configure DNS on ESX server. Everything done but when I am trying to start the DNS, it gives me an error # service named restart Stopping named: Starting named: Error in named configuration: /etc/named.conf:42: when using 'view' statements, all zones must be...

5. Red Hat

Wrong ELFCLASS64 in RHEL 5 64 bit

Hi, I am using DB2 9.7 , configured odbc.ini file and exported environment variables but I am getting the following error. error while loading shared libraries: libodbc.so.1: wrong ELF class: ELFCLASS64 Kindly help.

6. Red Hat

User (Profile) Specific Start Menu for RHEL 6.1 using KDE 4.3.4

I installed RHEL 6.1 with KDE 4.3.4 using LDAP on a PC and have now the problem to specifiy a user/Profile specific start menu. I have used already the kmenuedit tool and tailored for one user a specific menu, successfully. I changed as an example the konsole submenu. The kmenuedit was...

7. Red Hat

Re-start of RHEL server

I had a query that should the RHEL servers in production environment be re-started say every 2-3 months so that the cache is cleared? I hope, my question is clear that should the Red Hat Linux servers be restarted periodically. Please revert with the reply to my query. Regards

8. Red Hat

How to configure DNS configuration for RHEL 5?

I wanted to know how to configure DNS configuration for RHEL 5. I hope, my query is clear of how to setup DNS for RHEL 5. Please revert with the reply to my query Regards

9. Red Hat

Memmove fail on 4 Gb+ raster under RHEL 64 bit

I'm rotating huge image rasters (1+ GB) using a 3-shear algorithm. I rotate 'in-place' after reallocating the raster. A necessary first step is reorganizing the image in the new raster dimensions that will exist after the rotation. RGBA pixels byte packed into uint32. The following code runs...

10. AIX

How to find which internal hosts still using my DNS service ? Please help

Hello guys, I am new to AIX . I have two AIX v5.3 servers running BIND DNS service on them. The plan is to shut down only the DNS service on them, but in order to do that I have to determine which internal hosts are still using the servers to resolve DNS queries. Can you please advice on...

LEARN ABOUT SUSE

usoc

usoc(7D)                                                              Devices                                                             usoc(7D)

NAME

       usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver

DESCRIPTION

       The  Fibre  Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre
       Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.

FILES

       /kernel/drv/usoc

           32-bit ELF kernel module

       /kernel/drv/sparcv9/usoc

           64-bit ELF kernel module

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       +-----------------------------+-----------------------------+
       |Architecture                 |SPARC                        |
       +-----------------------------+-----------------------------+
       |Interface stability          |Unknown                      |
       +-----------------------------+-----------------------------+
       |Availability                 |SUNWusoc                     |
       +-----------------------------+-----------------------------+

SEE ALSO

       fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D)

       Writing Device Drivers

       Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994

       Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996

        Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998

       Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998

DIAGNOSTICS

       The following messages are logged and may also appear on the system console. On the console these messages are preceded by:

       usoc%d:

       where

       usoc%d:
       is the per-port instance number of the usoc controller.

       Fibre Channel is ONLINE

       The Fibre Channel loop is now online.

       Fibre Channel Loop is ONLINE

       The Fibre Channel loop is now online.

       Fibre Channel Loop is OFFLINE

       The Fibre Channel loop is now offline.

       attach failed: device in slave-only slot.

       Move soc+ card to another slot.

       attach failed: alloc soft state.

       Driver did not attach, devices will be inaccessible.

       attach failed: bad soft state.

       Driver did not attach, devices will be inaccessible.

       attach failed: unable to map eeprom

       Driver was unable to map device memory; check for bad hardware.  Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to map XRAM

       Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to map registers

       Driver was unable to map device registers; check for bad hardware. Driver did not attach to device,   devices will be inaccessible.

       attach failed: unable to access status register

       Driver was unable to map device  registers; check for bad hardware.  Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to install interrupt handler

       Driver was not able to add the interrupt routine  to the kernel. Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to access host adapter XRAM

       Driver was unable to access device RAM; check for  bad  hardware. Driver did not attach to device,  devices will be inaccessible.

       attach failed: unable to write host adapter XRAM

       Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

       attach failed: read/write mismatch in XRAM

       Driver was unable to verify device RAM; check for  bad hardware. Driver did not attach to device, devices will be inaccessible.

SunOS 5.10                                                          20 Jul 1999                                                           usoc(7D)