[UCIMC-Tech] point MX records to Google mail servers?
Josh King
jking at chambana.net
Tue Sep 10 17:28:03 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Barry,
That was my bad, when I corrected the records I didn't notice they
were missing the FQDN dot as well. It should be corrected now.
On 09/10/2013 12:32 PM, Barry Isralewitz wrote:
> Hi Josh, Hi Chris,
>
>
> Thanks for working on this! We're almost there; the addresses I
> asked or are now in the MX records, but they all have
> "thebikeproject.org" tacked on to the end (see nslookup below).
> Maybe the problem is: in the BIND zone file, the Google mail
> server addresses each need a trailing dot (".") at the end, for
> example aspmx.l.google.com --> aspmx.l.google.com.
>
> ...to keep the local domain from being appended, so the current
> aspmx.l.google.com.thebikeproject.org changes to -->
> aspmx.l.google.com in the MX records.
>
> Here's nslookup output.. ============================== ===>
> nslookup
>> set q=mx thebikeproject.org.
> Server: 130.126.2.131 Address: 130.126.2.131#53
>
> Non-authoritative answer: thebikeproject.org mail exchanger = 5
> alt1.aspmx.l.google.com.thebikeproject.org. thebikeproject.org mail
> exchanger = 5 alt2.aspmx.l.google.com.thebikeproject.org.
> thebikeproject.org mail exchanger = 1
> aspmx.l.google.com.thebikeproject.org. thebikeproject.org mail
> exchanger = 10 aspmx3.googlemail.com.thebikeproject.org.
> thebikeproject.org mail exchanger = 10
> aspmx2.googlemail.com.thebikeproject.org.
>
> Authoritative answers can be found from: thebikeproject.org
> nameserver = ns2.chambana.net. thebikeproject.org nameserver =
> ns.chambana.net. thebikeproject.org nameserver = ns3.chambana.net.
> aspmx.l.google.com.thebikeproject.org internet address =
> 209.66.96.72 alt1.aspmx.l.google.com.thebikeproject.org internet
> address = 209.66.96.72 alt2.aspmx.l.google.com.thebikeproject.org
> internet address = 209.66.96.72
> aspmx2.googlemail.com.thebikeproject.org internet address =
> 209.66.96.72 aspmx3.googlemail.com.thebikeproject.org internet
> address = 209.66.96.72 ns.chambana.net internet address =
> 64.89.16.20 ns2.chambana.net internet address = 192.80.111.168
> ns3.chambana.net internet address = 209.66.96.66
> ==============================
>
>
> Cheers,
>
> Barry
>
>
>
>
>
> On Sep 9, 2013, at 9:29 AM, Josh King wrote:
>
>> Hi Barry,
>>
>> There was a typo in the records as entered. The zone should be
>> replying with the correct information now.
>>
>> On Sat 07 Sep 2013 05:24:00 AM EDT, Barry Isralewitz wrote:
>>> Hello Chris,
>>>
>>> Thanks for working on this, but it looks like MX records
>>> haven't changed, that they are still "10
>>> mail.thebikeproject.org.". Here's some nslookup results, which
>>> seem to show that ns.chambana.net is providing the old records
>>> ("10 mail.thebikeproject.org.") and an SOA query which shows
>>> that ns.chambana.net is the right place to ask for
>>> thebikeproject.org .
>>>
>>> ================= ===> nslookup
>>>> thebikeproject.org.
>>> Server: 75.75.75.75 Address: 75.75.75.75#53
>>>
>>> Non-authoritative answer: Name: thebikeproject.org Address:
>>> 209.66.96.72
>>>> set q=mx thebikeproject.org.
>>> Server: 75.75.75.75 Address: 75.75.75.75#53
>>>
>>> Non-authoritative answer: thebikeproject.org mail exchanger =
>>> 10 mail.thebikeproject.org.
>>>
>>> Authoritative answers can be found from:
>>>> server ns.chambana.net
>>> Default server: ns.chambana.net Address: 64.89.16.20#53
>>>> thebikeproject.org.
>>> Server: ns.chambana.net Address: 64.89.16.20#53
>>>
>>> thebikeproject.org mail exchanger = 10
>>> mail.thebikeproject.org.
>>>> server ns2.chambana.net.
>>> Default server: ns2.chambana.net. Address: 192.80.111.168#53
>>>> thebikeproject.org.
>>> Server: ns2.chambana.net. Address: 192.80.111.168#53
>>>
>>> thebikeproject.org mail exchanger = 10
>>> mail.thebikeproject.org.
>>>
>>> ===========
>>>
>>> If I query Start of Authority (soa) I am seeing, as expected,
>>> 'origin' as 'ns.chambana.net'. Refresh is 300 seconds, so no
>>> worries there either: =========== nslookup
>>>> set q=soa thebikeproject.org.
>>> Server: 75.75.75.75 Address: 75.75.75.75#53
>>>
>>> Non-authoritative answer: thebikeproject.org origin =
>>> ns.chambana.net mail addr = hostmaster.chambana.net serial =
>>> 2013012600 refresh = 300 retry = 300 expire = 2419200 minimum =
>>> 300
>>>
>>> Authoritative answers can be found from: ===========
>>>
>>> Let me know what you think...
>>>
>>> Cheers,
>>>
>>> Barry
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sep 4, 2013, at 12:51 AM, Barry Isralewitz wrote:
>>>
>>>> Hi Chris,
>>>>
>>>>
>>>> On Sep 3, 2013, at 7:00 PM, Chris Ritzo wrote:
>>>>
>>>>> On 09/03/2013 07:51 PM, Chris Ritzo wrote:
>>>>>> On 09/03/2013 07:10 PM, Barry Isralewitz wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Just to clarify on the below: I don't think I have the
>>>>>>> admin access to do this myself for thebikeproject.org
>>>>>>> <http://thebikeproject.org> (for example, I don't have
>>>>>>> login access to ns.chambana.net
>>>>>>> <http://ns.chambana.net>). Could someone with admin
>>>>>>> permissions edit the DNS zone file records for for me?
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Barry
>>>>>>>
>>>>>>>
>>>>>>> On Sep 1, 2013, at 2:48 PM, Barry Isralewitz wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I'd like to point the MX records for
>>>>>>>> thebikeproject.org <http://thebikeproject.org/> to
>>>>>>>> Google's mail servers (then will use a feature of
>>>>>>>> Google Apps for Non-profits). I think we'd need to
>>>>>>>> change the records on the chambana.net
>>>>>>>> <http://chambana.net/> servers, not at my registrar
>>>>>>>> 1and1, since my registrar's only involvement is to
>>>>>>>> point to chambana nameservers (ns.chambana.net
>>>>>>>> <http://ns.chambana.net/> and ns2.chambana.net
>>>>>>>> <http://ns2.chambana.net/>). As far as I know,
>>>>>>>> thebikeproject.org <http://thebikeproject.org/> is
>>>>>>>> currently not using mail at all on chambana.net
>>>>>>>> <http://chambana.net/> servers, so no active service
>>>>>>>> would be endangered. I'm pretty sure our chambana
>>>>>>>> mailing lists (bikecoop, bikecoop-staff,
>>>>>>>> bikecoop-announce) would not be affected at all --
>>>>>>>> but I don't know enough Mailman mailing list
>>>>>>>> internals to be 100% positive; let me know if you
>>>>>>>> think otherwise.
>>>>>>>>
>>>>>>>>
>>>>>>>> The MX values I'd like are at "MX Record Values,
>>>>>>>> Google Apps Documentation"
>>>>>>>> http://support.google.com/a/bin/answer.py?hl=en&answer=174125
>>>>>>>>
>>>>>>>>
…except with TTL set to 86400, so:
>>>>>>>>
>>>>>>>> Name/Host/Alias Time to Live (TTL) Record Type
>>>>>>>> Value/Answer/Destination Blank or @ 86400 MX 1
>>>>>>>> ASPMX.L.GOOGLE.COM <http://ASPMX.L.GOOGLE.COM/> Blank
>>>>>>>> or @ 86400 MX 5 ALT1.ASPMX.L.GOOGLE.COM Blank or @
>>>>>>>> 86400 MX 5 ALT2.ASPMX.L.GOOGLE.COM Blank or @ 86400
>>>>>>>> MX 10 ASPMX2.GOOGLEMAIL.COM
>>>>>>>> <http://ASPMX2.GOOGLEMAIL.COM/> Blank or @ 86400 MX
>>>>>>>> 10 ASPMX3.GOOGLEMAIL.COM
>>>>>>>> <http://ASPMX3.GOOGLEMAIL.COM/>
>>>>>>>>
>>>>>>>>
>>>>>>>> Essential, says Google, that ASPMX.L.GOOGLE.COM
>>>>>>>> <http://ASPMX.L.GOOGLE.COM/> gets top priority.
>>>>>>>>
>>>>>>>> I may be a little rusty here, let me know if
>>>>>>>> something is obviously wrong…
>>>>>>>>
>>>>>>>> Cheers, Barry
>>>>>>>>
>>>>>>>> -- Barry Isralewitz Theoretical and Computational
>>>>>>>> Biophysics Group 3043 Beckman, University of Illinois
>>>>>>>> at Urbana-Champaign Office Phone: (217) 244-1612
>>>>>>>> email: barryi at ks.uiuc.edu
>>>>>>>> <mailto:barryi at ks.uiuc.edu>
>>>>>>>> http://www.ks.uiuc.edu/~barryi
>>>>>>>>
>>>>>>>
>>>>>>> -- Barry Isralewitz Theoretical and Computational
>>>>>>> Biophysics Group 3043 Beckman, University of Illinois
>>>>>>> at Urbana-Champaign Office Phone: (217) 244-1612 email:
>>>>>>> barryi at ks.uiuc.edu <mailto:barryi at ks.uiuc.edu>
>>>>>>> http://www.ks.uiuc.edu/~barryi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> IMC-Tech mailing list IMC-Tech at lists.chambana.net
>>>>>>> https://lists.chambana.net/mailman/listinfo/imc-tech
>>>>>>>
>>>>>>
>>>>>> Hi Barry, I can take a look at making these changes. I do
>>>>>> think there is potential for issues with lists, though
>>>>>> I'm not sure. Since we aren't hosting email accounts for
>>>>>> TBP (that I know about), I think it should be fine.
>>>>>>
>>>>>> , you can also send mail now to support at tech.chambana.net
>>>>>> to have these requests logged in our redmine ticket
>>>>>> queue.
>>>>>>
>>>>>> I'll get back to you after I've had a chance to enact
>>>>>> these changes.
>>>>>>
>>>>>
>>>>> Barry, These changes have now been made to TBP's DNS record
>>>>> on chambana.net. It may take a little bit for the change to
>>>>> propogate to all three of chambana.net's DNS servers.
>>>>>
>>>>> Let us know if you need additional changes made.
>>>>>
>>>>> Best, Chris R.
>>>>
>>>>
>>>>
>>>> Thanks much for making the changes, and for the quick
>>>> response! I would normally know within a day or so if the
>>>> changes work as hoped/intended, but with technology-free Rosh
>>>> Hashanah coming Wed. night, I won't be able to check on this
>>>> until Sunday. Should be able to let you know outcome, and
>>>> ask after any other changes, then.
>>>>
>>>> Cheers,
>>>>
>>>> Barry
>>>>
>>>> -- Barry Isralewitz Theoretical and Computational Biophysics
>>>> Group 3043 Beckman, University of Illinois at
>>>> Urbana-Champaign Office Phone: (217) 244-1612 email:
>>>> barryi at ks.uiuc.edu http://www.ks.uiuc.edu/~barryi
>>>>
>>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJSL1ajAAoJEC/aTaFprkmZ6r4P/ie775fKC5pzAVyuGhploIDv
HxENFD4BfaNfW27Q4QgkIJirW4bLFJ9jJK6LlKGm5IqbFeaLUj2EwjMMs4byDvhH
gxO8wkXW4RmavI2DO02gVk4gd7y9iDLK0Xj7Kt5stGhsHf2cGhWoxmJYabbbfCf5
faWYG78VXthVvaeXQ937El3qaZ4m4bBn9mrDAHZoX5mbOnjjapSR1vBz64T6nM2s
mzLSau1beM1N914/BNhLB5qcqp5pfOpPI8TXp13qUx06xDekqSOzp1QSS45YlwZl
++oVNTXfaCyNT7x+dZWjfejYiWHZJWXX+SJ8FgbDII4tabznfJDImikL/JxltCER
FKQY7melWcsJPwBYxqrj7a6iSbSHaeJu9tBYTAOrNrYLRDB3bONmClLocn7bpHZb
9XGw8CwNssVWwTVizKGVQD1o/wnERAmum4YWUZHkWf1UG97fZaStMB3O5LnkjM00
qXhUDt9wS/mR9cJW57xLviLqxD2RoZxYaLKclgIU6bHL5wbBCvr3EpDv29EfUYCU
UtTfqoF062JcpgOkkEK/NOzri74t8Qm+O6ZpF5PTHk01/oP9FEJNbl2L3PPX9GBo
rA6x6Cs9Fj7au8DvsWxeWv0reOrgbOV0WvFyDVakeKfh8OSS695Q1aQYsacs4G7G
3n0lCmXdREtyo3nOv+JY
=ciKk
-----END PGP SIGNATURE-----
More information about the IMC-Tech
mailing list