05. september 2002 - 17:40
Der er
21 kommentarer og 1 løsning
DNS problem
Hej Jeg har et problem med min DNS på min linux server. Jeg får ikke svar på nogen queries ude på internettet. Jeg vil gerne køre en DNS cache til mit lokale netværk. Hosts: # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 Vision localhost.localdomain localhost resolv.conf: nameserver 127.0.0.1 nameserver 194.239.134.83 nameserver 193.162.153.164 named.conf: options { /* Hvor er filerne med DNS-opsætning */ directory "/var/named"; /* Indsaet 1-3 forwarder nameservere */ /* Brug dem fra din ISP og indsaet IP-adresserne */ /* i stedet for NNN.NNN.NNN.NNN og MMM.MMM.MMM.MMM */ forwarders { 194.239.134.83; 193.162.153.164; }; /* Lyt på DNS-forespørgsler til to IP-adresser */ listen-on { 192.168.0.10; 127.0.0.1 ; }; /* Udkommenter følgende linje hvis dit domæne er kendt på internettet */ notify no; }; logging { category lame-servers { null; }; category cname { null; }; }; zone "." in { type hint; file "root.cache"; }; zone "0.0.127.in-addr.arpa" in { type master; file "127.0.0.rev"; }; zone "0.168.192.in-addr.arpa" in { type master; file "192.168.0.rev"; };
Annonceindlæg tema
05. september 2002 - 17:41
#1
Hvad er problemet? Jeg har forsøgt at helt lade være med at køre named, men den kan ikke lave queries alligevel.
05. september 2002 - 19:31
#2
Hvad siger en
# dig
www.yahoo.com ???
05. september 2002 - 19:47
#3
[root@Vision root]# dig
www.yahoo.com ; <<>> DiG 9.2.0 <<>>
www.yahoo.com ;; global options: printcmd
;; connection timed out; no servers could be reached
05. september 2002 - 19:50
#4
Du får lige mine zone filer, det er vist nogen jeg har fundet på SSLUG: 127.0.0.rev: N SOA ns.intranet. hostmaster.intranet. ( 1999102400 ; serial number 60000 ; refresh (1 day) 3600 ; retry (1 hour) 2600000 ; expire (1 month) 60000 ; minimum (1 day) ) ; ; DNS-serveren for denne zone: ; IN NS ns.intranet. ; ; Reverse mappings: ; 1 IN PTR localhost. 192.168.0.rev N SOA ns.intranet. hostmaster.intranet. ( 1999102400 ; serial number 60000 ; refresh (1 day) 3600 ; retry (1 hour) 2600000 ; expire (1 month) 60000 ; minimum (1 day) ) ; ; DNS-serveren for denne zone: ; IN NS ns.intranet. ; ; Reverse mappings: ; 1 IN PTR localhost. root.cache: . 3600000 NS E.ROOT-SERVERS.NET. E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10 ; ; formerly NS.ISC.ORG ; . 3600000 NS F.ROOT-SERVERS.NET. F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241 ; ; formerly NS.NIC.DDN.MIL ; . 3600000 NS G.ROOT-SERVERS.NET. G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4 ; ; formerly AOS.ARL.ARMY.MIL ; . 3600000 NS H.ROOT-SERVERS.NET. H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53 ; ; formerly NIC.NORDU.NET ; . 3600000 NS I.ROOT-SERVERS.NET. I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17 ; ; temporarily housed at NSI (InterNIC) ; . 3600000 NS J.ROOT-SERVERS.NET. J.ROOT-SERVERS.NET. 3600000 A 198.41.0.10 ; ; temporarily housed at NSI (InterNIC) ; . 3600000 NS K.ROOT-SERVERS.NET. K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129 ; ; temporarily housed at ISI (IANA) ; . 3600000 NS L.ROOT-SERVERS.NET. L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12 ; ; temporarily housed at ISI (IANA) ; . 3600000 NS M.ROOT-SERVERS.NET. M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33 ; End of File
05. september 2002 - 19:53
#5
ok.. problemet er at du bruger forwarders. Dem har jeg ikke så meget forstand på.. Hvis du har en root.hints fil - så prøv at fjerne forwarden i din config. Kan ikke lige overskue om det kan være dem der laver problemer.
Jeg har skrevet en guide til RedHat som vi næsten skal til at udgive på
www.lws.dk - men jeg vil gerne sende den til dig, hvis du vil se den. Smid en e-mail hvis du er intereseret.
05. september 2002 - 19:54
#6
-- når jeg siger problemet er at du bruger forwaders - er det ikke sikkert det er dem der giver problemer - jeg kender bare ikke så meget til dem - så jeg kan ikke lige overskue om det kan være dem der snyder.
05. september 2002 - 20:00
#7
er der evt noget at finde her: # cat /var/log/messages | grep "named"
05. september 2002 - 20:05
#8
sep 4 22:45:12 Vision named: named nedlukning failed Sep 4 22:45:15 Vision named[5706]: starting BIND 9.2.0 -u named Sep 4 22:45:15 Vision named[5706]: using 1 CPU Sep 4 22:45:15 Vision named[5709]: loading configuration from '/etc/named.conf' Sep 4 22:45:16 Vision named[5709]: /etc/named.conf:2: unknown option 'ptions' Sep 4 22:45:16 Vision named[5709]: loading configuration: failure Sep 4 22:45:16 Vision named[5709]: exiting (due to fatal error) sep 4 22:45:16 Vision named: named opstart succeeded sep 4 22:45:20 Vision named: named nedlukning failed sep 4 22:52:49 Vision named: named nedlukning failed Sep 4 22:52:52 Vision named[5889]: starting BIND 9.2.0 -u named Sep 4 22:52:52 Vision named[5889]: using 1 CPU Sep 4 22:52:52 Vision named[5892]: loading configuration from '/etc/named.conf' sep 4 22:52:52 Vision named: named opstart succeeded Sep 4 22:52:52 Vision named[5892]: no IPv6 interfaces found Sep 4 22:52:52 Vision named[5892]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 4 22:52:52 Vision named[5892]: listening on IPv4 interface eth1, 192.168.0.10#53 Sep 4 22:52:52 Vision named[5892]: dns_master_load: root.cache:1: unknown RR type 'file' Sep 4 22:52:52 Vision named[5892]: could not configure root hints from 'root.cache': unknown class/type Sep 4 22:52:52 Vision named[5892]: loading configuration: unknown class/type Sep 4 22:52:52 Vision named[5892]: exiting (due to fatal error) sep 4 22:52:54 Vision named: named nedlukning failed Sep 4 22:52:57 Vision named[5943]: starting BIND 9.2.0 -u named Sep 4 22:52:57 Vision named[5943]: using 1 CPU Sep 4 22:52:58 Vision named[5946]: loading configuration from '/etc/named.conf' sep 4 22:52:58 Vision named: named opstart succeeded Sep 4 22:52:58 Vision named[5946]: no IPv6 interfaces found Sep 4 22:52:58 Vision named[5946]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 4 22:52:58 Vision named[5946]: listening on IPv4 interface eth1, 192.168.0.10#53 Sep 4 22:52:58 Vision named[5946]: dns_master_load: root.cache:1: unknown RR type 'file' Sep 4 22:52:58 Vision named[5946]: could not configure root hints from 'root.cache': unknown class/type Sep 4 22:52:58 Vision named[5946]: loading configuration: unknown class/type Sep 4 22:52:58 Vision named[5946]: exiting (due to fatal error) sep 4 22:53:02 Vision named: named nedlukning failed Sep 4 22:53:02 Vision named[5980]: starting BIND 9.2.0 -u named Sep 4 22:53:02 Vision named[5980]: using 1 CPU Sep 4 22:53:02 Vision named[5983]: loading configuration from '/etc/named.conf' sep 4 22:53:02 Vision named: named opstart succeeded Sep 4 22:53:02 Vision named[5983]: no IPv6 interfaces found Sep 4 22:53:02 Vision named[5983]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 4 22:53:02 Vision named[5983]: listening on IPv4 interface eth1, 192.168.0.10#53 Sep 4 22:53:02 Vision named[5983]: dns_master_load: root.cache:1: unknown RR type 'file' Sep 4 22:53:02 Vision named[5983]: could not configure root hints from 'root.cache': unknown class/type Sep 4 22:53:02 Vision named[5983]: loading configuration: unknown class/type Sep 4 22:53:02 Vision named[5983]: exiting (due to fatal error) sep 4 23:07:35 Vision named: named nedlukning failed Sep 4 23:07:35 Vision named[6047]: starting BIND 9.2.0 -u named Sep 4 23:07:35 Vision named[6047]: using 1 CPU Sep 4 23:07:35 Vision named[6050]: loading configuration from '/etc/named.conf' sep 4 23:07:35 Vision named: named opstart succeeded Sep 4 23:07:35 Vision named[6050]: no IPv6 interfaces found Sep 4 23:07:35 Vision named[6050]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 4 23:07:35 Vision named[6050]: listening on IPv4 interface eth1, 192.168.0.10#53 Sep 4 23:07:35 Vision named[6050]: command channel listening on 127.0.0.1#953 Sep 4 23:07:35 Vision named[6050]: /etc/named.conf:24: unknown logging category 'cname' ignored Sep 4 23:07:35 Vision named[6050]: 127.0.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 4 23:07:35 Vision named[6050]: dns_master_load: 127.0.0.rev:1: N.0.0.127.in-addr.arpa: not at top of zone Sep 4 23:07:36 Vision named[6050]: zone 0.0.127.in-addr.arpa/IN: loading master file 127.0.0.rev: not at top of zone Sep 4 23:07:36 Vision named[6050]: 192.168.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 4 23:07:36 Vision named[6050]: dns_master_load: 192.168.0.rev:18: N.0.168.192.in-addr.arpa: not at top of zone Sep 4 23:07:36 Vision named[6050]: zone 0.168.192.in-addr.arpa/IN: loading master file 192.168.0.rev: not at top of zone Sep 4 23:07:36 Vision named[6050]: running Sep 4 23:07:36 Vision named[6050]: shutting down Sep 4 23:07:36 Vision named[6050]: stopping command channel on 127.0.0.1#953 Sep 4 23:07:36 Vision named[6050]: no longer listening on 127.0.0.1#53 Sep 4 23:07:36 Vision named[6050]: no longer listening on 192.168.0.10#53 Sep 4 23:07:36 Vision named[6047]: exiting sep 4 23:07:37 Vision named: named nedlukning succeeded Sep 4 23:07:37 Vision named[6082]: starting BIND 9.2.0 -u named Sep 4 23:07:37 Vision named[6082]: using 1 CPU Sep 4 23:07:37 Vision named[6085]: loading configuration from '/etc/named.conf' sep 4 23:07:37 Vision named: named opstart succeeded Sep 4 23:07:37 Vision named[6085]: no IPv6 interfaces found Sep 4 23:07:37 Vision named[6085]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 4 23:07:37 Vision named[6085]: listening on IPv4 interface eth1, 192.168.0.10#53 Sep 4 23:07:37 Vision named[6085]: command channel listening on 127.0.0.1#953 Sep 4 23:07:37 Vision named[6085]: /etc/named.conf:24: unknown logging category 'cname' ignored Sep 4 23:07:37 Vision named[6085]: 127.0.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 4 23:07:37 Vision named[6085]: dns_master_load: 127.0.0.rev:1: N.0.0.127.in-addr.arpa: not at top of zone Sep 4 23:07:37 Vision named[6085]: zone 0.0.127.in-addr.arpa/IN: loading master file 127.0.0.rev: not at top of zone Sep 4 23:07:37 Vision named[6085]: 192.168.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 4 23:07:37 Vision named[6085]: dns_master_load: 192.168.0.rev:18: N.0.168.192.in-addr.arpa: not at top of zone Sep 4 23:07:37 Vision named[6085]: zone 0.168.192.in-addr.arpa/IN: loading master file 192.168.0.rev: not at top of zone Sep 4 23:07:37 Vision named[6085]: running Sep 5 16:00:07 Vision named[6085]: shutting down Sep 5 16:00:07 Vision named[6085]: stopping command channel on 127.0.0.1#953 Sep 5 16:00:07 Vision named[6085]: no longer listening on 127.0.0.1#53 Sep 5 16:00:07 Vision named[6085]: no longer listening on 192.168.0.10#53 Sep 5 16:00:07 Vision named[6082]: exiting sep 5 16:00:07 Vision named: named nedlukning succeeded Sep 5 16:33:48 Vision named[7785]: starting BIND 9.2.0 -u named Sep 5 16:33:48 Vision named[7785]: using 1 CPU Sep 5 16:33:48 Vision named[7788]: loading configuration from '/etc/named.conf' sep 5 16:33:48 Vision named: named opstart succeeded Sep 5 16:33:48 Vision named[7788]: no IPv6 interfaces found Sep 5 16:33:48 Vision named[7788]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 5 16:33:48 Vision named[7788]: listening on IPv4 interface eth1, 192.168.0.10#53 Sep 5 16:33:48 Vision named[7788]: command channel listening on 127.0.0.1#953 Sep 5 16:33:48 Vision named[7788]: /etc/named.conf:24: unknown logging category 'cname' ignored Sep 5 16:33:48 Vision named[7788]: 127.0.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 5 16:33:48 Vision named[7788]: dns_master_load: 127.0.0.rev:1: N.0.0.127.in-addr.arpa: not at top of zone Sep 5 16:33:48 Vision named[7788]: zone 0.0.127.in-addr.arpa/IN: loading master file 127.0.0.rev: not at top of zone Sep 5 16:33:48 Vision named[7788]: 192.168.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 5 16:33:48 Vision named[7788]: dns_master_load: 192.168.0.rev:18: N.0.168.192.in-addr.arpa: not at top of zone Sep 5 16:33:48 Vision named[7788]: zone 0.168.192.in-addr.arpa/IN: loading master file 192.168.0.rev: not at top of zone Sep 5 16:33:48 Vision named[7788]: running Sep 5 17:13:24 Vision named[7788]: shutting down Sep 5 17:13:24 Vision named[7788]: stopping command channel on 127.0.0.1#953 Sep 5 17:13:24 Vision named[7788]: no longer listening on 127.0.0.1#53 Sep 5 17:13:24 Vision named[7788]: no longer listening on 192.168.0.10#53 Sep 5 17:13:24 Vision named[7785]: exiting sep 5 17:13:25 Vision named: named nedlukning succeeded Sep 5 17:13:25 Vision named[7935]: starting BIND 9.2.0 -u named Sep 5 17:13:25 Vision named[7935]: using 1 CPU Sep 5 17:13:25 Vision named[7938]: loading configuration from '/etc/named.conf' sep 5 17:13:25 Vision named: named opstart succeeded Sep 5 17:13:25 Vision named[7938]: no IPv6 interfaces found Sep 5 17:13:25 Vision named[7938]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 5 17:13:25 Vision named[7938]: listening on IPv4 interface eth1, 192.168.0.10#53 Sep 5 17:13:25 Vision named[7938]: command channel listening on 127.0.0.1#953 Sep 5 17:13:25 Vision named[7938]: /etc/named.conf:24: unknown logging category 'cname' ignored Sep 5 17:13:25 Vision named[7938]: 127.0.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 5 17:13:25 Vision named[7938]: dns_master_load: 127.0.0.rev:1: N.0.0.127.in-addr.arpa: not at top of zone Sep 5 17:13:25 Vision named[7938]: zone 0.0.127.in-addr.arpa/IN: loading master file 127.0.0.rev: not at top of zone Sep 5 17:13:25 Vision named[7938]: 192.168.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 5 17:13:25 Vision named[7938]: dns_master_load: 192.168.0.rev:18: N.0.168.192.in-addr.arpa: not at top of zone Sep 5 17:13:25 Vision named[7938]: zone 0.168.192.in-addr.arpa/IN: loading master file 192.168.0.rev: not at top of zone Sep 5 17:13:25 Vision named[7938]: running
05. september 2002 - 20:12
#9
Det hjalp ikke at slå forwarders'ne fra. Jeg tror ikke fejlen ligger gemt i Named. Hvor kan problemet ellers være opstået?
05. september 2002 - 20:14
#10
...Jeg har jo også sat mine rigtige DNS servere til henholdsvis sekundære og tertiære DNS servere i resolv.conf - burde den så ikke prøve dem ved fejl på den første? Er der en log jeg måske kan få noget ud af at kigge på?
05. september 2002 - 20:25
#11
Tjaeee.. Der er jo noget galt med stort set alle dine zone filer.: Sep 5 17:13:25 Vision named[7938]: /etc/named.conf:24: unknown logging category 'cname' ignored Sep 5 17:13:25 Vision named[7938]: 127.0.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 5 17:13:25 Vision named[7938]: dns_master_load: 127.0.0.rev:1: N.0.0.127.in-addr.arpa: not at top of zone Sep 5 17:13:25 Vision named[7938]: zone 0.0.127.in-addr.arpa/IN: loading master file 127.0.0.rev: not at top of zone Sep 5 17:13:25 Vision named[7938]: 192.168.0.rev:1: no TTL specified; using SOA MINTTL instead Sep 5 17:13:25 Vision named[7938]: dns_master_load: 192.168.0.rev:18: N.0.168.192.in-addr.arpa: not at top of zone Sep 5 17:13:25 Vision named[7938]: zone 0.168.192.in-addr.arpa/IN: loading master file 192.168.0.rev: not at top of zone Jeg ved ikke om det har den store betydning.. Men det bør da rettes til som det første i alle tilfælde. Du har vel ikke noget ipchains/iptables som har lukket for 53 på Input
05. september 2002 - 20:31
#12
Jeg prøver lige at se om ikke jeg kan få rettet det. Der er fuld adgang på loopback interfacet og min iptables giver fuld adgang indefra til internettet. Jeg har ikke lige et konkret script jeg kan vise dig, da det er noget jeg har konfigureret lidt hen af vejen, desværre. Men jeg kan lige prøve at lukke iptables ned og se om det virker.
05. september 2002 - 20:33
#13
Ja jeg tænker på om f.eks. Input DROP kan have den effekt! Jeg ved det ikke betragt det som et skud i tågen :)
05. september 2002 - 21:12
#14
Årrrh for hel.... da osse. Dum fejl. Det var firewall'en der var problemet, havde lige glemt at opdatere mit script siden sidste install. Tak for hjælpen!
05. september 2002 - 21:59
#15
Jamen selv tak - fint at problemet blev lokaliseret så.. Husk at rette til så du ikke får alle de fejl.. Test desuden med 2x dig kammandoen om den henter fra 127.0.0.1 - det er ret væsentligt. Du vil kunne se det hvis den henter fra din udbyder så vil tiden ligge på 15-25 Msec - men lokalt 0-5 Msec
05. september 2002 - 22:03
#16
; <<>> DiG 9.2.0 <<>> localhost ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54346 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;localhost. IN A ;; AUTHORITY SECTION: . 10800 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2002090500 1800 900 604800 86400 ;; Query time: 168 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Thu Sep 5 22:06:18 2002 ;; MSG SIZE rcvd: 102 Jeg mangler nok at rette mine zoner lidt til
05. september 2002 - 22:06
#17
er det 2. svar? Det er først efter 2. gang med dig på samme domain du skal se resultatet. Ovenstående er meget normalt efter første gang.
05. september 2002 - 22:08
#18
; <<>> DiG 9.2.0 <<>> localhost ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24263 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;localhost. IN A ;; AUTHORITY SECTION: . 10466 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2002090500 1800 900 604800 86400 ;; Query time: 13 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Thu Sep 5 22:11:52 2002 ;; MSG SIZE rcvd: 102
05. september 2002 - 22:09
#19
Det var anden gang
05. september 2002 - 22:14
#20
ups.. jeg havde heller ikke set det var localhost :ø] Men det burde være <2msec ---- ??? Men ret dine filer til så du ikke har fejlene længere, så kan det være det virker.
05. september 2002 - 22:15
#21
; <<>> DiG 9.2.1 <<>> localhost ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58407 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;localhost. IN A ;; AUTHORITY SECTION: . 10798 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2002090500 1800 900 604800 86400 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Thu Sep 5 22:22:01 2002 ;; MSG SIZE rcvd: 102
05. september 2002 - 22:16
#22
Det var min dig localhost :ø]
IT-kurser om Microsoft 365, sikkerhed, personlig vækst, udvikling, digital markedsføring, grafisk design, SAP og forretningsanalyse.