Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > General

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 7th April 2012, 02:41
kpowney kpowney is offline
Junior Member
 
Join Date: Apr 2012
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default Incorrect behavior for CNAME records ISPConfig 3

I have a server running Debian 6 and ISPConfig 3.04.3. The server was built using the Perfect Server Debian 6 Bind and Dovecot instructions. All functions of the server work as expected except for fail2ban and resolution of CNAME dns records. I haven't looked into fail2ban yet and to be honest it is the least of my concerns at the moment.

My concern is with the CNAME record resolution. Currently dns responses are appending my current domain name to the end of the cname data record. For example sub.domain.tld resolves as cnamedata.tld.domain.tld. from what I can tell the zone file in bind is correct. This occurs for all cname records in either of the two zones I have currently on the server.

For example:

Zone domain1.tld file contains a record as follows:
mail 86400 CNAME mail.domain1.tld.

Zone domain2.tld contains:
home 86400 CNAME home.dynamicdns.tld

DNS resolution:
$nslookup mail.domain1.tld
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
mail.domain1.tld canonical name = mail.domain1.tld.domain1.tld.
Name: mail.domain1.tld.domain1.tld
Address: 72.20.x.x

$nslookup home.domain2.tld
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
home.domain2.tld canonical name = home.dynamicdns.tld.domain2.tld.
Name: home.dynamicdns.tld.domain2.tld.
Address: 72.20.x.x (should be 67.177.x.x)

If needed I can provide domain information and exact zone files, but I would prefer to keep them private if possible as one of the records should resolve to my home IP. Any help or advise on figuring this out would be appreciated.

Thanks

-kmp-
Reply With Quote
Sponsored Links
  #2  
Old 7th April 2012, 10:46
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,739 Times in 2,574 Posts
Default

Quote:
Originally Posted by kpowney View Post
Zone domain2.tld contains:
home 86400 CNAME home.dynamicdns.tld
You've forgotten a dot. The record must be:

Code:
home     86400     CNAME     home.dynamicdns.tld.
BTW, MX records must not point to CNAME records - only A records are allowed.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #3  
Old 7th April 2012, 19:48
kpowney kpowney is offline
Junior Member
 
Join Date: Apr 2012
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default exactly

Falko,

thanks for the reply that is exactly what I did. I left off the trailing '.' on all of the CNAME records. I actually found the issue last night but didn't get a chance to post the solution.

In regard to CNAME and MX records is there a reason CNAME records shouldn't be pointed to MX records? The MX record itself resolves to an A record. I also haven't had any issues sending or receiving mail from either domain.

Thanks
Reply With Quote
  #4  
Old 8th April 2012, 10:11
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,739 Times in 2,574 Posts
 
Default

http://en.wikipedia.org/wiki/MX_record
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
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
SquirrelMail login not working glenneh Installation/Configuration 13 9th April 2011 20:01
ISPConfig 3.0.0.9 RC2 released till General 51 17th April 2009 17:12
ISPConfig 3.0.1 released till General 36 29th March 2009 14:30
Loads of mysql connections to dbispconfig StrikerNL General 2 5th March 2009 14:31
ISPConfig, postfix, dovecot: incorrect permissions arsen.gushin Installation/Configuration 9 4th March 2009 10:34


All times are GMT +2. The time now is 15:56.


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