Re: [dns-operations] Route 53 Unexpected geo location behavior

Dan McCombs via dns-operations writes: > Ah, yes, so in this case the addresses given back when no edns > subnet is provided are the addresses of servers in eu-west, whereas > with the resolver's own IP (or /24 subnet, or the subnet of clients > querying it) as the edns subnet gets more expected

Re: [dns-operations] Route 53 Unexpected geo location behavior

--- Begin Message --- > > If there is a performance issue with one set of records versus another > (you don't > really say why the differing responses matter in your email), you might > try contacting the nameserver operator directly to discuss the issue. > Ah, yes, so in this case the addresses

Re: [dns-operations] Route 53 Unexpected geo location behavior

Dan McCombs via dns-operations wrote: > Hi everyone, > > We've stumbled upon what seems like unexpected behavior with Route 53 > returning > answers based on IP geo location to our resolvers. > > According to their documentation: > > When a browser or other viewer uses a DNS resolver that

Re: [dns-operations] Route 53 Unexpected geo location behavior

On Sat, Jun 10, 2023 at 05:52:27AM -0400, Dan McCombs via dns-operations wrote: > > dig -b 64.227.108.32 +short +subnet=64.227.108.32/32 \ > > @ns-1339.awsdns-39.org doitb-synthetic.atlassian.net FWIW, though it seems to not matter with the server in question, note that a scope prefix length

Re: [dns-operations] Route 53 Unexpected geo location behavior

me IP >> blocks). This is the first time we've had a user contact us about this, so >> I'm not sure if something changed with Route 53 recently, if this is being >> caused by configuration specific to the atlassian.net zone, or if >> somehow we just haven'

[dns-operations] Route 53 Unexpected geo location behavior

--- Begin Message --- Hi everyone, We've stumbled upon what seems like unexpected behavior with Route 53 returning answers based on IP geo location to our resolvers. According to their documentation : > When a