Archief - dns probleem

G|N| · 30 dec 2004

ik ben al een tijdje aan het proberen dns fatsoenlijk te laten werken, maar het lukt me maar niet. normaal gezien alles goed ingesteld enzo

mijn domain is dus thuis.lan

Code:

server:/var/log# dig any thuis.lan

; <<>> DiG 9.2.1 <<>> any thuis.lan
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12728
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;thuis.lan.                     IN      ANY

;; AUTHORITY SECTION:
.                       6940    IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2004123000 1800 900 604800 86400

;; Query time: 12 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Dec 30 17:53:18 2004
;; MSG SIZE  rcvd: 102

betekent dit nu dat het werkt of niet?

als ik bv. google.com wil opzoeken lukt het precies wel

Code:

server:/var/log# nslookup www.google.com

Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
www.google.com  canonical name = www.google.akadns.net.
Name:   www.google.akadns.net
Address: 66.102.11.99
Name:   www.google.akadns.net
Address: 66.102.11.104

maar nslookup naar thuis.lan lukt dan weer niet

Code:

server:/var/log# nslookup thuis.lan

Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find thuis.lan: NXDOMAIN

ik zou echt niet weten hoe het komt

SiNTAX · 19 jan 2005

zonder uw /etc/named.conf en zone file, valt er niet veel over te zeggen he

G|N| · 19 jan 2005

Code:

server:~# cat /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

acl "dhcp-clients" {
        192.168.0.4/12
};

// prime the server with knowledge of the root servers
zone "." {
        type hint;
        file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
//  Because many of our users are uncomfortable receiving undelegated answers
//  from root or top level domains, other than a few for whom that behaviour
//  has been trusted and expected for quite some length of time, we have now
//  introduced the "root-delegations-only" feature which applies delegation-only//  logic to all top level domains, and to the root domain.  An exception list
//  should be specified, including "MUSEUM" and "DE", and any other top level
//  domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/named.conf.local";

Code:

server:~# cat /etc/bind/named.conf.local
//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
include "/etc/bind/zones.rfc1918";

zone "thuis.lan" {
        type master;
        file "/etc/bind/db.thuis";
        allow-update {"dhcp-clients"; };

zone "0.168.192.in-addr.arpa" in {
        type master;
        file "/etc/bind/db.192.168.0";
        allow-update {"dhcp-clients"; };

al de zone files nodig?

SiNTAX · 19 jan 2005

zone "thuis.lan" {
type master;
file "/etc/bind/db.thuis";
allow-update {"dhcp-clients"; };

Is het door het cut'n pasten.. of tel ik hier 2 x { en maar 1x } ?!

G|N| · 19 jan 2005

ok dat was idd al een fout, stom! :doh:

edit: het lijkt nog altijd niet te werken
maar ik zal eens rondkijken naar nog fouten in de zone files

SiNTAX · 19 jan 2005

Misschien best gewoon eens in /var/log/messages kijken naar foutmeldingen van 'named'.

servi · 19 jan 2005

toon ook eens wat er in
/etc/bind/db.thuis
staat, 9 / 10 op zit daar de fout.

G|N| · 20 jan 2005

Code:

server:~# cat /etc/bind/db.thuis
$TTL 7200       ;2 hours
                20041230 ;serial
                10800 ;refresh(3hours)
                3600 ;retry (1 hour)
                604800 ;expire (1 week)
                86400 ;minimum (1day)

                NS server.thuis.lan
server  A       192.168.0.3
router  A       192.168.0.1
proxy           CNAME   server

servi · 20 jan 2005

probeer dit eens :

$TTL 60

@ IN SOA thuis.lan. emailadres.thuis.lan. ( ; vooral dit haakje niet vergeten
2005012001 ;serial
10800 ;vermits ge geen secundaire NS hebt maken de volgende 3 waarde niets uit
3600 ;retry (1 hour)
604800 ;expire (1 week)
60 ; best zo laag mogelijk wanneer je aan het testen (maar ook weer niet te laag !)
)
IN NS server ; geen thuis.lan achterplakken de naam is relatief !
server IN A 192.168.0.3
router IN A 192.168.0.1
; over het algemeen raad men af om CNAME te gebruiken
proxy IN A 192.168.0.1

G|N| · 20 jan 2005

nee het werkt nog altijd niet

ad:

Starting domain name service: named.
server:~# nslookup thuis.lan
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find thuis.lan: NXDOMAIN

servi · 20 jan 2005

jamaar thuis.lan bestaat niet hé en je moet ook je nameserver opgeven

dus : nslookup router.thuis.lan 127.0.0.1 -d2

G|N| · 8 mrt 2005

kben eens terug begonnen met mijn bind te configureren:
kzit al een stap verder, maar werkt nog altijd niet.
error:

Code:

Mar  8 18:28:07 server named[7737]: USAGE 1110302887 1110302788 CPU=0.04u/0s CHILDCPU=0u/0s
Mar  8 18:28:07 server named[7737]: NSTATS 1110302887 1110302788 A=8
Mar  8 18:28:07 server named[7737]: XSTATS 1110302887 1110302788 RR=29 RNXD=16 RFwdR=10 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=17 SAns=24 SFwdQ=2 SDupQ=0 SErr=0 RQ=8 RIQ=0 RFwdQ=2 RDupQ=0 RTCP=0 SFwdR=10 SFail=0 SFErr=0 SNaAns=6 SNXD=0 RUQ=0 RURQ=0 RUXFR=0 RUUpd=0
Mar  8 18:28:09 server named[7743]: starting (/etc/bind/named.conf).  named 8.3.3-REL-NOESW Sun Jan  4 04:05:59 UTC 2004 ^Iroot@rootstrap:/host/space/tmp/mdz/debian/security/bind/bind-8.3.3/src/bin/named
Mar  8 18:28:09 server named[7743]: hint zone "" (IN) loaded (serial 0)
Mar  8 18:28:09 server named[7743]: master zone "localhost" (IN) loaded (serial 1)
Mar  8 18:28:09 server named[7743]: master zone "127.in-addr.arpa" (IN) loaded (serial 1)
Mar  8 18:28:09 server named[7743]: master zone "0.in-addr.arpa" (IN) loaded (serial 1)
Mar  8 18:28:09 server named[7743]: master zone "255.in-addr.arpa" (IN) loaded (serial 1)
Mar  8 18:28:09 server named[7743]: /etc/bind/db.thuis: Line 11: Unknown type: server.
Mar  8 18:28:09 server named[7743]: /etc/bind/db.thuis:11: Database error near (server)
Mar  8 18:28:09 server named[7743]: /etc/bind/db.thuis: Line 12: Unknown type: router.
Mar  8 18:28:09 server named[7743]: /etc/bind/db.thuis:12: Database error near (router)
Mar  8 18:28:09 server named[7743]: /etc/bind/db.thuis: Line 14: Unknown type: proxy.
Mar  8 18:28:09 server named[7743]: /etc/bind/db.thuis:14: Database error near (proxy)
Mar  8 18:28:09 server named[7743]: Zone "thuis.lan" (file /etc/bind/db.thuis): no NS RRs found at zone top
Mar  8 18:28:09 server named[7743]: master zone "thuis.lan" (IN) rejected due to errors (serial 2005012001)
Mar  8 18:28:09 server named[7743]: /etc/bind/db.192.168.0:2: Database error near ()
Mar  8 18:28:09 server named[7743]: /etc/bind/db.192.168.0:3: Database error near ()
Mar  8 18:28:09 server named[7743]: /etc/bind/db.192.168.0:4: Database error near ()
Mar  8 18:28:09 server named[7743]: /etc/bind/db.192.168.0:5: Database error near ()
Mar  8 18:28:09 server named[7743]: /etc/bind/db.192.168.0:6: Database error near ()
Mar  8 18:28:09 server named[7743]: /etc/bind/db.192.168.0:8: data "" outside zone "0.168.192.in-addr.arpa" (ignored)
Mar  8 18:28:09 server named[7743]: Zone "0.168.192.in-addr.arpa" (file /etc/bind/db.192.168.0): no SOA RR found
Mar  8 18:28:09 server named[7743]: master zone "0.168.192.in-addr.arpa" (IN) rejected due to errors (serial 0)
Mar  8 18:28:09 server named[7743]: /etc/bind/named.conf:75: cannot redefine zone '0.in-addr.arpa' class IN
Mar  8 18:28:09 server named[7743]: /etc/bind/named.conf:79: cannot redefine zone '255.in-addr.arpa' class IN
Mar  8 18:28:09 server named[7743]: listening on [127.0.0.1].53 (lo)
Mar  8 18:28:09 server named[7743]: listening on [192.168.0.3].53 (eth0)
Mar  8 18:28:09 server named[7743]: Forwarding source address is [0.0.0.0].1354
Mar  8 18:28:09 server named[7743]: hint zone "" (IN) loaded (serial 0)
Mar  8 18:28:09 server named[7744]: Ready to answer queries.

Code:

server:~# cat /etc/bind/db.thuis
$TTL 60

@ IN SOA thuis.lan. server.thuis.lan. ( ; vooral dit haakje niet vergeten
        2005012001 ;serial
        10800 ;vermits ge geen secundaire NS hebt maken de volgende 3 waarde niets uit
        3600 ;retry (1 hour)
        604800 ;expire (1 week)
        60 ; best zo laag mogelijk wanneer je aan het testen (maar ook weer niet te laag !)
)
IN NS server ; geen thuis.lan achterplakken de naam is relatief !
        server IN A 192.168.0.3
        router IN A 192.168.0.1
; over het algemeen raad men af om CNAME te gebruiken
        proxy IN A 192.168.0.3

Code:

server:~# cat /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind/README.Debian for information on the
// structure of BIND configuration files in Debian for BIND versions 8.2.1
// and later, *BEFORE* you customize this configuration file.
//

options {
        directory "/var/cache/bind";

        // 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 and later use an unprivileged
        // port by default.

        // query-source address * port 53;

        // If your ISP provided one or more IP addresses for stable
        // nameservers, you probably want to use them as forwarders.
        // Uncomment the following block, and insert the addresses replacing
        // the all-0's placeholder.

        // forwarders {
        //      0.0.0.0;
        // };
};

// reduce log verbosity on issues outside our control
logging {
        category lame-servers { null; };
        category cname { null; };
};

// prime the server with knowledge of the root servers
zone "." {
        type hint;
        file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};

// add entries for other zones below here

zone "thuis.lan" in {
        type master;
        file "/etc/bind/db.thuis";

};
zone "0.168.192.in-addr.arpa" in {
        type master;
        file "/etc/bind/db.192.168.0";
};
zone "0.in-addr.arpa" in {
        type master;
        file "dummy";
};
zone "255.in-addr.arpa" in {
        type master;
        file "dummy";
};

MrFreeze · 10 mrt 2005

@ vergeten

Code:

$TTL 60

@ IN SOA thuis.lan. server.thuis.lan. ( 
        2005012001 ; serial
        10800 ; refresh
        3600 ; retry
        604800 ; expire
        60 ; ttl
)

@       IN      NS      server
server  IN      A       192.168.0.3
router  IN      A       192.168.0.1
proxy   IN      A       192.168.0.3

Code:

[root@fedora named]# nslookup server.thuis.lan
Server:         127.0.0.1
Address:        127.0.0.1#53

Name:   server.thuis.lan
Address: 192.168.0.3

G|N| · 11 mrt 2005

merci het werkt

gaat het ook om bv. mail.thuis.lan te koppelen aan server.thuis.lan/webmail?

MrFreeze · 11 mrt 2005

mx record toevoegen

Code:

thuis.lan.     IN      MX      10 server.thuis.lan.

de volgende stap is de mail server configureren, maar daar ben ik zelf nog niet aan begonnen

G|N| · 11 mrt 2005

mijn mailserver is al geconfigureerd, maar de bedoeling is dat http://mail.thuis.lan verwijst naar http://192.168.0.3/webmail

MrFreeze · 11 mrt 2005

mail.thuis.lan laten verwijzen naar 192.168.0.3 in de dns configuratie, en een
virtual host toevoegen in uw apache configuratie

Code:

<VirtualHost *>
    ServerAdmin [email protected]
    DocumentRoot /usr/share/squirrelmail
    ServerName mail.thuis.net
</VirtualHost>

http://httpd.apache.org/docs/vhosts/name-based.html

Archief - dns probleem

G|N|

Legacy Member

SiNTAX

Legacy Member

G|N|

Legacy Member

SiNTAX

Legacy Member

G|N|

Legacy Member

SiNTAX

Legacy Member

servi

Legacy Member

G|N|

Legacy Member

servi

Legacy Member

G|N|

Legacy Member

servi

Legacy Member

G|N|

Legacy Member

MrFreeze

Legacy Member

G|N|

Legacy Member

MrFreeze

Legacy Member

G|N|

Legacy Member

MrFreeze

Legacy Member