Project

General

Profile

Bug #336

Malformed SOA, MX, and NS records

Added by rgmhtt over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
hda-install
Target version:
-
Start date:
10/14/2009
Due date:
% Done:

100%

Description

Both the forward and reverse zones' SOA, NS, and MX records have only the domain where FQDN is the common practice, per the RFCs.

An alternative correction is to provide an A record for the domain. This is NOT the preferred solution.

If you need more explanation, I should be able to dig out sections of the RFCs and pages from Cricket's DS book!

History

#1 Updated by cpg over 11 years ago

  • Priority changed from Urgent to High

this is not as useful as it could be.

can you show an example, with before and after settings?
(or better yet, a patch for hdactl).

#2 Updated by rgmhtt over 11 years ago

In /usr/bin/hdactl

SOA occurs three times

printf $void " IN SOA %s. root.%s. (\n", $domain, $domain;
    printf $name2addr " IN SOA %s. root.%s. (\n", $domain, $domain;
    printf $addr2name "@ IN SOA %s. root.%s. (\n", $domain, $domain;

In each of these it should be

"@ IN SOA hda.%s. root.%s. (\n"

MX appears 2 lines twice:

printf $name2addr "\t\tIN MX 10 %s.\n", $domain;
    printf $name2addr "*\tIN MX 10 %s.\n", $domain;

again same change:

"\t\tIN MX 10 hda.%s.\n"

NS appears three times:

printf $void "\t\tIN NS %s.\n", $void_host;
    printf $name2addr "\t\tIN NS %s.\n", $domain;
    printf $addr2name "\t\tIN NS %s.\n", $domain;

same change:

"\t\tIN NS hda.%s.\n"

I don't know if there is any other place to make these changes. These seem obvious.

#3 Updated by Anonymous over 11 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Toegepast in changeset commit:"2742d4b88882d3f89f234be2b28e29c34fad5dad".

Also available in: Atom