Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > Installation/Configuration

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #11  
Old 19th September 2007, 21:18
catdude catdude is offline
Senior Member
 
Join Date: Jun 2007
Posts: 178
Thanks: 1
Thanked 12 Times in 11 Posts
Default

Quote:
Originally Posted by Ashaman074
dig -t ptr domain.com
That's the problem - a ptr record is associated with an IP address, not with a domain name. That command by definition won't generate a valid PTR record return.

Try using "dig -t ptr z.y.x.w.in-addr.arpa", where your IP address is w.x.y.z.
Reply With Quote
Sponsored Links
  #12  
Old 19th September 2007, 21:34
Ashaman074 Ashaman074 is offline
Junior Member
 
Join Date: May 2007
Posts: 27
Thanks: 0
Thanked 1 Time in 1 Post
Default

Oops. OK, here is the output of dig -t ptr 75.255.167.12.in-addr.arpa:
Code:
; <<>> DiG 9.3.2 <<>> -t ptr 75.255.167.12.in-addr.arpa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25615
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;75.255.167.12.in-addr.arpa.	IN	PTR

;; ANSWER SECTION:
75.255.167.12.in-addr.arpa. 43182 IN	CNAME	75.72/29.255.167.12.in-addr.arpa.

;; Query time: 15 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Wed Sep 19 14:35:19 2007
;; MSG SIZE  rcvd: 67
Which is what I was AOL's test was returning I believe...with no reference to the associated domains...?
Reply With Quote
  #13  
Old 19th September 2007, 23:32
catdude catdude is offline
Senior Member
 
Join Date: Jun 2007
Posts: 178
Thanks: 1
Thanked 12 Times in 11 Posts
Default

Quote:
Originally Posted by Ashaman074
Oops. OK, here is the output of dig -t ptr 75.255.167.12.in-addr.arpa:
Code:
; <<>> DiG 9.3.2 <<>> -t ptr 75.255.167.12.in-addr.arpa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25615
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;75.255.167.12.in-addr.arpa.	IN	PTR

;; ANSWER SECTION:
75.255.167.12.in-addr.arpa. 43182 IN	CNAME	75.72/29.255.167.12.in-addr.arpa.

;; Query time: 15 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Wed Sep 19 14:35:19 2007
;; MSG SIZE  rcvd: 67
Which is what I was AOL's test was returning I believe...with no reference to the associated domains...?
Yeah.... that's a bummer. That's not what I expected to see.

How about "dig -t ptr @12.167.255.75 75.255.167.12.in-addr.arpa"? I'm assuming that will return the host names for all the domains you've defined in ISPConfig.
Reply With Quote
  #14  
Old 20th September 2007, 17:17
Ashaman074 Ashaman074 is offline
Junior Member
 
Join Date: May 2007
Posts: 27
Thanks: 0
Thanked 1 Time in 1 Post
Default

Yes, that does return the entire list - but what does this mean?
Reply With Quote
  #15  
Old 20th September 2007, 17:25
catdude catdude is offline
Senior Member
 
Join Date: Jun 2007
Posts: 178
Thanks: 1
Thanked 12 Times in 11 Posts
Default

Quote:
Originally Posted by Ashaman074
Yes, that does return the entire list - but what does this mean?
It means that your ISPConfig server is properly configured for DNS and is returning the proper PTR records, but that the authority records that define where to look for reverse-IP mappings for your subnet are pointing somewhere other than your server.

I'm afraid my understanding of DNS internals fails at this point. I'm not sure how to determine where such requests are directed, or how to get them redirected to your server. The best I can offer at this point is to maybe contact tech support at your ISP (AT&T, was it?) and ask them.
Reply With Quote
  #16  
Old 20th September 2007, 17:48
Ashaman074 Ashaman074 is offline
Junior Member
 
Join Date: May 2007
Posts: 27
Thanks: 0
Thanked 1 Time in 1 Post
Default

Interesting. Well, I very much appreciate your help with these steps! I suppose it can't hurt to give them a call, they may be able to shed some light on this mystery for me - too strange.

Of course, if anyone else has thoughts on this Probl...err...that is "learning experience" I would appreciate it also.

Thanks again catdude for the assistance!
Reply With Quote
  #17  
Old 30th October 2007, 21:20
Ashaman074 Ashaman074 is offline
Junior Member
 
Join Date: May 2007
Posts: 27
Thanks: 0
Thanked 1 Time in 1 Post
Default

Hi, I thought I would add something new to this old thread as I never did resolve it. It has now become a bigger problem however, as apparently Comcast has tightened things up a bit and I can no longer send to them either

I contacted my ISP, who sent me the following information:

Code:
Following is an example of how a partial c class should be set up.
 

0/27.161.2.12.in-addr.arpa.     3600    SOA     dns2.anydomain.com.
administrator.anydomain.com. (
                        2002050202      ; serial
                        14400   ; refresh (4 hour)
                        600     ; retry (10 mins)
                        600000  ; expire (7 day)
                        86400)  ; minimum (1 day)
0/27.161.2.12.in-addr.arpa.     3600    NS      dns2.anydomain.com.
0/27.161.2.12.in-addr.arpa.     3600    NS      cbru.br.ns.els-gms.att.net.
0/27.161.2.12.in-addr.arpa.     3600    NS      dbru.br.ns.els-gms.att.net.
1.0/27.161.2.12.in-addr.arpa.   3600    PTR     gw.anydomain.com.
10.0/27.161.2.12.in-addr.arpa.  3600    PTR     hidden4.anydomain.com.
11.0/27.161.2.12.in-addr.arpa.  3600    PTR     hidden5.anydomain.com.
12.0/27.161.2.12.in-addr.arpa.  3600    PTR     hidden6.anydomain.com.
13.0/27.161.2.12.in-addr.arpa.  3600    PTR     www.anydomain.com.
14.0/27.161.2.12.in-addr.arpa.  3600    PTR     www.adomain.org.
2.0/27.161.2.12.in-addr.arpa.   3600    PTR     dns2.anydomain.com.
3.0/27.161.2.12.in-addr.arpa.   3600    PTR     firewall.anydomain.com.
4.0/27.161.2.12.in-addr.arpa.   3600    PTR     mail.anydomain.com.
5.0/27.161.2.12.in-addr.arpa.   3600    PTR     ftp.anydomain.com.
6.0/27.161.2.12.in-addr.arpa.   3600    PTR     www.anydomain.com.
7.0/27.161.2.12.in-addr.arpa.   3600    PTR     hidden1.anydomain.com.
8.0/27.161.2.12.in-addr.arpa.   3600    PTR     hidden2.anydomain.com.
9.0/27.161.2.12.in-addr.arpa.   3600    PTR     hidden3.anydomain.com.
0/27.161.2.12.in-addr.arpa.     3600    SOA     dns2.anydomain.com.
administrator.anydomain.com. (
                        2002050202      ; serial
                        14400   ; refresh (4 hour)
                        600     ; retry (10 mins)
                        600000  ; expire (7 day)
                        86400 )  ; minimum (1 day)
Unfortunately, I am not sure WHERE this should be set up - should I manually edit config files on my server? Or is there a better way to do this? If I understand them correctly, any PTR requests are being handed off by them to my name servers; but they say that something must not be configured right at my end, and they have sent me this sample.

Does anyone understand this or know what might be causing the problem?

Thanks!
Reply With Quote
  #18  
Old 10th December 2007, 17:13
Ashaman074 Ashaman074 is offline
Junior Member
 
Join Date: May 2007
Posts: 27
Thanks: 0
Thanked 1 Time in 1 Post
Default

Well, as a followup (I always hate abandoned threads when I am searching!), I had someone with extensive Linux experience do a little troubleshooting since I felt I had exhausted all of my resources. It seems the the problem came down to one simple entry:

In named.conf the entry was:

PHP Code:
zone "255.167.12.in-addr.arpa" {
        
type master;
        
file "pri.255.167.12.in-addr.arpa"
This was changed to:

PHP Code:
zone "72/29.255.167.12.in-addr.arpa" {
        
type master;
        
file "pri.255.167.12.in-addr.arpa"
Apparently all this trouble was as simple as the naming convention used. Interestingly enough, as I typed this today I noticed the changes had been overwritten to their original state! I'll have to keep an eye on it to see if it happens again, maybe manually editing the file wasn't the best way to go about it...

Thanks to everyone who tried to help with this problem.
Reply With Quote
The Following User Says Thank You to Ashaman074 For This Useful Post:
dabro (29th May 2008)
  #19  
Old 29th May 2008, 19:14
dabro dabro is offline
Junior Member
 
Join Date: May 2006
Posts: 10
Thanks: 4
Thanked 0 Times in 0 Posts
Default This Solution Works

Thanks for the information, I'm in the same boat, we installed an ATT T1 line and they delegated the r-dns to us. Adding the zone to named.conf with the subnet information as you described did start it to working. As in "zone "192/27.xxx.xxx.xx.in.addr.arpa" pointing to the same zone file "pri.xxx.xxx.xx.in-addr-arpa" does work. The zone file basically works without any mods except for too many entries. Now I need to figure out how to limit the reverse hostname to one host without ISPConfig overwriting the zone file with every domain on the server. Thanks again, it did save some hair pulling, Dave
Reply With Quote
  #20  
Old 29th May 2008, 19:39
daveb daveb is offline
Senior Member
 
Join Date: Dec 2006
Location: St Louis Mo
Posts: 272
Thanks: 43
Thanked 41 Times in 37 Posts
 
Default

I had the same problems with att and rdns delegation. Copy and edit the named.master template and you shouldn't have to worry about your changes being overwritten during updates.
Code:
cp /root/ispconfig/isp/conf/named.conf.master /root/ispconfig/isp/conf/customized_templates/named.conf.master
then edit
Code:
vi /root/ispconfig/isp/conf/customized_templates/named.conf.master
here is a link on how I changed named.conf http://www.howtoforge.com/forums/sho...85&postcount=2
Also here is a faq I was sent from att for Methods of Reverse Delegation
Code:
Customers using UNIX or Linux with BIND should follow the outline below.

A.  Classless Reverse Delegation  Less than /24 For more information RFC 2317 (Section 5.2).

1.      At SBC Name Server:
a.  Example  Classless reverse delegation of 192.68.10.8/29 is delegated to customers ns1.custdom.net 192.68.10.9. 
b.  The zone 192.68.10.net would have these CNAME entries to in-addr.arpa. 

;  rev del custdom.net 192.68.10.8/29
8       NS      ns1.custdom.net.
        NS      ns1.swbell.net.  ;an SBC server will be used only if secondary service is requested
        NS      ns2.swbell.net.  ;an SBC server will be used only if secondary service is requested
9        CNAME   9.8.10.68.192.in-addr.arpa.
10      CNAME   10.8.10.68.192.in-addr.arpa.
11      CNAME   11.8.10.68.192.in-addr.arpa.
12      CNAME   12.8.10.68.192.in-addr.arpa.
13      CNAME   13.8.10.68.192.in-addr.arpa.
14      CNAME   14.8.10.68.192.in-addr.arpa.

c.  Optional Secondary DNS Service - At SBC named.conf.in-addr with slave statement as secondary to 192.68.10.9.

zone "8.10.68.192.in-addr.arpa" { type slave; file "SECONDARY/192.68.10.8.net"; masters {192.68.10.9;};};

2.   At Customer Name Server:
a.  The following statement would be included at the customers named.conf file.  

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

b.  The zone 8.10.68.192.in-addr.arpa for the PTR records would look similar to this, edit the PTR records as desired

$ORIGIN  8.10.68.192.in-addr.arpa.
@     IN                NS               your-ns.custdom.net.
                             IN                NS               ns1.swbell.net. ;use an SBC server if secondary DNS service was requested
                             IN                NS               ns2.swbell.net. ;use an SBC server if secondary DNS service was requested
9                           IN                PTR             host1.custdom.net.
10     IN                PTR             host2.custdom.net.
11     IN                PTR             host3.custdom.net.
12     IN                PTR             host4.custdom.net.
13     IN                PTR             host5.custdom.net.
14                     IN                PTR           host6.custdom.net.

B.  Full Class/es Reverse Delegation - /24 Plus

1.      At SBC Name Server:
a.  Example  Reverse delegation of 192.68.10.0/24 is delegated to customers server, ns1.custdom.net 192.68.10.9.  The zone 192.68.net would have this NS record to ns1.custdom.net. 

;   rev del custdom.net 192.68.10.0/24
10      NS      ns1.custdom.net.
        NS      ns1.swbell.net.   ;only when specifically requested for secondary DNS service
        NS      ns2.swbell.net.   ;only when specifically requested for secondary DNS service

b.  Optional Secondary DNS Service - At SBC named.conf.in-addr with slave statement to 192.68.10.9.

zone "10.68.192.in-addr.arpa" { type slave; file "SECONDARY/192.68.10.net"; masters {192.68.10.9;};};

2.   At Customer Name Server:
a.  The following statement would be included at the customers named.conf file. 

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

b.  The zone 10.68.192.in-addr.arpa for the PTR records would look similar to this, edit the PTR records as desired

$ORIGIN  10.68.192.in-addr.arpa.
@     IN                NS               your-ns.custdom.net.
                        IN                NS               ns1.swbell.net.   ;use an SBC server only when secondary DNS service was specifically requested
                        IN                NS               ns2.swbell.net.   ;use an SBC server only when secondary DNS service was specifically requested
                        IN                PTR             host1.custdom.net.
2                       IN                PTR             host2.custdom.net.
;cont
254   IN                PTR             host254.custdom.net.
255   IN                PTR             host255.custdom.net.
Hope this helps Ashaman074 and dabro
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
DNS Configuration Problems VMartins Installation/Configuration 10 24th July 2007 14:40
Unable send receive emails vassilis3 Installation/Configuration 15 19th May 2007 14:34
No SPF record. beryl Installation/Configuration 6 17th May 2007 19:52
dns problems rayit General 2 24th August 2006 18:04
DNS, rDNS, NAT and vhosts, oh my! Hyakugei Installation/Configuration 2 19th May 2006 16:23


All times are GMT +2. The time now is 08:55.


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