The service 'named' on server server.domain.net is currently down

F

flexilove

New member
Joined
Jun 27, 2023
Messages
14
hello I just installed directadmin and I'm trying to assign a hostname but I'm getting this error I also created a hostname A record

The service 'named' on server server.domain.abc is currently down​

This message has been automatically generated notifying you that the service named is currently down.
Click to expand...
 
check logs - usually error described with details here.
/var/log/messages or /var/named/data/named.run
 
flexilove said:
ello I just installed directadmin and I'm trying to assign a hostname but I'm getting this error I also created a hostname A record
Click to expand...
Did you wait long enough? Is everything installed already, every service?

We had somebody with the same issue recently, and he started doing and changing all kind of things, while most things weren't even installed.
Directadmin itself is installed very quickly, but other services, like apache, php, mysql but also named, will take a while.

Check services in administration. If all is present, then indeed check logfiles.

Or try to restart named as root via SSH and see what error that it says:
service named restart
 
Redirecting to /bin/systemctl restart named.service
Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.
Click to expand...

Richard G said:
Did you wait long enough? Is everything installed already, every service?

We had somebody with the same issue recently, and he started doing and changing all kind of things, while most things weren't even installed.
Directadmin itself is installed very quickly, but other services, like apache, php, mysql but also named, will take a while.

Check services in administration. If all is present, then indeed check logfiles.

Or try to restart named as root via SSH and see what error that it says:
service named restart
Click to expand...
I get this error
Zhenyapan said:
check logs - usually error described with details here.
/var/log/messages or /var/named/data/named.run
Click to expand...

Jun 29 20:53:08 server bash: zone web1.wasyazilim.xyz/IN: loading from master file /var/named/web1.wasyazilim.xyz.db failed: file not found
Jun 29 20:53:08 server systemd: named.service: control process exited, code=exited status=1
Jun 29 20:53:08 server systemd: Unit named.service entered failed state.
Jun 29 20:53:08 server systemd: named.service failed.
 
I don't even have a /var/named/data/named.run file.

What do logs say? Check my post and see what is in there, check it and report outcome otherwise we aren't able to help you.
 
Richard G said:
Bir /var/named/data/named.run dosyam bile yok.

Günlükler ne diyor? Gönderime bakın ve orada ne olduğuna bakın, kontrol edin ve sonucu bildirin, aksi takdirde size yardımcı olamayız.
Click to expand...
managed-keys-zone: loaded serial 0
zone 0.in-addr.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
zone localhost.localdomain/IN: loaded serial 0
zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
zone localhost/IN: loaded serial 0
all zones loaded
running
network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
network unreachable resolving './NS/IN': 2001:500:1::53#53
network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
network unreachable resolving './NS/IN': 2001:500:a8::e#53
network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
network unreachable resolving './NS/IN': 2001:500:12::d0d#53
network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
network unreachable resolving './NS/IN': 2001:500:2::c#53
network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
network unreachable resolving './NS/IN': 2001:500:2d::d#53
network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:500:200::b#53
network unreachable resolving './NS/IN': 2001:500:200::b#53
network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
network unreachable resolving './NS/IN': 2001:500:2f::f#53
network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
network unreachable resolving './NS/IN': 2001:7fd::1#53
network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
network unreachable resolving './NS/IN': 2001:500:9f::42#53
network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
network unreachable resolving './NS/IN': 2001:dc3::35#53
network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
network unreachable resolving './NS/IN': 2001:7fe::53#53
managed-keys-zone: Key 20326 for zone . acceptance timer complete: key now trusted
resolver priming query complete
received control channel command 'stop'
shutting down: flushing changes
stopping command channel on 127.0.0.1#953
stopping command channel on ::1#953
no longer listening on 127.0.0.1#53
no longer listening on ::1#53
exiting
managed-keys-zone: journal file is out of date: removing journal file
managed-keys-zone: loaded serial 2
zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
zone localhost.localdomain/IN: loaded serial 0
zone localhost/IN: loaded serial 0
zone 0.in-addr.arpa/IN: loaded serial 0
all zones loaded
running
network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
network unreachable resolving './NS/IN': 2001:500:2d::d#53
network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
network unreachable resolving './NS/IN': 2001:7fd::1#53
network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
network unreachable resolving './NS/IN': 2001:500:9f::42#53
network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
network unreachable resolving './NS/IN': 2001:500:a8::e#53
network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
network unreachable resolving './NS/IN': 2001:500:12::d0d#53
network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
network unreachable resolving './NS/IN': 2001:500:1::53#53
network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
network unreachable resolving './NS/IN': 2001:7fe::53#53
network unreachable resolving './DNSKEY/IN': 2001:500:200::b#53
network unreachable resolving './NS/IN': 2001:500:200::b#53
network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
network unreachable resolving './NS/IN': 2001:500:2::c#53
network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
network unreachable resolving './NS/IN': 2001:500:2f::f#53
network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
network unreachable resolving './NS/IN': 2001:dc3::35#53
network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
managed-keys-zone: Key 20326 for zone . acceptance timer complete: key now trusted
resolver priming query complete
received control channel command 'reload'
loading configuration from '/etc/named.conf'
reading built-in trust anchors from file '/etc/named.root.key'
initializing GeoIP Country (IPv4) (type 1) DB
GEO-106FREE 20180327 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
initializing GeoIP Country (IPv6) (type 12) DB
GEO-106FREE 20180605 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
GeoIP City (IPv4) (type 2) DB not available
GeoIP City (IPv4) (type 6) DB not available
GeoIP City (IPv6) (type 30) DB not available
GeoIP City (IPv6) (type 31) DB not available
GeoIP Region (type 3) DB not available
GeoIP Region (type 7) DB not available
GeoIP ISP (type 4) DB not available
GeoIP Org (type 5) DB not available
GeoIP AS (type 9) DB not available
GeoIP Domain (type 11) DB not available
GeoIP NetSpeed (type 10) DB not available
using default UDP/IPv4 port range: [32768, 60999]
using default UDP/IPv6 port range: [32768, 60999]
sizing zone task pool based on 6 zones
none:104: 'max-cache-size 90%' - setting to 19311MB (out of 21457MB)
none:104: 'max-cache-size 90%' - setting to 19311MB (out of 21457MB)
configuring command channel from '/etc/rndc.key'
configuring command channel from '/etc/rndc.key'
reloading configuration succeeded
reloading zones succeeded
all zones loaded
running
network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
network unreachable resolving './DNSKEY/IN': 2001:500:200::b#53
network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
managed-keys-zone: Key 20326 for zone . acceptance timer complete: key now trusted
client @0x7f848c19f520 167.248.133.137#59264 (ip.parrotdns.com): query (cache) 'ip.parrotdns.com/A/IN' denied
client @0x7f848c19f520 167.248.133.51#45318 (ip.parrotdns.com): query (cache) 'ip.parrotdns.com/A/IN' denied
client @0x7f848c19f520 206.189.129.39#42177 (www.google.com): query (cache) 'www.google.com/A/IN' denied
client @0x7f848c19f520 146.88.241.160#33248 (2d978f69.asertdnsresearch.com): query (cache) '2d978f69.asertdnsresearch.com/A/IN' denied
client @0x7f848c173e40 146.88.241.230#47185 (www.wikipedia.org): query (cache) 'www.wikipedia.org/A/IN' denied
received control channel command 'reload'
loading configuration from '/etc/named.conf'
reading built-in trust anchors from file '/etc/named.root.key'
initializing GeoIP Country (IPv4) (type 1) DB
GEO-106FREE 20180327 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
initializing GeoIP Country (IPv6) (type 12) DB
GEO-106FREE 20180605 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
GeoIP City (IPv4) (type 2) DB not available
GeoIP City (IPv4) (type 6) DB not available
GeoIP City (IPv6) (type 30) DB not available
GeoIP City (IPv6) (type 31) DB not available
GeoIP Region (type 3) DB not available
GeoIP Region (type 7) DB not available
GeoIP ISP (type 4) DB not available
GeoIP Org (type 5) DB not available
GeoIP AS (type 9) DB not available
GeoIP Domain (type 11) DB not available
GeoIP NetSpeed (type 10) DB not available
using default UDP/IPv4 port range: [32768, 60999]
using default UDP/IPv6 port range: [32768, 60999]
sizing zone task pool based on 8 zones
none:104: 'max-cache-size 90%' - setting to 19311MB (out of 21457MB)
none:104: 'max-cache-size 90%' - setting to 19311MB (out of 21457MB)
configuring command channel from '/etc/rndc.key'
configuring command channel from '/etc/rndc.key'
reloading configuration succeeded
reloading zones succeeded
zone server1.wasyazilim.com/IN: loading from master file /var/named/server1.wasyazilim.com.db failed: file not found
zone server1.wasyazilim.com/IN: not loaded due to errors.
zone wasyazilim.xyz/IN: loaded serial 2023062300
all zones loaded
running
zone wasyazilim.xyz/IN: sending notifies (serial 2023062300)
network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:503:c27::2:30#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:503:ba3e::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:503:ba3e::2:30#53
network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:500:a8::e#53
network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:500:a8::e#53
network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:500:9f::42#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:500:9f::42#53
network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:500:2d::d#53
network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:500:2d::d#53
network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
network unreachable resolving './DNSKEY/IN': 2001:500:200::b#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:500:12::d0d#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:500:12::d0d#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:500:2f::f#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:500:2f::f#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:500:1::53#53
network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:500:1::53#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:7fd::1#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:7fd::1#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:dc3::35#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:dc3::35#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:500:200::b#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:500:200::b#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:7fe::53#53
network unreachable resolving 'ns2.wasyazilim.com/A/IN': 2001:7fe::53#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:502:1ca1::30#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:501:b1f9::30#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:503:d414::30#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:503:39c1::30#53
network unreachable resolving 'ns2.wasyazilim.com/AAAA/IN': 2001:503:a83e::2:30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:502:8cc::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:231d::2:30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:d937::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:856e::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:502:7094::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:d2d::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:eea3::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:83eb::30#53
'ns2.wasyazilim.com/A/IN' sorununu çözen ağ erişilemiyor: 2001:503:eea3::30#53
yönetilen anahtarlar bölgesi: bölge için anahtar 20326. kabul zamanlayıcısı tamamlandı: anahtar artık güvenilir
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:7fd::1#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:7fd::1#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:7fe::53#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:7fe::53#53
'yeniden yükle' kontrol kanalı komutu alındı
'/etc/named.conf' dosyasından yapılandırma yükleniyor
'/etc/named.root.key' dosyasından yerleşik güven bağlantılarını okuma
GeoIP Ülke (IPv4) (tip 1) DB başlatılıyor
GEO-106FREE 20180327 Yapı 1 Telif Hakkı (c) 2018 MaxMind Inc Tüm Hakları Saklıdır
GeoIP Ülke (IPv6) (tip 12) DB başlatılıyor
GEO-106FREE 20180605 Yapı 1 Telif Hakkı (c) 2018 MaxMind Inc Tüm Hakları Saklıdır
GeoIP Şehri (IPv4) (tip 2) DB mevcut değil
GeoIP Şehri (IPv4) (tip 6) DB mevcut değil
GeoIP Şehri (IPv6) (tip 30) DB mevcut değil
GeoIP Şehri (IPv6) (tip 31) DB mevcut değil
GeoIP Bölgesi (tip 3) DB mevcut değil
GeoIP Bölgesi (tip 7) DB mevcut değil
GeoIP ISP (tip 4) DB mevcut değil
GeoIP Org (tip 5) DB mevcut değil
GeoIP AS (tip 9) DB mevcut değil
GeoIP Etki Alanı (tip 11) DB mevcut değil
GeoIP NetSpeed (tip 10) DB mevcut değil
varsayılan UDP/IPv4 bağlantı noktası aralığı kullanılarak: [32768, 60999]
varsayılan UDP/IPv6 bağlantı noktası aralığı kullanılarak: [32768, 60999]
bölge görev havuzunu 8 bölgeye göre boyutlandırma
none:104: 'max-cache-size 90%' - 19311MB olarak ayarlandı (21457MB üzerinden)
none:104: 'max-cache-size 90%' - 19311MB olarak ayarlandı (21457MB üzerinden)
'/etc/rndc.key' adresinden komut kanalını yapılandırma
'/etc/rndc.key' adresinden komut kanalını yapılandırma
yeniden yükleme yapılandırması başarılı
yeniden yükleme bölgeleri başarılı
zone server1.wasyazilim.com/IN: /var/named/server1.wasyazilim.com.db ana dosyasından yükleme başarısız oldu: dosya bulunamadı
bölge server1.wasyazilim.com/IN: hatalar nedeniyle yüklenmedi.
tüm bölgeler yüklendi
koşma
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:12::d0d#53
bölge wasyazilim.xyz/IN: bölge seri numarası (2023062300) değişmedi. bölge kölelere aktarılamayabilir.
zone wasyazilim.xyz/IN: yüklenen seri 2023062300
zone wasyazilim.xyz/IN: bildirim gönderme (seri 2023062300)
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:200::b#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:9f::42#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:7fd::1#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:dc3::35#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:1::53#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:503:c27::2:30#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:2f::f#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:a8::e#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:7fe::53#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:2::c#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:2d::d#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:503:ba3e::2:30#53
yönetilen anahtarlar bölgesi: bölge için anahtar 20326. kabul zamanlayıcısı tamamlandı: anahtar artık güvenilir
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:12::d0d#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:1::53#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:12::d0d#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:1::53#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:a83e::2:30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:231d::2:30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:502:1ca1::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:eea3::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:d2d::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:502:8cc::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:83eb::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:856e::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:39c1::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:d414::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:39c1::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:d937::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:d414::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:502:7094::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:500:d937::30#53
'ns1.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:501:b1f9::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:502:7094::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:501:b1f9::30#53
'ns2.wasyazilim.com/AAAA/IN' sorununu çözen ağ erişilemiyor: 2001:503:231d::2:30#53
'yeniden yükle' kontrol kanalı komutu alındı
'/etc/named.conf' dosyasından yapılandırma yükleniyor
'/etc/named.root.key' dosyasından yerleşik güven bağlantılarını okuma
GeoIP Ülke (IPv4) (tip 1) DB başlatılıyor
GEO-106FREE 20180327 Yapı 1 Telif Hakkı (c) 2018 MaxMind Inc Tüm Hakları Saklıdır
GeoIP Ülke (IPv6) (tip 12) DB başlatılıyor
GEO-106FREE 20180605 Yapı 1 Telif Hakkı (c) 2018 MaxMind Inc Tüm Hakları Saklıdır
GeoIP Şehri (IPv4) (tip 2) DB mevcut değil
GeoIP Şehri (IPv4) (tip 6) DB mevcut değil
GeoIP Şehri (IPv6) (tip 30) DB mevcut değil
GeoIP Şehri (IPv6) (tip 31) DB mevcut değil
GeoIP Bölgesi (tip 3) DB mevcut değil
GeoIP Bölgesi (tip 7) DB mevcut değil
GeoIP ISP (tip 4) DB mevcut değil
GeoIP Org (tip 5) DB mevcut değil
GeoIP AS (tip 9) DB mevcut değil
GeoIP Etki Alanı (tip 11) DB mevcut değil
GeoIP NetSpeed (tip 10) DB mevcut değil
varsayılan UDP/IPv4 bağlantı noktası aralığı kullanılarak: [32768, 60999]
varsayılan UDP/IPv6 bağlantı noktası aralığı kullanılarak: [32768, 60999]
bölge görev havuzunu 8 bölgeye göre boyutlandırma
none:104: 'max-cache-size 90%' - 19311MB olarak ayarlandı (21457MB üzerinden)
none:104: 'max-cache-size 90%' - 19311MB olarak ayarlandı (21457MB üzerinden)
'/etc/rndc.key' adresinden komut kanalını yapılandırma
'/etc/rndc.key' adresinden komut kanalını yapılandırma
yeniden yükleme yapılandırması başarılı
yeniden yükleme bölgeleri başarılı
zone server1.wasyazilim.com/IN: /var/named/server1.wasyazilim.com.db ana dosyasından yükleme başarısız oldu: dosya bulunamadı
bölge server1.wasyazilim.com/IN: hatalar nedeniyle yüklenmedi.
tüm bölgeler yüklendi
koşma
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:503:c27::2:30#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:503:ba3e::2:30#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:2f::f#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:2d::d#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:dc3::35#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:1::53#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:7fd::1#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:12::d0d#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:9f::42#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:7fe::53#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:2::c#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:200::b#53
ağa erişilemiyor './DNSKEY/IN' çözümleniyor: 2001:500:a8::e#53
yönetilen anahtarlar bölgesi: bölge için anahtar 20326. kabul zamanlayıcısı tamamlandı: anahtar artık güvenilir
alınan kontrol kanalı komutu 'dur'
kapatma: yıkama değişiklikleri
127.0.0.1#953'te komut kanalını durdurma
::1#953'te komut kanalını durdurma
::#53'te artık dinlemiyorum
127.0.0.1#53'te artık dinlemiyorum
45.151.143.105#53'te artık dinlenmiyor
çıkmak

[/BİR ŞEYİN ÖNCEDEN REKLAMI]
Click to expand...
Jun 25 03:17:01 server systemd: Started Session 2504 of user root.
Jun 25 03:17:02 server systemd: Starting Generate rndc key for BIND (DNS)...
Jun 25 03:17:02 server systemd: Started Generate rndc key for BIND (DNS).
Jun 25 03:17:02 server systemd: Starting Berkeley Internet Name Domain (DNS)...
Jun 25 03:17:02 server bash: zone localhost.localdomain/IN: loaded serial 0
Jun 25 03:17:02 server bash: zone localhost/IN: loaded serial 0
Jun 25 03:17:02 server bash: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
Jun 25 03:17:02 server bash: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Jun 25 03:17:02 server bash: zone 0.in-addr.arpa/IN: loaded serial 0
Jun 25 03:17:02 server bash: zone wasyazilim.xyz/IN: loaded serial 2023062300
Jun 25 03:17:02 server bash: zone server.wasyazilim.xyz/IN: loading from master file /var/named/server.wasyazilim.xyz.db failed: file not found
Jun 25 03:17:02 server bash: zone server.wasyazilim.xyz/IN: not loaded due to errors.
Jun 25 03:17:02 server bash: _default/server.wasyazilim.xyz/IN: file not found
Jun 25 03:17:02 server systemd: named.service: control process exited, code=exited status=1
Jun 25 03:17:02 server systemd: Failed to start Berkeley Internet Name Domain (DNS).
Jun 25 03:17:02 server systemd: Unit named.service entered failed state.
Jun 25 03:17:02 server systemd: named.service failed.
Jun 25 03:17:02 server kernel: Firewall: *UDP_IN Blocked* IN=ens192 OUT= MAC=ff:ff:ff:ff:ff:ff:ac:16:2d:b3:15:80:08:00 SRC=45.151.143.182 DST=45.151.143.255 LEN=68 TOS=0x00 PREC=0x00 TTL=128 ID=55365 PROTO=UDP SPT=57621 DPT=57621 LEN=48
Jun 25 03:17:04 server kernel: Firewall: *UDP_IN Blocked* IN=ens192 OUT= MAC=ff:ff:ff:ff:ff:ff:ac:16:2d:b3:15:80:08:00 SRC=45.151.143.182 DST=45.151.143.255 LEN=68 TOS=0x00 PREC=0x00 TTL=128 ID=55381 PROTO=UDP SPT=57621 DPT=57621 LEN=48
Jun 25 03:17:05 server kernel: Firewall: *ICMP_IN Blocked* IN=ens192 OUT= MAC=00:0c:29:b8:2c:e8:a8:d0:e5:b0:ec:81:08:00 SRC=3.26.210.46 DST=45.151.143.105 LEN=36 TOS=0x00 PREC=0x00 TTL=222 ID=49055 DF PROTO=ICMP TYPE=8 CODE=0 ID=10 SEQ=10160
Jun 25 03:17:05 server kernel: Firewall: *ICMP_IN Blocked* IN=ens192 OUT= MAC=00:0c:29:b8:2c:e8:a8:d0:e5:b0:ec:81:08:00 SRC=3.26.28.102 DST=45.151.143.105 LEN=36 TOS=0x00 PREC=0x00 TTL=224 ID=43211 DF PROTO=ICMP TYPE=8 CODE=0 ID=10 SEQ=10160
Jun 25 03:17:06 server kernel: Firewall: *ICMP_IN Blocked* IN=ens192 OUT= MAC=00:0c:29:b8:2c:e8:a8:d0:e5:b0:ec:81:08:00 SRC=13.236.70.96 DST=45.151.143.105 LEN=36 TOS=0x00 PREC=0x00 TTL=223 ID=14181 DF PROTO=ICMP TYPE=8 CODE=0 ID=32 SEQ=13527
Jun 25 03:17:06 server kernel: Firewall: *ICMP_IN Blocked* IN=ens192 OUT= MAC=00:0c:29:b8:2c:e8:a8:d0:e5:b0:ec:81:08:00 SRC=3.26.96.250 DST=45.151.143.105 LEN=36 TOS=0x00 PREC=0x00 TTL=222 ID=10912 DF PROTO=ICMP TYPE=8 CODE=0 ID=32 SEQ=13527
Jun 25 03:17:06 server kernel: Firewall: *ICMP_IN Blocked* IN=ens192 OUT= MAC=00:0c:29:b8:2c:e8:a8:d0:e5:b0:ec:81:08:00 SRC=13.210.217.2 DST=45.151.143.105 LEN=36 TOS=0x00 PREC=0x00 TTL=222 ID=37410 DF PROTO=ICMP TYPE=8 CODE=0 ID=32 SEQ=13527
Jun 25 03:17:06 server kernel: Firewall: *UDP_IN Blocked* IN=ens192 OUT= MAC=ff:ff:ff:ff:ff:ff:f0:1f:af:d2:10:3f:08:00 SRC=45.151.143.164 DST=45.151.143.255 LEN=68 TOS=0x00 PREC=0x00 TTL=128 ID=38552 PROTO=UDP SPT=57621 DPT=57621 LEN=48
Click to expand...
service named restart
Redirecting to /bin/systemctl restart named.service
Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.
Click to expand...
 
Sorry, I don't understand Turkish, but from what I see, this is at least one of your problems for not starting.

zone server1.wasyazilim.com/IN: /var/named/server1.wasyazilim.com.db ana dosyasından yükleme başarısız oldu: dosya bulunamadı
bölge server1.wasyazilim.com/IN: hatalar nedeniyle yüklenmedi.
tüm bölgeler yüklendi
koşma
Click to expand...
If Google translated this correctly then the zone server1.wasyazilim.com.db is present in named.conf but the file does not exists.

Yes here you go, same but then in English.

Code: 
Jun 25 03:17:02 server bash: zone server.wasyazilim.xyz/IN: loading from master file /var/named/server.wasyazilim.xyz.db failed: file not found
Jun 25 03:17:02 server bash: zone server.wasyazilim.xyz/IN: not loaded due to errors.
Jun 25 03:17:02 server bash: _default/server.wasyazilim.xyz/IN: file not found

So you have to fix your hostname record. Or remove it from DA and create it again.

You probably also highly customized your named.conf since I see a lot of geoip stuff in there.
Also a lot of DNS keys not found. Does not look as a default named.conf to me.

However, things might work again if you fix the hostname record.
 
I changed the hostname but I still have the same problem
Richard G said:


Google bunu doğru bir şekilde tercüme ettiyse, zone server1.wasyazilim.com.db, adlandırılmış.conf'ta bulunur, ancak dosya mevcut değildir.

Evet, işte burada, aynı ama sonra İngilizce.

Code: 
25 Haziran 03:17:02 sunucu bash: zone server.wasyazilim.xyz/IN: /var/named/server.wasyazilim.xyz.db ana dosyasından yükleme başarısız oldu: dosya bulunamadı
Haz 25 03:17:02 sunucu bash: zone server.wasyazilim.xyz/IN: hatalar nedeniyle yüklenmedi.
25 Haziran 03:17:02 sunucu bash'ı: _default/server.wasyazilim.xyz/IN: dosya bulunamadı

Bu nedenle, ana bilgisayar adı kaydınızı düzeltmeniz gerekir. Veya DA'dan kaldırın ve yeniden oluşturun.

Orada pek çok coğrafi ip öğesi gördüğüm için, muhtemelen adlandırılmış.conf dosyanızı da oldukça özelleştirmişsinizdir.
Ayrıca çok fazla DNS anahtarı bulunamadı. Bana varsayılan bir name.conf gibi görünmüyor.

Ancak, ana bilgisayar adı kaydını düzeltirseniz işler yeniden çalışabilir.
Click to expand...
 
flexilove said:
I changed the hostname but I still have the same problem
Click to expand...
Yes because I didn't say to change the hostname but the hostname record. I might have been a bit unclear.

Log in as administrator.
Go under adminstrator settings to DNS Administration.
Search for your server hostname there, should be a standalone record, so like server.wxxxxim.xyz and delete that one, probably since you changed your hostname it's now still called server1.wxxxxxim.xyz.

Remove that one, then create a new one with the current hostname, then it should be fixed if all is well.
 
prnt.sc

Screenshot

Captured with Lightshot
prnt.sc prnt.sc
ekledim fakat sorun devam ediyor
Richard G said:
Evet, çünkü bir bilgisayar markası değil, bir bilgisayar adı korumasını değiştirmeyi söylemişti. Biraz kararsız kalmış olabilirim.

Yönetici olarak oturum açın.
Yönetici ayarları, DNS Yönetimi'ne gidin.
Orada sunucu ana bilgisayar adınızı arayın, server.wxxxxim.xyz gibi bağımsız bir kayıt olmalı ve onu silinmelidir, muhtemelen ana bilgisayar adınızı değiştirdiğiniz için artık hala server1.wxxxxxim.xyz olarak adlandırılmaktadır.

Bunu kaldırın, ardından mevcut ana bilgisayar adıyla yeni bir tane oluşturun, ardından her şey yolundaysa düzeltilmelidir.
Click to expand...
 

The service 'named' on server web1.wasyazilim.xyz is currently down​

This message has been automatically generated notifying you that the service named is currently down.
Richard G said:
Yes because I didn't say to change the hostname but the hostname record. I might have been a bit unclear.

Log in as administrator.
Go under adminstrator settings to DNS Administration.
Search for your server hostname there, should be a standalone record, so like server.wxxxxim.xyz and delete that one, probably since you changed your hostname it's now still called server1.wxxxxxim.xyz.

Remove that one, then create a new one with the current hostname, then it should be fixed if all is well.
Click to expand...
 
Please English only.

So you added the new server hostname which starts with web1.

What does die error say, still says server1? If yes, look for a record in DNS administration that says server1 and remove it.
 
So in DNS administration there is no entry with server.wasyazilim.xyz?
If not, then edit the /etc/named.conf file and remove the part for server.wasyazilim.xyz from there and restart named.
 
Richard G said:
So in DNS administration there is no entry with server.wasyazilim.xyz?
If not, then edit the /etc/named.conf file and remove the part for server.wasyazilim.xyz from there and restart named.
Click to expand...
// generated by named-bootconf.pl

options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;

allow-transfer { none; };
allow-recursion { localnets; };
listen-on-v6 { any; };
notify no;
};

//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

include "/etc/rndc.key";

zone "web1.wasyazilim.xyz" { type master; file "/var/named/web1.wasyazilim.xyz.db"; };
Click to expand...
 
Odd.. must be in there, this is the error:
Code: 
Jun 25 03:17:02 server bash: zone server.wasyazilim.xyz/IN: loading from master file /var/named/server.wasyazilim.xyz.db failed: file not found
If not in there, check the /var/named directory and remove the server.wasyazilim.xyz.db file if present.

Issue the command:
service named restart

If still not running, show me the new log from /var/log/messages file please.
 
Question, are you even running directadmin, because normally this is not on a /etc/named.conf file from directadmin.

Code: 
// generated by named-bootconf.pl
 
I have no idea how to do
Richard G said:
Question, are you even running directadmin, because normally this is not on a /etc/named.conf file from directadmin.

Code: 
// generated by named-bootconf.pl
Click to expand...
no such file exists

Richard G said:
Odd.. must be in there, this is the error:
Code: 
Jun 25 03:17:02 server bash: zone server.wasyazilim.xyz/IN: loading from master file /var/named/server.wasyazilim.xyz.db failed: file not found
If not in there, check the /var/named directory and remove the server.wasyazilim.xyz.db file if present.

Issue the command:
service named restart

If still not running, show me the new log from /var/log/messages file please.
Click to expand...
service named restart
Redirecting to /bin/systemctl restart named.service
Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.
 
You must log in or register to reply here.
Back
Top