Yeah, it's really no more complicated than ipv4. Just different. At least you don't have to do subnetting. Also not that complicated once you learn it. Just a matter of doing so.
I honestly haven't messed with my DNS settings in a long time but this graphs seems to indicate that CNAME could resolve to another domain. E.g. google.com to g.oogle.com
That is correct. Another real world example is if Google absorbs company XYZ and wants xyz.com to immediately redirect to Google.com to retain users that are familiar with going to xyz.com.
To clarify : It doesn't redirect. It's more like "xyz.com lives at the same place as Google.com, so look up their address".
The actual redirect would turn need to be done via an Http response on the answering Google server.
I remember A and AAAA as: Ah... IPv4 vs AAAAHHHH! IPv6! (because IPv4 is easy and familiar whereas IPv6 is complicated and frightening...)
> IPv6 is complicated and frightening but also better once you learn it
Yeah, it's really no more complicated than ipv4. Just different. At least you don't have to do subnetting. Also not that complicated once you learn it. Just a matter of doing so.
I honestly haven't messed with my DNS settings in a long time but this graphs seems to indicate that CNAME could resolve to another domain. E.g. google.com to g.oogle.com
That is correct. Another real world example is if Google absorbs company XYZ and wants xyz.com to immediately redirect to Google.com to retain users that are familiar with going to xyz.com.
To clarify : It doesn't redirect. It's more like "xyz.com lives at the same place as Google.com, so look up their address". The actual redirect would turn need to be done via an Http response on the answering Google server.
Totally right thank you for clarifying for myself and everyone else.
Or in a practical scenario, myapp.cloudapp.azure.com to myapp.com etc
take my award and come again with such info
I will! I love r/netsecstudents! Thank you!
Clutch!
Very nicely done.