I guess the difference in views starts with what one considers to be a problem…
3 Likes
Well I consider a problem that IPv4 and IPv6 have different records.
A versus AAAA and they do not mix.
For me that is a problem, they should be the same regardless the protocol.
I never understood why they are different.
In many things we give a ‘version’ with a request and then get the right answer.
I do not understand why DNS doesn’t have this, why the request can’t define the answer to get.
Setup a dual-protocol mailserver, then you will know soon enough that you have to define everything twice…on ALL records.
For what?
Same for NTP, a dualstack server needs to define everything twice…on all sides.
For what?
Those are just a few of my problems.
And that is fine, and I think pretty much everyone has understood that by now. So no need to keep repeating it over and over again.
3 Likes
You keep saying that IPv6 should be pushed. Same same 
That’s the topic. Please read the title carefully to understand. Don’t like it? Simply don’t use it and don’t mess with others wanting to use it. Is that so hard?
4 Likes
Sure. But this thread was created by people of that point of view to discuss with like-minded people, of which there are a few. Those have understood that your view differs from their view, and simply would like to discuss amongst like-minded people what they see as relevant.
You don’t agree, and that’s fine. But as you’ve stated yourself, the views are likely to never align. So why don’t you start your own thread where you can discuss with like-minded people what you consider to be problems, and let those who have a different view discuss amongst their group of like-minded people.
2 Likes
Rather simple: He is trolling.
4 Likes
I only point out the problems with a 30+ years protocol, that made sense at the time but do hinder implementation today.
Sadly you seem to dismiss the problems of IPv6 and stick to thinking of decennia ago.
That could have been changed today without problems.
Why force this on people today, when it clearly isn’t properly implemented from the start.
Don’t get me wrong, I do want to use IPv6, but it needs fixing. Strange is, people that love IPv6 are as flexible as a doorknob and do not want to hear complaints.
In the end IPv6 will die and replaced by something else that does fix the problems. As companies are spending a shitload of money on it, and they receive complaints all the time from people like me.
But the protocol doesn’t change to solve those complaints.
Get a life will you. Your replies only prove my points about IPv6.
So, let us be, and be happy you have a better grasp of things.
Assuming that by “on people”, you mean to include yourself. Where in this thread do you think anyone is forcing you to use a protocol you don’t want to use? I think it’s been pointed out time and time again that if you don’t want to use IPv6, then just don’t. But also let other people be who do want to use it, and do want to talk about that. Just as they let you be.
Yeah, if that is what you believe, then why not just quietly wait until the time has come, and rejoice when it does?
If that is the conclusion you reach, why keep complaining, as you yourself acknowledge it is of no use? Simply wait until IPv6’s demise, and look forward to then be free of it.
2 Likes
There will be a new protocol. Trust me.
It will fix the gaps between IPv4 and IPv6 today.
The issue is simple, money, loads of companies spend a shitload of money in IPv6 but problems aren’t solved.
When companies stop funding, it will stop. And something new will come that solves the issues.
Things will change as IPv6 still hasn’t reached momentum and people complain about it.
You can dislike my comments, so be it. In the end money and backing of companies will alter IPv6 or make IPv7.
I do not know, but IPv6 as we have it today is a failure.
I hope it changes soon…for the better.
Yeah, just ignore IPv6 until then and keep using IPv4. Again, noone forces you to use it. Just similarly let other people be who do want to use it in the meantime, and do want to talk about it until something new and better has become available.
I don’t dislike your comments. I just don’t agree with them. But rest assured I let you be, and just ask that you similarly let me and others with a different point of view be as well.
1 Like
You can try coding in C++…if you do…you need to define IPv4 and IPv6 seperatly in there.
Why? Inet versus Inet6 and the rest of the code that needs to be double.
Useless.
That’s why DNS exists - for more than 30 years.
Not entirely sure off the top of my head, but I’d expect the new combined IPv4/IPv6 interface not to have entirely replaced the previous IPv4-only interface, but to be an optional addition. Just stick to the latter (IPv4-only), then, ignore the former.
Then just don’t use it. Entirely up to you.
1 Like
C++ has 2 instances, inet and inet6…seems you do not know how much work it is to seperate the 2 of them.
You have to code everything dual-stack…that could have been prevented.
But they expected that IPv4 would die and IPv6 would take over…then it would have made sense. But it didn’t.
So coders have to code everything twice and test twice. This will not last.
At a certain point a company will say: ENOUGH!
Then things will merge or a new protocol will come that is backwards-compatible.
For now, IPv6 has no future, as it will not replace IPv4.
It designed to do so, but IPv4 never died. That is the problem.
The internet never switched, and never will the way it is now.
Why? Who forces you to do that?
Why? Just stick to the IPv4-only interface.
Who is trolling now?
Did you understand one bit what I said before?
Why IPv6 has problems to be accepted and new protocol?
IPv4 is the dominant protocol and will be for a long time, because IPv6 was never designed to be compatible. Not in coding, not in DNS not in everything.
At the time of design they thought to switch from IPv4 to IPv6 and the world would switch too.
The current IPv6 will never take over the way it is now. As everything needs to be coded in both…also DNS need to be programmed double.
Don’t start on Mail, then all hell breaks loose…dual stack there is the worst of the worst.
It needs to be redesigned. From DNS to compilers. Else the mess will be bigger and bigger.
We deal with old-junk…IPv4 and IPv6…it’s not modern. Time for IPv2024 
Then don’t use it. Nobody forces you to.
We don’t have to agree. I’m not responding to convince you, but to clarify for others how things truly are, given the confusion you keep creating concerning the facts.
1 Like
As mentioned before; that is precisely what A and AAAA do:
An A record stands for IPv4 and an AAAA record means IPv6. In other words; a system just as you like it; you give a ‘version’ with a request and get the right answer in response.
Which records besides A and AAAA (and probably their PTRs) are you referring to?
1 Like