i’m seeing some weird behavior with route 53 creat...
# generald
dazzling-scientist-80826
10/03/2018, 8:33 PMi’m seeing some weird behavior with route 53 creating a TXT record on an apex domain. non-apex domain txt records seem to work fine, but when i create an apex record, like for SPF or similar, the creation succeeds, i get a valid resource id, but the domain doesn’t appear in route 53 & doesn’t get returned when i
dig TXTw
white-balloon-205
10/03/2018, 9:34 PM
That is surprising. When you say you got a valid resource ID - do you mean you got back an ARN or equivalent? If you use
awsd
dazzling-scientist-80826
10/04/2018, 5:18 PMsooo i just went to answer this question for you, but i’m not able to reproduce this problem… on my test domain… even tho it was reproducing reliably a few times yesterday on my main domain - really confusing. let me do a little more investigation
dazzling-scientist-80826
10/04/2018, 5:31 PMok - soooo this works totally fine on my test domain - same pulumi script, but here’s what happens on my main domain:
dazzling-scientist-80826
10/04/2018, 5:31 PMthe resource name is just HOSTEDZONEID_domainname_TXT
dazzling-scientist-80826
10/04/2018, 5:32 PMso removing that resource from the pulumi script & then running update causes the resource to be created
dazzling-scientist-80826
10/04/2018, 5:32 PMbut if i try to recreate it
dazzling-scientist-80826
10/04/2018, 5:32 PMon both test & real domains, it reports success
dazzling-scientist-80826
10/04/2018, 5:32 PMit’s shown in
aws route53 list-resource-record-setsdazzling-scientist-80826
10/04/2018, 5:32 PMBUT for the test domain, it also shows up in the aws console
dazzling-scientist-80826
10/04/2018, 5:32 PMfor the real domain, it doesn’t!
dazzling-scientist-80826
10/04/2018, 5:33 PMmeanwhile, for the test domain,
digdazzling-scientist-80826
10/04/2018, 5:33 PMbut on the real domain, it does not
dazzling-scientist-80826
10/04/2018, 5:33 PMi can manually add the record in the aws console & then it shows up & dig reports the right result
dazzling-scientist-80826
10/04/2018, 5:33 PMaws route53 list-resource-record-setsdazzling-scientist-80826
10/04/2018, 5:33 PMseems like something is funky on the aws side … just for my main domain ¯\_(ツ)_/¯
dazzling-scientist-80826
10/04/2018, 5:38 PM…. and just tried it one more time and it worked correctly
dazzling-scientist-80826
10/04/2018, 5:38 PMmy least favorite kind of bug 😕
dazzling-scientist-80826
10/04/2018, 5:39 PManyway, this is not really blocking/hurting me in any way now - but it was surprising/confusing
dazzling-scientist-80826
10/04/2018, 5:39 PMi’m paranoid about checking DNS records anyway - so maybe no action necessary other than remember i said this so that later when somebody else has a similar problem a pattern may start to emerge 🙂 sorry for the distraction
2 Views