Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Decyphering /var/log/syslog Trying to Sort Out DNS

Status
Not open for further replies.
giganetwireless

giganetwireless

IS-IT--Management
Jul 18, 2007
20
Hello Group

UBUNTU 6.06
Apache2 2.0.55
PHP 5.1.2
ISPConfig 2.3.2
Shorewall 3.0.4

This server is intended to be the primary www, IMAP server for my wireless ISP clientelle.
I utilized as my guide for setting up the server itself and have also installed ISPConfig.

At this point I am trying to see if anyone can shed some light on the logs pertaining to DNS when I run 'nano /var/log/syslog'

I have been reading an article which indicated at the end of each 'zone' line should end with 'loaded serial 1'

Can someone help me to decypher this log so I know what is an actual error and what is acceptable functionality?

* command channel listening on ::1#953 [shouldn't this line indicate my public IP?]

* zone giganetwireless.com/IN: loading master file pri.giganetwireless.com: CNAME and other data
[shoudn't this line indicate 'loaded serial 2007083107'?]

* zone 152.169.72.in-addr.arpa/IN: sending notifies (serial 2007083107)
[where are 'notifies' being sent, is this an error?]

Code: 
Aug 31 11:03:21 giganetwireless named[13512]: starting BIND 9.3.2 -u bind -t /var/lib/named
Aug 31 11:03:21 giganetwireless named[13512]: found 1 CPU, using 1 worker thread
Aug 31 11:03:21 giganetwireless named[13512]: loading configuration from '/etc/bind/named.conf'
Aug 31 11:03:21 giganetwireless named[13512]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 31 11:03:21 giganetwireless named[13512]: listening on IPv4 interface eth0, 72.169.152.211#53
Aug 31 11:03:21 giganetwireless named[13512]: command channel listening on 127.0.0.1#953
Aug 31 11:03:21 giganetwireless named[13512]: command channel listening on ::1#953
Aug 31 11:03:21 giganetwireless named[13512]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1
Aug 31 11:03:21 giganetwireless named[13512]: zone 152.169.72.in-addr.arpa/IN: loaded serial 2007083107
Aug 31 11:03:21 giganetwireless named[13512]: dns_master_load: pri.giganetwireless.com:25: [URL unfurl="true"]www.giganetwireless.com:[/URL] CNAME and other data
Aug 31 11:03:21 giganetwireless named[13512]: zone giganetwireless.com/IN: loading master file pri.giganetwireless.com: CNAME and other data
Aug 31 11:03:21 giganetwireless named[13512]: zone highcountryhomesofanza.com/IN: loaded serial 2007083112
Aug 31 11:03:21 giganetwireless named[13512]: running
Aug 31 11:03:21 giganetwireless named[13512]: zone 152.169.72.in-addr.arpa/IN: sending notifies (serial 2007083107)
Aug 31 11:03:21 giganetwireless named[13512]: zone highcountryhomesofanza.com/IN: sending notifies (serial 2007083112)
Aug 31 11:03:21 giganetwireless named[13512]: client 72.169.152.211#33300: received notify for zone 'highcountryhomesofanza.com'

When I run 'dig 72.169.152.211 giganetwireless.com any' I recieve the following:

Code: 
mailman@giganetwireless:/etc/bind$ sudo dig 72.169.152.211 giganetwireless.com any
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20175
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;72.169.152.211.                        IN      A

;; ANSWER SECTION:
72.169.152.211.         102     IN      A       0.0.0.0

;; Query time: 11 msec
;; SERVER: 72.169.152.211#53(72.169.152.211)
;; WHEN: Fri Aug 31 11:47:53 2007
;; MSG SIZE  rcvd: 48


; <<>> DiG 9.3.2 <<>> 72.169.152.211 giganetwireless.com any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 30054
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;giganetwireless.com.           IN      ANY

;; Query time: 4 msec
;; SERVER: 72.169.152.211#53(72.169.152.211)
;; WHEN: Fri Aug 31 11:47:53 2007
;; MSG SIZE  rcvd: 37

Can someone point in the right direction to troubleshooting DNS resolution for this server?

Thank you
Regards
 
Sort by date Sort by votes
Try the following to query the server 72.169.152.211 for any zone called giganetwireless.com
Code: 
dig @72.169.152.211 any giganetwireless.com


As for the 1::953 control channel you need to use a line like such for opening a control channel on your public IP.
Code: 
controls {
        inet 127.0.0.1 allow { localhost; } keys { localkey; };
        inet <Public IP> allow { <DNS Server ACL>;} keys { domainkey; };
};

As for the rest, post the part of your named.conf where you define your zones and the first few lines of your zone files (before you start defining your records).


Have Fun!

 
Upvote 0 Downvote
Thank you for the reply...

'dig @72.169.152.211 any giganetwireless.com'
Code: 
mailman@giganetwireless:/etc/bind$ sudo dig @72.169.152.211 any highcountryhomesofanza.com

; <<>> DiG 9.3.2 <<>> @72.169.152.211 any giganetwireless.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37508
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;giganetwireless.com.           IN      ANY

;; Query time: 7 msec
;; SERVER: 72.169.152.211#53(72.169.152.211)
;; WHEN: Fri Aug 31 13:49:15 2007
;; MSG SIZE  rcvd: 37

My own domain (giganetwireless.com) always turns up as above- yet one of my client domains (highcountryhomesofanza.com) result as follows when using 'dig @72.169.152.211 any highcountryhomesofanza.com'

Code: 
mailman@giganetwireless:/etc/bind$ sudo dig @72.169.152.211 any highcountryhomesofanza.com

; <<>> DiG 9.3.2 <<>> @72.169.152.211 any highcountryhomesofanza.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20077
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;highcountryhomesofanza.com.    IN      ANY

;; ANSWER SECTION:
highcountryhomesofanza.com. 86400 IN    A       72.169.152.211
highcountryhomesofanza.com. 86400 IN    SOA     ns1.highcountryhomesofanza.com. webmaster.highcountryhomesofanza.com. 2007083112 28800 7200 604800 86400
highcountryhomesofanza.com. 86400 IN    NS      ns1.highcountryhomesofanza.com.
highcountryhomesofanza.com. 86400 IN    NS      ns2.highcountryhomesofanza.com.

;; ADDITIONAL SECTION:
ns1.highcountryhomesofanza.com. 86400 IN A      72.169.152.211
ns2.highcountryhomesofanza.com. 86400 IN A      72.169.152.211

;; Query time: 7 msec
;; SERVER: 72.169.152.211#53(72.169.152.211)
;; WHEN: Fri Aug 31 13:53:47 2007
;; MSG SIZE  rcvd: 174

Verify location for insertion of 'controls'
I want to verify that I would place the 'controls' command in '/etc/bind/named.conf' just below 'options'?


 
Upvote 0 Downvote
Got to get used to this forum, buttons are opposite sides- meant to 'Preview' not 'Post', anyhow...

'named.conf zone defs'
Code: 
zone "." {
        type hint;
        file "db.root";
};

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

zone "152.169.72.in-addr.arpa" {
        type master;
        file "pri.152.169.72.in-addr.arpa";
};


zone "giganetwireless.com" {
        type master;
        file "pri.giganetwireless.com";
};
zone "highcountryhomesofanza.com" {
        type master;
        file "pri.highcountryhomesofanza.com";
};

First few lines of 'pri.giganetwireless.com'
Code: 
@       IN      SOA     ns1.giganetwireless.com. web_admin.giganetwireless.com. (
                        2007083102       ; serial, todays date + todays serial #
                        28800              ; refresh, seconds
                        7200              ; retry, seconds
                        604800              ; expire, seconds
                        86400 )            ; minimum, seconds
;
                NS      ns1.giganetwireless.com.              ; Inet Address of name server 1
                NS      ns2.giganetwireless.com.              ; Inet Address of name server 2
;

First few lines of 'pri.highcountryhomesofanza.com'
Code: 
$TTL        86400
@       IN      SOA     ns1.highcountryhomesofanza.com. webmaster.highcountryhomesofanza.com. (
                        2007083112       ; serial, todays date + todays serial #
                        28800              ; refresh, seconds
                        7200              ; retry, seconds
                        604800              ; expire, seconds
                        86400 )            ; minimum, seconds
;
                NS      ns1.highcountryhomesofanza.com.              ; Inet Address of name server 1
                NS      ns2.highcountryhomesofanza.com.              ; Inet Address of name server 2
;


Contents of'pri.152.169.72.in-addr.arpa'

Code: 
$TTL        86400
@               IN      SOA     ns1.giganetwireless.com. hostmaster.giganetwireless.com. (
                                2007083107       ; serial, todays date + todays serial #
                                28800   ; Refresh
                                7200    ; Retry
                                604800  ; Expire
                                86400)  ; Minimum TTL
                        NS      ns1.giganetwireless.com.
                        NS      ns2.giganetwireless.com.
211       PTR     giganetwireless.com.
210       PTR     login.giganetwireless.com.
211       PTR     [URL unfurl="true"]www.giganetwireless.com.[/URL]
211       PTR     ns2.giganetwireless.com.
211       PTR     ns1.giganetwireless.com.
211       PTR     mail.giganetwireless.com.
211       PTR     webmail.giganetwireless.com.
211       PTR     giganetwireless.com.giganetwireless.com.
211       PTR     highcountryhomesofanza.com.
211       PTR     highcountryhomesofanza.com.highcountryhomesofanza.com.
211       PTR     mail.highcountryhomesofanza.com.
211       PTR     ns2.highcountryhomesofanza.com.
211       PTR     webmail.highcountryhomesofanza.com.
211       PTR     ns1.highcountryhomesofanza.com.

'giganetwireless.com' does not have 'Managed DNS Services', I have just registered a new domain 'giganetwireless.net' which is utilizing 'Managed DNS services'.
It is my understanding that at this domain I would create 'ns1-6.giganetwireless.net' and utilize those DNS settings in the server referred to in this post.
I am going to build another server tonight it will host giganetwireless.net [which will handle technical issues only not email] and my aim is to have two DNS servers of my own.

Thank you

Regards
 
Upvote 0 Downvote
UPDATE

I utilized the zone file for 'highcountryhomesofanza.com' with a copy function, opened the new file and changed it to reflect id 'giganetwireless.com'.
Then I restarted 'bind' and after running 'dig @72.169.152.211 any giganetwireless.com' I see:
Code: 
mailman@giganetwireless:/etc/bind$ sudo dig @72.169.152.211 any giganetwireless.com

; <<>> DiG 9.3.2 <<>> @72.169.152.211 any giganetwireless.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8435
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;giganetwireless.com.           IN      ANY

;; ANSWER SECTION:
giganetwireless.com.    86400   IN      A       72.169.152.211
giganetwireless.com.    86400   IN      SOA     ns1.giganetwireless.com. webmaster.giganetwireless.com. 2007083112 28800 7200 604800 86400
giganetwireless.com.    86400   IN      NS      ns1.giganetwireless.com.
giganetwireless.com.    86400   IN      NS      ns2.giganetwireless.com.

;; ADDITIONAL SECTION:
ns1.giganetwireless.com. 86400  IN      A       72.169.152.211
ns2.giganetwireless.com. 86400  IN      A       72.169.152.211

;; Query time: 8 msec
;; SERVER: 72.169.152.211#53(72.169.152.211)
;; WHEN: Fri Aug 31 14:30:12 2007
;; MSG SIZE  rcvd: 167

Thank you
 
Upvote 0 Downvote
The controls statement can be included anywhere. FYI, mine is after the "options" section.

Put this line in the file pri.152.169.72.in-addr.arpa, after your global $TTL line
Code: 
$ORIGIN 152.169.72.in-addr.arpa.

And similar lines in each of the forward zone files, like so
Code: 
$ORIGIN <Domain.Name>.

Try these out and keep us posted.

Have Fun!

 
Upvote 0 Downvote
Here's a real dumb question..

<DNS Server ACL>
At this point I haven't secured BIND, but do intend to do so.
Should I go ahead and run 'apt-get install dnssec' before proceeding any further, I know that isn't the proper package name.

Could you suggest a worthy tutorial that would assist me in securing BIND providing a post BIND installation method?

Thank you
 
Upvote 0 Downvote
Did some reading last night, I think I am on target with the ACL question I last submitted.
I was going to use this doc for ref to setup ACL: Would this be on the cue?

At either rate, I have gained incremental progress...

To this point I can access my domain remotely using:
But I wind up viewing a default shared IP page rather than the ISPConfig default for the domain 'index'

If I add 'www' to the URL the browser warns 'DNS Lookup Error'.

I know that a domain specific default index should show up rather than the 'Shared IP' default as I have another domain ' actually goes to it's domain default index. This server is utilizing 1 IP total.
Thinking about it this site has DNS from another regsitrar, that would probably cause this event??

I have found that after adding:
Code: 
'$ORIGIN 152.169.72.in-addr.arpa.' [into same file]
&
Code: 
'$ORIGIN <Domain.Name>.' [into each zone file]

After the server reboots OR ISPConfig is restarted these two lines are removed from each file.
The results are varied also, sometimes I using:
Code: 
dig @72.169.152.211 any giganetwireless.com
will turn up empty-handed until I manually edit the zone file.

I will be working on adding the ACL controls also today..

Thank you for your help
 
Upvote 0 Downvote
Check this out...
BIND 9 Administrator Reference Manual

The $ORIGIN statement in the forward zone files should look like...
Code: 
$ORIGIN giganetwireless.com.
with a different domain name for each zone file.

To add an ACL...
Code: 
acl acl-name { address_match_list };

BTW, shouldn't you be configuring your server using ISPconfig. I'm not too familiar with it but it sounds like it is overwriting your edited file.

Have Fun!

 
Upvote 0 Downvote
Hi Thnks for the reply..

Regarding the origin statement- I applied the proper domain name to each zone file.
Code: 
$ORIGIN giganetwireless.com.

I have to add this line to my zone.file.templates so that any time ISPConfig makes DNS mods it will re-insert the '$ORIGIN' tag..

Thanks for the ACL help :)

Yes, I am configuring using ISPConfig.
However in trying to get DNS to work I found myself having to manually edit the zone files.

Discovered over the weekend that I accidentally installed the unstable BETA version of ISPConfig, so last night I uninstalled 3.2.3 and re-installed 2.2.16 STABLE.

Am still having troubles with DNS resolution though, even though all proper registrar changes are validated.
I haven't tried re-booting the machine since installing ISPConfig 2.2.16, so I'm going to give that a shot to see if things change regarding DNS resolution??


THank you

Regards
 
Upvote 0 Downvote
I finally hit pay-dirt!

Thank you very much for your help with my DNS problems....

Have a great week.

Regards
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

spamjim
  • Locked
  • Question
Sorting out NTFS filesystem issues
Replies
0
Views
136
spamjim
spamjim
donald lepariku
  • Locked
  • Question
Error: 694, Severity: 24, State: 10 An attempt was made to read logical page '153', virtpage '616' f 1
Replies
3
Views
196
spamjim
spamjim
kasperelectronics
  • Locked
  • Question
Desktop streaming from a server to low power front end device e.g. RasPi
Replies
0
Views
84
kasperelectronics
kasperelectronics
Edwin Reyes
  • Locked
  • Question
High CPU utilization Linux Server due to mysql
Replies
1
Views
125
spamjim
spamjim
theniteowl
  • Locked
  • Question
Parsing data out of files
Replies
0
Views
78
theniteowl
theniteowl

Part and Inventory Search

Sponsor

Back
Top