s5780003:/var/lib/named/master # cat inet1.local
$TTL 2d
@ IN SOA s5780003.inet1.local. root.s5780003.inet1.local. (
2009122501 ; serial
3h ; refresh
1h ; retry
1w ; expiry
1d ) ; minimum
inet1.local. IN NS ns2.inet1.local.
inet1.local. IN NS ns1.inet1.local.
inet1.local. IN MX 1 mail.inetmining.com.
ns1.inet1.local. IN A 192.168.1.5
ns2.inet1.local. IN A 192.168.1.5
inetmining.com. IN A 71.41.72.28
www IN A 192.168.1.5
ftp IN A 192.168.1.5
www.inetmining.com. IN A 71.41.72.28
mail IN A 192.168.1.5
s5780003.inet1.local. IN A 192.168.1.5
s5780003 IN A 192.168.1.5
I bit difficult to say. My experience is a few years old. This looks like a zone file to be used by bind. And the zone seems to be inet1.local (name of the file). Then why do you still have all those inet1.local. in the file itself.
You seem to have systems in a complete different domain (inetmining.com) in this file.
Where is the zone file for the reversed lookup of the zone 1.168.192.in-addr.arpa with the PTR records?
You have the different names in A records for the same IP address. This should be aliases (CNAME).
made some changes to the zone file not sure if it is working entirely? I think I have it setup and working correctly but not sure. Any ideas for testing, to know if it is correct would greatly be appreciated. Thanks
s5780003:~ # cd /var/lib/named/master
s5780003:/var/lib/named/master # cat inet1.local
$TTL 2d
@ IN SOA ns1.inet1.local. root.inet1.local. (
2009122508 ; serial
3h ; refresh
1h ; retry
1w ; expiry
1d ) ; minimum
inet1.local. IN MX 1 mail.inetmining.com.
inet1.local. IN NS ns1.inet1.local.
ns1.inet1.local. IN A 192.168.1.5
inetmining.com. IN A 192.168.1.5
www IN A 192.168.1.5
ftp IN A 192.168.1.5
www.inetmining.com. IN A 192.168.1.5
mail IN A 192.168.1.5
s5780003.inet1.local. IN A 192.168.1.5
inet1.local. IN A 192.168.1.5
s5780003:/var/lib/named/master # cat 5.1.168.192.in-addr.arpa
$TTL 2d
@ IN SOA ns1.inet1.local. root.inet1.local. (
2009122520 ; serial
3h ; refresh
1h ; retry
1w ; expiry
1d ) ; minimum
5.1.168.192.in-addr.arpa. IN NS ns1.inet1.local.
5.1.168.192.in-addr.arpa. IN PTR ns1.inet1.local.
5.1.168.192.in-addr.arpa. IN PTR inetmining.com.
5.1.168.192.in-addr.arpa. IN PTR www.inet1.local.
5.1.168.192.in-addr.arpa. IN PTR ftp.inet1.local.
5.1.168.192.in-addr.arpa. IN PTR www.inetmining.com.
5.1.168.192.in-addr.arpa. IN PTR mail.inet1.local.
5.1.168.192.in-addr.arpa. IN PTR s5780003.inet1.local.
5.1.168.192.in-addr.arpa. IN PTR inet1.local.
s5780003:/var/lib/named/master # dig @localhost s5780003
^Cs5780003:/var/lib/named/master # dig @localhost s5780003
; <<>> DiG 9.6.1-P2 <<>> @localhost s5780003
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19534
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;s5780003. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2009122500 1800 900 604800 86400
;; Query time: 99 msec
;; SERVER: ::1#53(::1)
;; WHEN: Fri Dec 25 12:34:29 2009
;; MSG SIZE rcvd: 101
s5780003:/var/lib/named/master # dig s5780003.inet1.local
; <<>> DiG 9.6.1-P2 <<>> s5780003.inet1.local
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23432
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;s5780003.inet1.local. IN A
;; ANSWER SECTION:
s5780003.inet1.local. 172800 IN A 192.168.1.5
;; AUTHORITY SECTION:
inet1.local. 172800 IN NS ns1.inet1.local.
;; ADDITIONAL SECTION:
ns1.inet1.local. 172800 IN A 192.168.1.5
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Dec 25 12:36:14 2009
;; MSG SIZE rcvd: 88
s5780003:/var/lib/named/master # dig inet1.local
; <<>> DiG 9.6.1-P2 <<>> inet1.local
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30293
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;inet1.local. IN A
;; ANSWER SECTION:
inet1.local. 172800 IN A 192.168.1.5
;; AUTHORITY SECTION:
inet1.local. 172800 IN NS ns1.inet1.local.
;; ADDITIONAL SECTION:
ns1.inet1.local. 172800 IN A 192.168.1.5
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Dec 25 12:36:35 2009
;; MSG SIZE rcvd: 79
s5780003:/var/lib/named/master # nslookup google.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: google.com
Address: 74.125.47.99
Name: google.com
Address: 74.125.47.103
Name: google.com
Address: 74.125.47.104
Name: google.com
Address: 74.125.47.105
Name: google.com
Address: 74.125.47.106
Name: google.com
Address: 74.125.47.147
s5780003:/var/lib/named/master # nslookup
> inet1.local
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: inet1.local
Address: 192.168.1.5
> s5780003
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: s5780003.inet1.local
Address: 192.168.1.5
> mail.inet1.local
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: mail.inet1.local
Address: 192.168.1.5
> mail.inetmining.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: mail.inetmining.com
Address: 71.41.92.58
> www.inetmining.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: www.inetmining.com
Address: 71.41.72.28
>
There is still a lot of inet1.local in the zone file for inet1.local. All names in that zone file do allready get inet1.local added.
The zone file for 5.1.168.192.in-addr.arpa is nonsense. You should have one for 1.168.192.in-addr.arpa and of course then this zone part should not be inside the file like local1.net in the other one.
And all my other remarks about the .com subdomain and the CNAMEs still hold true.
Maybe you should first explain what you are trying to achieve. Did you register the inetmining subdomain at com and do you try to set up a DNS server for the internet to get systems in it resolved?
I am not very nice to you, but when you try to create and maintain a DNS server, that is not something for the faintharted. And when you do not understand what the difference is between your DNS clients not getting names resolved and the connection through a router to the Internet, you lack kowledge. That has nothing to do with Linux, it is plain network knowledge.
Update inet1.local is the local domain, Inetmining.com is the website domain. Should I just set it up as inetmining.com?
Make 2 (two) different zone files for these. And listen to hcw. You are on the wrong track. Read a manual.
I’m not meaning to be blunt. But there is a learning curve here. Setting up DNS requires a lot of knowledge and there are a lot of manuals, howto’s, tutorials … Jump into it. It takes time, but it’s doable. And when you are stuck, feel free to ask.
It is legal though to have multiple A records pointing to an IP address. Expert opinions are divided over whether this is a good thing. Pro: one less lookup. Con: you have to find all the records if you change the address. Con-Con: That’s what a good text editor is for.
I’m not sure what the OP’s problem is. If it’s failing to resolve external domains, then he needs a forwarder declaration or the server has to be allowed to use port 53 outgoing to do its own resolution. It is possible that some ISP block this port to force subscribers to use their forwarders. Try a dig forums.opensuse.org +trace, that will show the path from DNS root.
I have done some more research on this subject unfortunately there is a lot of conficting info per setup.I have updated my setup per your response. Please bare with me. Thank You.
s5780003:/var/lib/named/master # cat inet1.local
$TTL 2d
@ IN SOA s5780003.inet1.local. root.s5780003.inet1.local. (
2009122604 ; serial
3h ; refresh
1h ; retry
1w ; expiry
1d ) ; minimum
inet1.local. IN MX 3 mail.inet1.local.
inet1.local. IN NS inet1.local.
inet1.local. IN A 192.168.1.5
s5780003 IN CNAME inet1.local.
mail IN CNAME inet1.local.
s5780003:/var/lib/named/master # cat 5.1.168.192.in-addr.arpa
$TTL 2d
@ IN SOA s5780003.inet1.local. root.s5780003.inet1.local. (
2009122625 ; serial
3h ; refresh
1h ; retry
1w ; expiry
1d ) ; minimum
5.1.168.192.in-addr.arpa. IN NS inet1.local.
5.1.168.192.in-addr.arpa. IN PTR inet1.local.
s5780003:/var/lib/named/master #
The ptr is auto generated by yast2. I created a seperate zone for the website inetmining.com . Question: Should I use the assigned static IP from the router ( assigned to server nic)for the A record in the website zone or the static ip from the isp that is the routers set IP?
I am sorry, but most remarks I made are not used by you.
But the most important thing is, I repeat from my earlier post:
Maybe you should first explain what you are trying to achieve. Did you register the inetmining subdomain at com and do you try to set up a DNS server for the internet to get systems in it resolved?
You did provide us with one (only one) zone file of a configuration where we have nothing else. May be there is more, maybe not. My hint to a zone for reverse lookup made you show one to me. I do not know if you had it earlier, or just made it because I talked about it. Where is the bind configuration fiile, where are your forwarders?
First question is always: What are you going to make and why. When we know that we can maybe see if the files you show us are correct for what you want.
I’m transferring my windows 2003 r2 server over to a linuxed based enviroment ( Learning as I go sorta speak ). This will be a webserver / Mail server only for inetmining.com. This domain has been registered for around 2 years. I only need Dns to resolve the website domain locally and for other local devices.
The SOA was set by yast2 should I be correcting this to read the same as NS?
$TTL 2D
@ IN SOA s5780003.inet1.local. root.s5780003.inet1.local. (
2009122600 ; serial
3H ; refresh
1H ; retry
1W ; expiry
1D ) ; minimum
inetmining.com. IN MX 1 mail.inetmining.com.
inetmining.com. IN NS inetmining.com.
inetmining.com. IN A 71.41.72.28
www IN CNAME inetmining.com.
ftp IN CNAME inetmining.com.
mail IN CNAME inetmining.com.
$TTL 2D
@ IN SOA s5780003.inet1.local. root.s5780003.inet1.local. (
2009122604 ; serial
3H ; refresh
1H ; retry
1W ; expiry
1D ) ; minimum
28.72.41.71.in-addr.arpa. IN NS inetmining.com.
28.72.41.71.in-addr.arpa. IN PTR inetmining.com.
update : THe forwarders point to the ISP’s dns primary/secondary. I had to set that on the nic to gain access to the internet in the beginning. Yast updated the forwarder conf with these ip’s
# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Frank Bodammer, Lars Mueller <lmuelle@suse.de>
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND 9. It works as
# a caching only name server without modification.
#
# A sample configuration for setting up your own domain can be found in
# /usr/share/doc/packages/bind/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind/misc/options.
options {
# The directory statement defines the name server's working directory
directory "/var/lib/named";
# Write dump and statistics file to the log subdirectory. The
# pathenames are relative to the chroot jail.
dump-file "/var/log/named_dump.db";
statistics-file "/var/log/named.stats";
# Enable the next entry to prefer usage of the name server declared in
# the forwarders section.
#forward first;
# The listen-on record contains a list of local network interfaces to
# listen on. Optionally the port can be specified. Default is to
# listen on all interfaces found on your system. The default port is
# 53.
#listen-on port 53 { 127.0.0.1; };
listen-on port 53 { 127.0.0.1; 192.168.1.5; };
# The listen-on-v6 record enables or disables listening on IPv6
# interfaces. Allowed values are 'any' and 'none' or a list of
# addresses.
listen-on-v6 { any; };
# The next three statements may be needed if a firewall stands between
# the local server and the internet.
#query-source address * port 53;
#transfer-source * port 53;
#notify-source * port 53;
query-source address * port 53;
transfer-source * port 53;
notify-source * port 53;
# The allow-query record contains a list of networks or IP addresses
# to accept and deny queries from. The default is to allow queries
# from all hosts.
#allow-query { 127.0.0.1; };
#allow-query { 127.0.0.1; 192.168.1.5/24; };
# If notify is set to yes (default), notify messages are sent to other
# name servers when the the zone data is changed. Instead of setting
# a global 'notify' statement in the 'options' section, a separate
# 'notify' can be added to each zone definition.
notify no;
include "/etc/named.d/forwarders.conf";
};
# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
# # Log queries to a file limited to a size of 100 MB.
# channel query_logging {
# file "/var/log/named_querylog"
# versions 3 size 100M;
# print-time yes; // timestamp log entries
# };
# category queries {
# query_logging;
# };
#
# # Or log this kind alternatively to syslog.
# channel syslog_queries {
# syslog user;
# severity info;
# };
# category queries { syslog_queries; };
#
# # Log general name server errors to syslog.
# channel syslog_errors {
# syslog user;
# severity error;
# };
# category default { syslog_errors; };
#
# # Don't log lame server messages.
# category lame-servers { null; };
#};
# The following zone definitions don't need any modification. The first one
# is the definition of the root name servers. The second one defines
# localhost while the third defines the reverse lookup for localhost.
zone "." in {
type hint;
file "root.hint";
};
zone "localhost" in {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
# Include the meta include file generated by createNamedConfInclude. This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named
include "/etc/named.conf.include";
zone "inet1.local" in {
allow-transfer { any; localhost; localnets; };
file "master/inet1.local";
type master;
};
zone "5.1.168.192.in-addr.arpa" in {
allow-transfer { any; localhost; localnets; };
file "master/5.1.168.192.in-addr.arpa";
type master;
};
logging {
category default { log_syslog; };
channel log_syslog { syslog; };
};
zone "inetmining.com" in {
allow-transfer { any; localhost; localnets; };
file "master/inetmining.com";
type master;
};
zone "28.72.41.71.in-addr.arpa" in {
allow-transfer { any; localhost; localnets; };
file "master/58.92.41.71.in-addr.arpa";
type master;
};
# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.
I am afraid that distance as well as in space and time (not being in the same room as you) as in understanding is a bit to big for me. I realy do not know where to start. And then you come again with a host of new facts full of problems. I realy do not know where to start. Maybe I can point you to BIND Configuration Files. There you will find background and also some neatly formatted examples.
The zone 5.1.168.192.in-addr.arpa is wrong. The zone is 1.168.192.in-addr.arpa and last numbers of the IP addresses are the labels of the PTR RRs.
Same for 72.41.71.in-addr.arpa. The zone must be 41.71.in-addr.arpa and there is then a RR:
28 IN NS inetmining.com.
And I also do still not understand what inet1.local is. In some places it is a domain and in others it is a system. Do you want to serve *local *as a top level to your clients, or the subdomain inet1.local or both?
If you want a DNS server to resolve inetmining.com locally, then you do not have inet.local or whatever in there. Everything is written in terms of inetmining.com. Then the shorthand of not writing the full domain and leaving out the final dot works properly. And the IP addresses should be local ones, unless you have locally reachable external addresses. I assume that single external address you named is reachable at that IP address. YaST can create both a forward and reverse zone for you. The forward one should look like this:
$TTL 2D
@ IN SOA inetmining.com. root.inetmining.com. (
2009122500 ; serial
3H ; refresh
1H ; retry
1W ; expiry
1D ) ; minimum
@ IN NS ns
ns IN A 192.168.0.1
www IN CNAME ns
And similarly for the reverse, except the NS line looks like this:
0.168.192.in-addr.arpa. IN NS ns.inetmining.com.
The rest of the lines can be like this:
1 IN PTR ns.inetmining.com.
Note that by convention the name of the reverse zone is just the network address reversed, leaving out the last octet, so the file is called 0.168.192.in-addr.arpa, not 1.0.168.192.in-addr.arpa.
However, if the address is an external one, then you cannot have a reverse mapping for it yourself, unless you want to ruin the reverse mappings for other addresses in that subnet which may not belong to you. The reverse mapping has already been done by whoever owns that address block. In fact when I go do
host 71.41.72.28
I get
rrcs-71-41-72-28.se.biz.rr.com.
and you have to live with that.
Once again I ask, are you sure you should be putting external addresses in a local DNS resolver? If you are behind a NAT router/firewall and have a local address for the host, you should use that.
Referring to your post #8 above: mail can NOT be a CNAME. Make it an “A” record. Having two (or more) A records is ok.
Ask your provider to set the reverse lookup for your subnet. Some “good” providers can do this for you. It should be set to reverse resolve 71.41.72.28 to mail.inetmining.com.
Some hints how to proceed: edit the config files; when you think they are ok do as root: rcnamed restart. Then look at /var/log/messages for any errors. Try what works using dig:
Then edit again as required. To get you started: this is an actual working conf file for a slave:
$ORIGIN .
$TTL 172800 ; 2 days
resalvatsano.ch IN SOA ns.niticgopyregol.ch. admin.resalvatsano.ch. (
2009062502 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
604800 ; expire (1 week)
86400 ; minimum (1 day)
)
NS ns.wblx.ch.
NS ns.yhavzk.ch.
NS ns.niticgopyregol.ch.
A 84.55.231.47
MX 10 mail.resalvatsano.ch.
MX 20 mail.niticgopyregol.ch.
$ORIGIN resalvatsano.ch.
mail A 84.55.231.47
ns A 84.55.231.47
www A 84.55.231.47
I took the liberty to anonymize things. Looking up these names on the real internet ™ will not work. This domain has three nameservers, a primary and a backup mailserver and a webserver. www could be made a CNAME as well. You put your own values.
Should I be concerned with the automatic empty zones showing in the message log. IF so, is there a way to clean these up?
Dec 27 20:03:41 s5780003 named[19051]: starting BIND 9.6.1-P2 -t /var/lib/named -u named
Dec 27 20:03:41 s5780003 named[19051]: built with ‘–prefix=/usr’ ‘–bindir=/usr/bin’ ‘–sbindir=/usr/sbin’ ‘–sysconfdir=/etc’ ‘–localstatedir=/var’ ‘–libdir=/usr/lib64’ ‘–includedir=/usr/include/bind’ ‘–mandir=/usr/share/man’ ‘–infodir=/usr/share/info’ ‘–with-openssl’ ‘–enable-threads’ ‘–with-libtool’ ‘–enable-runidn’ ‘–with-libxml2’ ‘–with-dlz-mysql’ ‘CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fno-strict-aliasing’ ‘LDFLAGS=-L/usr/lib64’
Dec 27 20:03:41 s5780003 named[19051]: adjusted limit on open files from 8192 to 1048576
Dec 27 20:03:41 s5780003 named[19051]: found 2 CPUs, using 2 worker threads
Dec 27 20:03:41 s5780003 named[19051]: using up to 4096 sockets
Dec 27 20:03:41 s5780003 named[19051]: loading configuration from ‘/etc/named.conf’
Dec 27 20:03:41 s5780003 named[19051]: using default UDP/IPv4 port range: [1024, 65535]
Dec 27 20:03:41 s5780003 named[19051]: using default UDP/IPv6 port range: [1024, 65535]
Dec 27 20:03:41 s5780003 named[19051]: listening on IPv6 interfaces, port 53
Dec 27 20:03:41 s5780003 named[19051]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 27 20:03:41 s5780003 named[19051]: listening on IPv4 interface eth1, 192.168.1.5#53
Dec 27 20:03:41 s5780003 named[19051]: /etc/named.conf:54: using specific query-source port suppresses port randomization and can be insecure.
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: 0.IN-ADDR.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: 127.IN-ADDR.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: 254.169.IN-ADDR.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Dec 27 20:03:41 s5780003 named[19051]: 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
Dec 27 20:03:41 s5780003 named[19051]: 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
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: D.F.IP6.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: 8.E.F.IP6.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: 9.E.F.IP6.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: A.E.F.IP6.ARPA
Dec 27 20:03:41 s5780003 named[19051]: automatic empty zone: B.E.F.IP6.ARPA
Dec 27 20:03:41 s5780003 named[19051]: command channel listening on 127.0.0.1#953
Dec 27 20:03:41 s5780003 named[19051]: command channel listening on ::1#953
Dec 27 20:03:41 s5780003 named[19051]: the working directory is not writable
Dec 27 20:03:41 s5780003 named[19051]: zone 0.0.127.in-addr.arpa/IN: loaded serial 42
Dec 27 20:03:41 s5780003 named[19051]: zone 1.168.192.in-addr.arpa/IN: loaded serial 2009122708
Dec 27 20:03:41 s5780003 named[19051]: zone inetmining.com/IN: loaded serial 2009122709
Dec 27 20:03:41 s5780003 named[19051]: zone localhost/IN: loaded serial 42
Dec 27 20:03:41 s5780003 named[19051]: running