wildcard DNS not parsed correctly #818

Open
booi opened this Issue Jun 14, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@booi

booi commented Jun 14, 2012

Creating wildcard DNS entries works but on retrieval they are returned incorrectly. A record retrieved via record = boto.route53.connection.Route53Connection.get_all_rrsets() yields a record.name with '\052' instead of '*'.

"\052.domain.com" instead of "*.domain.com"

\052 is * in unicode but it doesn't seem to be parsed this way.

@meonkeys

This comment has been minimized.

Show comment Hide comment
@meonkeys

meonkeys Jan 2, 2013

Strange, these asterisks don't need to be escaped.

I asked for help with this in the Route 53 forum.

Other folks appear to just work around the issue by manually unescaping asterisks. See:

See PR #1216 for a fix.

meonkeys commented Jan 2, 2013

Strange, these asterisks don't need to be escaped.

I asked for help with this in the Route 53 forum.

Other folks appear to just work around the issue by manually unescaping asterisks. See:

See PR #1216 for a fix.

@zimbatm

This comment has been minimized.

Show comment Hide comment
@zimbatm

zimbatm May 5, 2015

It's also an issue for zone.find_records('@', 'A') because r.name == name doesn't match. See

if r.name == name and r.type == type:

zimbatm commented May 5, 2015

It's also an issue for zone.find_records('@', 'A') because r.name == name doesn't match. See

if r.name == name and r.type == type:

k8s-merge-robot added a commit to kubernetes/kops that referenced this issue Aug 2, 2017

Merge pull request #3110 from mikesplain/FixWildcards
Automatic merge from submit-queue

Fix Wildcard domains returned as ASCII in dns-controller

After running into #2671 whenever dns-controller restarted, I looked into why dns-controller successfully creates entries for wildcard domains (e.g. `*.example.com` ) but after restarting, it errors, unable to find the old record.  It looks amazon returns ascii `\\052.example.com` instead of the `*.example.com` we expect. This was a simple fix I tested in our cluster and it seems to have fixed the issue.  I'm open to any changes but I think this could be a useful fix for those that may run into this in the future.

This isn't a new thing apparently: boto/boto#818

Fixes #2671

@Jason-Crowe Jason-Crowe referenced this issue in aws-samples/aws-lambda-mirror-dns-function Sep 13, 2017

Open

Wildcard records not handled #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment