DNS homepage display error
-
Simply a display error on the dashboard of my homebuilt box, I'm sure that would be an interesting DNS address . . .
peace and love, thanks for your hard work.
-
I give up. I know, its Friday, lots of work and so on, but I do not see the issue.
I still find my :
way better.
-
@Gertjan The issue is cosmetic. but I guess thanks for contributing?
-
@herozero
Still don't getting it. A cosmetic error ? -
You think
::1is incorrect? That's IPv6 localhost. That's expected there. -
@stephenw10 Another reason I hate IPv6. No one really understands it.
-
Holding out for IPv8!
-
@DefenderLLC said in DNS homepage display error:
No one really understands it.
I am fairly sure there are lots of people understand it, I do for sure ;) I would suggest you go get your IPv6 certification from Hurricane Electric, its free and while not all inclusive sort of info or test. But running through the test will get you familiar with all the basic concept as you do your research on the question being asked, etc. And once you reach SAGE you will get a free tshirt ;)
I still wear mine now and then and it was back in 2011 ;)
-
@johnpoz I just mean most people. I have worked in network engineering at Dell, GM, and AIG and none of them will touch it.
-
@DefenderLLC yeah its been a really slow adoption... I use to work for a large MSP, and had many many customers.. Not one of them wanted or even asked for IPv6.. Other than on stupid RFC documentation they sent in (request for quote).. But then never followed through with it..
And I honestly looked for any projects I could get involved in - there were none.. Globally None..
I finally got involved in getting a /32 from arin, and creating the routing objects for it via our ASNs etc.. There was one project that was being worked on.. But the nature of the projected actually required it because they were doing something with mobile comms in cars, and there are a shit ton of cars ;) heheh Wonder whatever happened with that project? I completed my portion of all the IPv6 routing, and delegation, etc. I know they brought up some connections in the IPv6 space.. But then I left that company a couple of years back.
They really couldn't easy do what they were wanting to do if they would of tried doing it with IPv4 - just not enough IP space available - even if you owned all of it ;)
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.11 | Lab VMs 2.8, 24.11 -
Sage Level. I love it.
-
@johnpoz Meanwhile, AT&T just "doubled" the cost for any static IPv4s for residential customers. So my /29 just went from $15/mo to $30/mo. Still keeping it though!
-
Thanks for the info, I love spurring a good chat. Yeah I had no idea it was standard for IPv6 localohost, it was not showing in 23.3 which is what really caught my eye. Cheers
-
@stephenw10 I'm having MAS90 and MAS200 ERP ptsd just seeing the word SAGE.
-
The US Government is mandating IPv6 now. They are even starting to shift some of their internal services to IPv6. It will only be a matter of time now before everyone has to learn it, and has no choice.
-
@behemyth said in DNS homepage display error:
The US Government is mandating IPv6 now. They are even starting to shift some of their internal services to IPv6. It will only be a matter of time now before everyone has to learn it, and has no choice.
I work for a DoD agency and I have yet to see our installation switch from the good ol IPv4.
-
@rtorres haha - yeah when has the gov/dod done stuff on time ;)
They still have time to get to the 80% mark ;)
c. Require that at least 80 percent of IP-enabled assets on DoD networks are operating in IPv6-only environments by the end of FY 2025.
edit: quick once over that doc, looks there is really no actual drop dead date, because they have a clause where if stuff doesn't support IPv6 it can stay, and just need to come up with a plan to retire it.. Which could be 20 years from now knowing the gov/dod, and some the really OLD equipment I worked on when I was in the navy..
Seems more like they are saying new equipment needs to be IPv6.. Which is great..
And also a clause where you can file for an exception ;) to the rule..
-
@johnpoz They're probably still using Cisco 6500s too. LOL
-
@DefenderLLC Oh I wouldn't doubt it - I have seen those still in the wild, and not gov or dod ;)
I would have to check with my buddy, but they still had a 6509 in the DC, pretty sure last time I checked with him the uptime was like 12 years ;)
-
@johnpoz I remember deploying hundreds of 6509s and 6913s when I worked at Dell from the mid-90s to early 2000s. We had them everywhere as DC and mid-core switches along with those Cisco Lightstreams (ATM). I also remember when the gig over copper blades came out which was a big deal back then.
I'm really showing my age here... LOL
