jungaretti/bacon

MX record priority error

khromov opened this issue ยท 2 comments

๐Ÿ‘‹ I was using this script to migrate a domain but ran into this error mid-way:

Error: couldn't create record: unmarshaling JSON body: invalid character '<' looking for beginning of value Usage:

When checking in the Porkbun admin it seemed to be a faulty MX record that got created but had priority 0. After manually changing the priority from PB admin panel the script could proceed.

Here is a snippet from my yaml:

  - type: MX
    host: "x.domain.com"
    content: mxa.eu.mailgun.org.
    ttl: 600
    priority: 10

As an aside, for some reason Bacon can't seem to detect that this particular DNS entry is already created:

  - type: TXT
    host: "bun-verify.khromov.se"
    content: "127d8e80396db8b58b2f236991f5e715c5431df0763ccaef0d2edd516220308a"
    ttl: 300

Every time i re-run it it says:

./bacon deploy khromov.se.yaml --delete --create
Deleting 1 records...
- {344101976 bun-verify.khromov.se TXT 127d8e80396db8b58b2f236991f5e715c5431df0763ccaef0d2edd516220308a 600 0 }
Creating 1 records...
- {bun-verify.khromov.se TXT 0xc0000b9450 127d8e80396db8b58b2f236991f5e715c5431df0763ccaef0d2edd516220308a}
Deployment complete!

Thanks for a great tool!

Bacon has trouble de-serializing and comparing numerical properties such as TTL and priority. I suspect that both of these problems relate to flakiness in Bacon's conversion to/from string