Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to tampere. dns records #8

Closed
tswfi opened this issue Feb 12, 2019 · 5 comments
Closed

Changes to tampere. dns records #8

tswfi opened this issue Feb 12, 2019 · 5 comments
Assignees
Labels
DNS Change DNS Change request

Comments

@tswfi
Copy link
Member

tswfi commented Feb 12, 2019

#2 is still underway so this is "freeform" :)

New records (explicit MX and spf with trex mailman already added even if it is not yet used):

tampere     MX      193.28.89.206
tampere     TXT     "v=spf1 mx mx:mailman.trex.fi ~all"

Remove old deprecated records:

old.tampere           A            193.28.89.81
staging.tampere    A            193.28.89.206
*.staging.tampere  CNAME staging.tampere
@tanelikaivola
Copy link
Member

Actions taken

Deprecated records have been removed.

Clarification required

Does the target MX have a host name?

MX records should not point to IP addresses but to A/AAAA records specified somewhere else.

Option 1

  • mail.tampere A 193.28.89.206
  • tampere MX mail.tampere
  • tampere TXT "v=spf1 mx mx:mailman.trex.fi ~all"

Option 2

  • tampere MX 193.28.89.206
  • tampere TXT "v=spf1 mx mx:mailman.trex.fi ~all"

Option 3

  • tampere MX somemailmx.somewhere.fi
  • tampere TXT "v=spf1 mx mx:mailman.trex.fi ~all"

Verification notes

Additionally as a minor note, SPF record specifies mx:mailman.trex.fi, but last priority MX of mailman.trex.fi points to mqueue2.axu.tm that doesn't have A record specified. You should contact trex.fi to fix this issue.

@olmari
Copy link
Member

olmari commented Feb 14, 2019

mqueue2.axu.tm has AAAA record, and only AAAA record, "by design" of axu.

dig +short AAAA mqueue2.axu.tm
2001:1430:a:6e:a00:3eff:fe66:14

So it isn't broken, while I have no clue why axu wanted it that way.

@tanelikaivola tanelikaivola added question Further information is requested DNS Change DNS Change request labels Feb 14, 2019
@tswfi
Copy link
Member Author

tswfi commented Feb 14, 2019

Thanks!

Option 1 works fine. 193.28.89.206 is tampere.hacklab.fi server but for clarity I like to have it specified as its own. (a record will act as a mx record also, but I prefer having mx clearly specified).

Option 2 isn't this the same that was requested?

Option 3 no outside mx server right now

Lets use Option 1. I have to check with the mail server admins if they have AAAA working also (probably not). Will open a new issue about it if later if needed...

For the spf rule, I just copied what vaasa has for trex, didn't even check what it has :)

@rostbach
Copy link

I also vote for option 1, as that was what originally we wanted

@tanelikaivola
Copy link
Member

Change completed, current active record set:

Record Type Data
tampere A 193.28.89.206
tampere AAAA 2001:1bc8:1001:401:904f:35ff:fe34:c527
mail.tampere A 193.28.89.206
tampere MX 10 mail.tampere
*.tampere CNAME tampere

Please wait a while (hour or so) for DNS records to propagate and check if everything works as it should. Reopen this issue if there are problems with this change.

@tanelikaivola tanelikaivola removed the question Further information is requested label Feb 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DNS Change DNS Change request
Projects
None yet
Development

No branches or pull requests

4 participants