Bind Failed

Discussion in 'HOWTO-Related Questions' started by christoph2k, Apr 20, 2007.

  1. christoph2k

    christoph2k New Member

    Hello,

    I'm working through the Perfect System Setup - Debian Etch. I'm on page 4 (http://www.howtoforge.com/perfect_setup_debian_etch_p4), but when I go to start Bind9, it gives me an error:

    Starting domain name service...: bind failed!

    It doesn't tell me anything in the Log Files... They just show the following (please excuse the length):

    Apr 20 19:11:06 debian syslogd 1.4.1#18: restart.
    Apr 20 19:11:06 debian kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
    Apr 20 19:11:06 debian kernel: Linux version 2.6.18-4-486 (Debian 2.6.18.dfsg.1-12) (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Mon Mar 26 16:39:10 UTC 2007
    Apr 20 19:11:06 debian kernel: BIOS-provided physical RAM map:
    Apr 20 19:11:06 debian kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 0000000000100000 - 0000000013ff0000 (usable)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 0000000013ff0000 - 0000000013ff8000 (ACPI data)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 0000000013ff8000 - 0000000014000000 (ACPI NVS)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 00000000ffee0000 - 00000000fff00000 (reserved)
    Apr 20 19:11:06 debian kernel: BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
    Apr 20 19:11:06 debian kernel: 319MB LOWMEM available.
    Apr 20 19:11:06 debian kernel: On node 0 totalpages: 81904
    Apr 20 19:11:06 debian kernel: DMA zone: 4096 pages, LIFO batch:0
    Apr 20 19:11:06 debian kernel: Normal zone: 77808 pages, LIFO batch:15
    Apr 20 19:11:06 debian kernel: DMI 2.3 present.
    Apr 20 19:11:06 debian kernel: ACPI: RSDP (v000 AMI ) @ 0x000fa340
    Apr 20 19:11:06 debian kernel: ACPI: RSDT (v001 AMIINT SiS735XX 0x00001000 MSFT 0x0100000b) @ 0x13ff0000
    Apr 20 19:11:06 debian kernel: ACPI: FADT (v001 AMIINT SiS735XX 0x00001000 MSFT 0x0100000b) @ 0x13ff0030
    Apr 20 19:11:06 debian kernel: ACPI: DSDT (v001 SiS 735 0x00000100 MSFT 0x0100000d) @ 0x00000000
    Apr 20 19:11:06 debian kernel: ACPI: PM-Timer IO Port: 0x808
    Apr 20 19:11:06 debian kernel: Allocating PCI resources starting at 20000000 (gap: 14000000:eac00000)
    Apr 20 19:11:06 debian kernel: Detected 1194.986 MHz processor.
    Apr 20 19:11:06 debian kernel: Built 1 zonelists. Total pages: 81904
    Apr 20 19:11:06 debian kernel: Kernel command line: root=/dev/hda1 ro
    Apr 20 19:11:06 debian kernel: Local APIC disabled by BIOS -- you can enable it with "lapic"
    Apr 20 19:11:06 debian kernel: mapped APIC to ffffd000 (01282000)
    Apr 20 19:11:06 debian kernel: Enabling fast FPU save and restore... done.
    Apr 20 19:11:06 debian kernel: Enabling unmasked SIMD FPU exception support... done.
    Apr 20 19:11:06 debian kernel: Initializing CPU#0
    Apr 20 19:11:06 debian kernel: PID hash table entries: 2048 (order: 11, 8192 bytes)
    Apr 20 19:11:06 debian kernel: Console: colour VGA+ 80x25
    Apr 20 19:11:06 debian kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Apr 20 19:11:06 debian kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Apr 20 19:11:06 debian kernel: Memory: 317136k/327616k available (1502k kernel code, 9828k reserved, 601k data, 256k init, 0k highmem)
    Apr 20 19:11:06 debian kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
    Apr 20 19:11:06 debian kernel: Calibrating delay using timer specific routine.. 2391.06 BogoMIPS (lpj=4782139)

    Does anyone have a clue what the problem could be?

    If you need any more information then just ask, but I have followed the HOW-TO to a t :).

    Thank you!

    Chris
     
  2. christoph2k

    christoph2k New Member

    Fixed.... Sorry!
     
  3. fher98

    fher98 New Member

    Well,.. can you tell me how you fix it,.. cuz i have the same problem.. thanks
     
  4. christoph2k

    christoph2k New Member

  5. fher98

    fher98 New Member

    thanks... ill do
     

Share This Page