HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Server Operation (http://www.howtoforge.com/forums/forumdisplay.php?f=5)
-   -   Please help me whit bind9 (http://www.howtoforge.com/forums/showthread.php?t=13473)

astra2000 17th June 2007 03:33

Please help me whit bind9
 
Hello party peopel, i'm tryng config the bind9 (first time)
and i think is all ok but i can't ping the adress...

check this out:


on /etc/bind/zones/master

i have 2 files:
- tuga4u.com.db
- 192.168.1.rev

on the file tuga4u.com.db is this:
Quote:

$TTL 604800
@ IN SOA tuga4u.com. admin.tuga4u.com. (
2007061101 ; Serial
7200 ; Refresh
120 ; Retry
2419200 ; Expire
604800) ; Default TTL

;
IN NS dns.tuga4u.com.
IN A 192.168.1.103
IN NS ns
IN NS ns1.tuga4u.com
IN NS ns2.tuga4u.com




IN MX 10 mail.tuga4u.com.
@ IN A 192.168.1.103
boss IN A 192.168.1.103
www IN A 192.168.1.103
news IN A 192.168.1.103
mail IN A 192.168.1.103
dns IN A 192.168.1.103
dns2 IN A 192.168.1.103
(192.168.1.103 is the server where bind9 is executed)

On 192.168.1.rev is this:
Quote:

$TTL 1d ;
$ORIGIN 1.168.192.IN-ADDR.ARPA.
@ IN SOA ns1.tuga4u.com. info.tuga4u.com. (
2007011501
7200
120
2419200
604800
)
IN NS ns1.tuga4utuga4u.com.
IN NS ns2.tuga4u.com.
1 IN PTR ns1.tuga4u.com.
2 IN PTR ns2.tuga4u.com.




on /etc/bind i have this files:

-db.0
-db.127
-db.125
-db.empty
-db.local
-db.root
-named.conf
-named.conf.local
-named.conf.options
-rndc.key
-zones.rfc1918

-------------------------------------------------------------------

now, wenn i ping the host:

Quote:

ping ns1.tuga4u.com
Quote:

ping: unknown host ns1.tuga4u.com


ideas???

astra2000 17th June 2007 04:00

on var/log/daemon.log i have something like this:


Quote:

Jun 16 02:10:06 debian named[11679]: starting BIND 9.4.1 -u bind
Jun 16 02:10:06 debian named[11679]: found 2 CPUs, using 2 worker threads
Jun 16 02:10:06 debian named[11679]: loading configuration from '/etc/bind/named.conf'
Jun 16 02:10:06 debian named[11679]: listening on IPv6 interfaces, port 53
Jun 16 02:10:06 debian named[11679]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 16 02:10:06 debian named[11679]: listening on IPv4 interface eth0, 192.168.1.103#53
Jun 16 02:10:06 debian named[11679]: automatic empty zone: 254.169.IN-ADDR.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty zone: 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.0.IP6.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty 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
Jun 16 02:10:06 debian named[11679]: automatic empty zone: D.F.IP6.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty zone: 8.E.F.IP6.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty zone: 9.E.F.IP6.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty zone: A.E.F.IP6.ARPA
Jun 16 02:10:06 debian named[11679]: automatic empty zone: B.E.F.IP6.ARPA
Jun 16 02:10:06 debian named[11679]: command channel listening on 127.0.0.1#953
Jun 16 02:10:06 debian named[11679]: command channel listening on ::1#953
Jun 16 02:10:06 debian named[11679]: zone 0.in-addr.arpa/IN: loaded serial 1
Jun 16 02:10:06 debian named[11679]: zone 127.in-addr.arpa/IN: loaded serial 1
Jun 16 02:10:06 debian named[11679]: /etc/bind/zones/master/192.168.1.rev:13: TTL set to prior TTL (1)
Jun 16 02:10:06 debian named[11679]: zone 1.168.192.IN-ADDR.ARPA/IN: loaded serial 2007011501
Jun 16 02:10:06 debian named[11679]: zone 255.in-addr.arpa/IN: loaded serial 1
Jun 16 02:10:06 debian named[11679]: zone tuga4u.com/IN: loaded serial 2007061101
Jun 16 02:10:06 debian named[11679]: zone localhost/IN: loaded serial 1
Jun 16 02:10:06 debian named[11679]: running
Jun 16 02:10:06 debian named[11679]: zone 1.168.192.IN-ADDR.ARPA/IN: sending notifies (serial 2007011501)
Jun 16 02:10:06 debian named[11679]: zone tuga4u.com/IN: sending notifies (serial 2007061101)

on /etc/resolv.conf

Quote:

search Cablecom
nameserver 62.2.17.60
nameserver 62.2.24.158
nameserver 62.2.17.61

falko 17th June 2007 15:48

Does
Code:

dig @localhost ns1.tuga4u.com
work?

astra2000 18th June 2007 01:18

debian:/home/virus# dig @localhost ns1.tuga4u.com
bash: dig: command not found

edge 18th June 2007 01:26

Quote:

Originally Posted by astra2000
debian:/home/virus# dig @localhost ns1.tuga4u.com
bash: dig: command not found

Use dig localhost ns1.tuga4u.com (I think falko had a late night)

Also.. Your DNS should not have LAN IP's (192.168.1.103) in it,exept if you want to use it on your LAN only.

falko 18th June 2007 13:06

Quote:

Originally Posted by edge
Use dig localhost ns1.tuga4u.com (I think falko had a late night)

No,
Code:

dig @localhost ns1.tuga4u.com
is correct.

Please install dnsutils:
Code:

apt-get install dnsutils
and run
Code:

dig @localhost ns1.tuga4u.com
again.

astra2000 18th June 2007 17:14

Here is a quote

Quote:

debian:/home/virus# dig @localhost ns1.tuga4u.com

; <<>> DiG 9.4.1 <<>> @localhost ns1.tuga4u.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 21533
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ns1.tuga4u.com. IN A

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Jun 18 16:06:49 2007
;; MSG SIZE rcvd: 32

astra2000 18th June 2007 17:18

Quote:

Originally Posted by edge
Use dig localhost ns1.tuga4u.com (I think falko had a late night)

Also.. Your DNS should not have LAN IP's (192.168.1.103) in it,exept if you want to use it on your LAN only.


whitch io should i met there???
my external ip ???

falko 19th June 2007 15:03

Quote:

Originally Posted by astra2000
my external ip ???

Yes, use public IP addresses, otherwise nobody from outside your LAN can access your web sites.

falko 19th June 2007 15:04

Quote:

Originally Posted by astra2000
Here is a quote

There's no ANSWER section, which means that you local nameserver isn't configured to resolve ns1.tuga4u.com.


All times are GMT +2. The time now is 15:14.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.