Topic: misconfigured DNS

[perler]

hi,

sometime ago i seem to have misconfigured my dns server.

server name: orbit
domain: patsplanet.net
subnet: 192.168.0.x
dhcp is on..

these are the symptomps:

from a windows pc in the domain:

nslookup yahoo.com
*** Can't find server name for address 192.168.0.254: Non-existent domain
*** Can't find server name for address 192.168.0.254: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.0.254

Non-authoritative answer:
Name:    yahoo.com
Addresses:  66.94.234.13, 216.109.112.135

from the server itself:

[root@orbit etc]# host localhost
Host localhost not found: 3(NXDOMAIN)
[root@orbit etc]# host orbit
Host orbit not found: 3(NXDOMAIN)
[root@orbit etc]# host orbit.patsplanet.net
Host orbit.patsplanet.net not found: 3(NXDOMAIN)
[root@orbit etc]# host patsplanet.net
patsplanet.net has address 217.225.249.169
[root@orbit etc]#

the last ip is the one i get from my ISP.

so, for me it looks like the reverse lookup is not working. here are some snippets from /home/dns/etc/named.conf:

options {
        directory "/var/named";
        forwarders 217.237.149.225; 217.237.151.97;
        listen-on { 127.0.0.1; 192.168.0.254; };

btw, is there a way to make the forwarders dynamic? my ISP gives me a new IP every 24h and also the DNS might change..

but here are the important parts:

#----------------------------------------
# localhost PTR record
#----------------------------------------

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

zone "localhost." {
        type master;
        file "named.localhost";
};
#----------------------------------------
# local network PTR records
#----------------------------------------

zone "0.168.192.in-addr.arpa."
{
        type master;
        file "named.localnetwork";
};

zone "patsplanet.net"
{
    type master;
    file "db.patsplanet.net";
};

and here is a listing from /home/dns/var/named

[root@orbit named]# ls -1 /home/dns/var/named
db.patsplanet.net
named.localnetwork

somehow i miss named.local and named.localhost ?

all this is in sme 6.0 (unsupported developers release. i didn't upgrade to 6.0.1 because i don't want to break things.

the problem with this configuraion is, that althou IP's are resolved from windows workstations, it is a bit slow because windows first tries to resolve the dns' hostname and fails..

PAT

[hardijs]

hi,

sometime ago i seem to have misconfigured my dns server.
....

so, for me it looks like the reverse lookup is not working. here are some snippets from /home/dns/etc/named.conf:

Am I correct that you are configuring named under SME vers 6?????

well - since version 6 SME uses tinydns and dnscache combo
say under v6 I get

root@sargs root]# service named status
named: unrecognized service
[root@sargs root]# service tinydns status
/service/tinydns: up (pid 1645) 15671 seconds, normally down

don't ask me why tinydns - just as I grasped the basic concepts under named I just had to switch to tinydns - no harm was done and it works as well.
somebody said something about security....


somebody having experiernced the beta6 may help you better tho I would advise you to reconsider your [not]upgrading to the latest version...

[perler]

hi,

sometime ago i seem to have misconfigured my dns server.
....

so, for me it looks like the reverse lookup is not working. here are some snippets from /home/dns/etc/named.conf:

Am I correct that you are configuring named under SME vers 6?????

well - since version 6 SME uses tinydns and dnscache combo
say under v6 I get

root@sargs root]# service named status
named: unrecognized service
[root@sargs root]# service tinydns status
/service/tinydns: up (pid 1645) 15671 seconds, normally down

yep, that was the problem, both were running in parallel and i think named was misconfigured and run first so tinydnds couldn't bind to port 53 which left  the system in an uncomplete state..

don't ask me why tinydns - just as I grasped the basic concepts under named I just had to switch to tinydns - no harm was done and it works as well.
somebody said something about security....

yep, it's from the coder of qmail which is my mta of choice because it is written towards extrem security. a good choice, vbut the should have removed the /etc/inti.d/named file

PAT


PAT