Re: DNS64 & nslookup

> On 13 Apr 2018, at 2:22 am, Mark Boolootian wrote: > > > Hi Mark, > > I know this is the wrong list for this > discussion, but I wanted to reply on > general principles. I lurk on the v6ops > list so know you think about this stuff > a lot. > > > Secondly, I would look at

RE: DNS64 & nslookup

From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Mark Boolootian Sent: Thursday, April 12, 2018 9:22 AM To: Mark Andrews <ma...@isc.org> Cc: Bind Users <bind-users@lists.isc.org> Subject: Re: DNS64 & nslookup > We've been running a DNS64/NAT64

Re: DNS64 & nslookup

Hi Mark, I know this is the wrong list for this discussion, but I wanted to reply on general principles. I lurk on the v6ops list so know you think about this stuff a lot. > Secondly, I would look at other mechanisms than DNS64/NAT64 to provide > IPv4 as-a-service. It really has a lot of

Re: DNS64 & nslookup

Firstly, you can tell nslookup to make queries “nslookup -query=”. nslookup is a really old tool which is why it make A queries by default. It predates even the concept of IPv6 (which dates from ~1995). The same also applies to dig which is slightly younger than nslookup. Secondly, I

Re: DNS64 & nslookup

On Apr 11, 2018, at 4:26 PM, Mark Boolootian wrote: >>> As far as I know, a host with on an IPv6 address is only ever >>> going to perform lookups. I'd be very interested to know >>> if there are cases where that isn't true. >> >> Well, if you run nslookup or dig -t a,

Re: DNS64 & nslookup

>> As far as I know, a host with on an IPv6 address is only ever >> going to perform lookups. I'd be very interested to know >> if there are cases where that isn't true. > > Well, if you run nslookup or dig -t a, you're asking for A records > explicitly. Ah, true that. Does nslookup do

Re: DNS64 & nslookup

On Apr 11, 2018, at 3:49 PM, Mark Boolootian wrote: > >>> I'll give those tools a try, but I don't understand how my client is >>> requesting >> an A record. It only has IPv6 networking. DNS64 should be requesting an >> A record, but that the client should see is the converted

Re: DNS64 & nslookup

DNS64 server takes a lookup and if there are NOT records at the name it then performs a A lookup for the same name and maps the results into records and returns them. There are additional caveats but that is the basic process. It does NOT take a A lookup and return record. A

Re: DNS64 & nslookup

According to what I've read, that's exactly what DNS64 does. It converts A records to records. (For mixed networks, it just passes through records, but that's not in my configuration): "DNS64 is a mechanism for synthesizing resource records (RRs) from A RRs." -

Re: DNS64 & nslookup

>> I'll give those tools a try, but I don't understand how my client is >> requesting > an A record. It only has IPv6 networking. DNS64 should be requesting an > A record, but that the client should see is the converted record. Is that > not right? > > Nope-- DNS requests aren't going to

Re: DNS64 & nslookup

On Apr 11, 2018, at 3:32 PM, Rick Tillery wrote: > I'll give those tools a try, but I don't understand how my client is > requesting an A record. It only has IPv6 networking. DNS64 should be > requesting an A record, but that the client should see is the converted

Re: DNS64 & nslookup

Because nslookup and dig are specialised DNS testing tools. They don’t use getaddrinfo to perform test lookups. getaddrinfo is the function that most applications use as part of the connection process. > On 12 Apr 2018, at 8:33 am, Rick Tillery wrote: > > I'll give

Re: DNS64 & nslookup

I'll give those tools a try, but I don't understand how my client is requesting an A record. It only has IPv6 networking. DNS64 should be requesting an A record, but that the client should see is the converted record. Is that not right? Rick On Wed, Apr 11, 2018, 5:27 PM Chuck Swiger

Re: DNS64 & nslookup

On Apr 11, 2018, at 3:09 PM, Rick Tillery wrote: > I appear to have my NAT64+DN64 IPv6 -> IPv4 network configured correctly, as > I can access IPv4 only Internet sites, e.g. from my browser. But some tools > don't seem to work the way I think they should. > > One

DNS64 & nslookup

I appear to have my NAT64+DN64 IPv6 -> IPv4 network configured correctly, as I can access IPv4 only Internet sites, e.g. from my browser. But some tools don't seem to work the way I think they should. One example is nslookup. If do nslookup ipv4.google.com, I get: $ nslookup ipv4.google.com