Instagram DNS issues



  • pfSense 2.4.5-RC and pfBlockerNG-devel, pfSense domain is "home.lan".

    I have experienced some intermittent slowness with Instagram whereby posts, comments and stories fail to load or freeze. If I switch to a cellular network the issue goes away and force closing the app also temporarily resolves the issue.

    I decided to run Wireshark to attempt to understand what is going on, but I seem to be perplexed. Here is a snippet of what I'm seeing in the capture, the app attempting to resolve gobbledygook domains. Can anyone help shed some light here, this only occurs with Instagram.

    Packet capture on the wireless lan interface

    192.168.20.211	192.168.20.1	DNS	82	Standard query 0x9a81 A xqjkttqvecyfa.home.lan
    192.168.20.1	192.168.20.211	DNS	157	Standard query response 0x9a81 No such name A xqjkttqvecyfa.home.lan SOA a.root-servers.net
    
    192.168.20.211	192.168.20.1	DNS	81	Standard query 0x08b1 A ikaoounbbmzw.home.lan
    192.168.20.1	192.168.20.211	DNS	156	Standard query response 0x08b1 No such name A ikaoounbbmzw.home.lan SOA a.root-servers.net
    
    Packet capture on the WAN interface (not the above records, but similar issue)
    [My WAN IP]	192.5.5.241	DNS	78	Standard query 0x0850 A coxmvku OPT
    192.5.5.241	[My WAN IP]	DNS	1069	Standard query response 0x0850 No such name A coxmvku SOA a.root-servers.net RRSIG NSEC cpa RRSIG NSEC aaa RRSIG OPT
    

  • LAYER 8 Global Moderator

    Chrome is a browser that does this, there are other apps that might do this as well... They check random names looking to see if your isp is hijacking dns..

    I don't use instragram but would think its the same sort of test..



  • Thanks johnpoz. So there is not much I can do then?


  • LAYER 8 Global Moderator

    Do about what? Keeping your resolver from trying to look them up? You can stop home.lan from being looked up upstream for sure if that is what your asking... That would be simple change to your zone type to static vs transparent

    The one I would be a bit more curious about is the single label query??

    Standard query 0x0850 A coxmvku OPT

    Do you have qname-minimisation enabled? I don't think unbound should query for single label -- Give me a minute to test that..

    edit:
    Oh that is dnsmasq that you can set --domain-needed on, not sure if you can stop those from trying to be resolved with unbound... Hmmm now you got me curious



  • @johnpoz said in Instagram DNS issues:

    Hmmm now you got me curious

    ☺ quite an achievement then!

    I have switched to static zone and cannot see those odd DNS queries on the WAN interface, but they do seem to appear on the wireless interface:

    192.168.20.211	192.168.20.1	DNS	68	Standard query 0x18f6 A nsbcvwwe
    192.168.20.1	192.168.20.211	DNS	143	Standard query response 0x18f6 No such name A nsbcvwwe SOA a.root-servers.net
    

  • LAYER 8 Global Moderator

    But that nsbcvmwwe would still have gone out your public.. There doesn't seem a way to stop those with unbound.. If it concerns you - one simple solution. Is what I do is send all local queries to pihole first, which is running dnsmasq. Which has the domain-needed option set, so those single label domains never even get sent to unbound to try and resolve.

    I would be more curious to to what is generating the single label queries..

    What is that 192.168.20.211 machine? Phone, PC? What os is it running - you see those when you run instagram app?



  • @johnpoz 192.168.20.211 is an iOS device and those queries are only seen when running instagram. The failure to resolve those domains seems to be causing the issue of Instagra freezing when loading or streaming content.


  • LAYER 8 Global Moderator

    That name would be impossible to resolve - that is the correct answer.. Roots are telling you there that nsbcvwwe is NX, and that is coming from the SOA (source of authority)..

    A query fo an A record of just nsbcvwwe, could never resolve, ever - its not a fqdn query.

    If your having issues with instagram - you need to look elsewhere for the problem.



  • Yep, gotcha. But why is Instagram doing this, and why does it not occur on a cellular network?


  • LAYER 8 Global Moderator

    I doubt its instagram - are you loading instagram via chrome... Chrome does those odd queries..

    Here I just launched chrome on my pc and get stuff like this.

    chrome.jpg

    How do you know it doesn't occur on cellular - are you sniffing your dns traffic when your on cellular?

    https://isc.sans.edu/diary/Google+Chrome+and+weird+DNS+requests/10312/



  • Interesting. No, this is through the native Instagram app.

    I am not sniffing my cellular network but when on cellular, the app doesn't freeze when loading content, ever.


  • LAYER 8 Global Moderator

    Well maybe it "uses" chrome in the background? But that is the correct response to a NX query, ie NX ;)

    Maybe there is some other query that is failing, or taking a long time? That your missing which is the root of the problem.. But such odd queries are common - and the proper response would be NX.

    When I grab my phone later - wife is still sleeping and its in the bedroom, I will fire up the instragram app on my iphone and check it out..



  • I've ditched the native iOS app and reverted to using the web app, issue resolved :)


  • LAYER 8 Global Moderator

    You have to have an account to even do anything - shit, yeah not going to do that.. Maybe its login process that is causing the delay?



  • @johnpoz oh go on, use a burner email :p Would be great to have an experts view!

    I wouldn't think it is the login process as the hanging occurs once I am logged in to the app and browsing content.

    I get it, Instagram is the devil. I gave up Facebook years ago, perhaps this is the sign to give up Instagram too.



  • More of this craziness. Is it only me on this forum who uses Instagram on an iOS device?

    No.	Time	Source	Destination	Protocol	Length	Info
    1	0.000000	2001:8003:281d:c802:1c8d:e82f:68c5:c1b1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	93	Standard query 0xb8cd A instagram.com
    2	0.000419	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:1c8d:e82f:68c5:c1b1	DNS	221	Standard query response 0xb8cd A instagram.com A 52.201.106.96 A 35.169.42.209 A 34.236.133.23 A 35.168.91.186 A 34.236.182.19 A 34.232.61.249 A 3.224.36.18 A 52.201.22.32
    3	1.001545	2001:8003:281d:c802:1c8d:e82f:68c5:c1b1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	93	Standard query 0xb483 AAAA instagram.com
    4	1.001899	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:1c8d:e82f:68c5:c1b1	DNS	317	Standard query response 0xb483 AAAA instagram.com AAAA 2406:da00:ff00::34c9:1620 AAAA 2406:da00:ff00::22e8:3df9 AAAA 2406:da00:ff00::34c9:6a60 AAAA 2406:da00:ff00::3401:6e34 AAAA 2406:da00:ff00::23ad:9cc7 AAAA 2406:da00:ff00::23a9:2ad1 AAAA 2406:da00:ff00::3e0:2412 AAAA 2406:da00:ff00::22ec:8517
    5	4.962123	192.168.20.211	192.168.20.1	DNS	79	Standard query 0x0692 AAAA fccinagrga.home.lan
    6	4.962127	192.168.20.211	192.168.20.1	DNS	79	Standard query 0x1ef4 A fccinagrga.home.lan
    7	4.962297	192.168.20.211	192.168.20.1	DNS	81	Standard query 0x2749 A pjlgidxjdlzm.home.lan
    8	4.962371	192.168.20.211	192.168.20.1	DNS	81	Standard query 0xc0e6 AAAA pjlgidxjdlzm.home.lan
    9	4.962496	192.168.20.211	192.168.20.1	DNS	84	Standard query 0x8974 A pfyymxzqjmlnizw.home.lan
    10	4.962751	192.168.20.211	192.168.20.1	DNS	84	Standard query 0x0ba3 AAAA pfyymxzqjmlnizw.home.lan
    11	4.962793	192.168.20.1	192.168.20.211	DNS	154	Standard query response 0x1ef4 No such name A fccinagrga.home.lan SOA a.root-servers.net
    12	4.962796	192.168.20.1	192.168.20.211	DNS	154	Standard query response 0x0692 No such name AAAA fccinagrga.home.lan SOA a.root-servers.net
    13	4.962917	192.168.20.1	192.168.20.211	DNS	156	Standard query response 0xc0e6 No such name AAAA pjlgidxjdlzm.home.lan SOA a.root-servers.net
    14	4.962924	192.168.20.1	192.168.20.211	DNS	156	Standard query response 0x2749 No such name A pjlgidxjdlzm.home.lan SOA a.root-servers.net
    15	4.963025	192.168.20.1	192.168.20.211	DNS	159	Standard query response 0x8974 No such name A pfyymxzqjmlnizw.home.lan SOA a.root-servers.net
    16	4.963039	192.168.20.1	192.168.20.211	DNS	159	Standard query response 0x0ba3 No such name AAAA pfyymxzqjmlnizw.home.lan SOA a.root-servers.net
    17	4.970590	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	104	Standard query 0x0f01 AAAA pfyymxzqjmlnizw.home.lan
    18	4.970897	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	179	Standard query response 0x0f01 No such name AAAA pfyymxzqjmlnizw.home.lan SOA a.root-servers.net
    19	4.973581	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	95	Standard query 0xd548 AAAA pfyymxzqjmlnizw
    20	5.001613	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	170	Standard query response 0xd548 No such name AAAA pfyymxzqjmlnizw SOA a.root-servers.net
    21	5.975287	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	99	Standard query 0xa01c A fccinagrga.home.lan
    22	5.975291	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	99	Standard query 0x8546 AAAA fccinagrga.home.lan
    23	5.975725	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	101	Standard query 0x1e10 A pjlgidxjdlzm.home.lan
    24	5.975799	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	101	Standard query 0xda80 AAAA pjlgidxjdlzm.home.lan
    25	5.975808	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	104	Standard query 0x676d A pfyymxzqjmlnizw.home.lan
    26	5.975860	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	174	Standard query response 0xa01c No such name A fccinagrga.home.lan SOA a.root-servers.net
    27	5.975972	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	176	Standard query response 0x1e10 No such name A pjlgidxjdlzm.home.lan SOA a.root-servers.net
    28	5.975992	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	179	Standard query response 0x676d No such name A pfyymxzqjmlnizw.home.lan SOA a.root-servers.net
    29	5.976019	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	174	Standard query response 0x8546 No such name AAAA fccinagrga.home.lan SOA a.root-servers.net
    30	5.976069	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	176	Standard query response 0xda80 No such name AAAA pjlgidxjdlzm.home.lan SOA a.root-servers.net
    31	5.979891	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	92	Standard query 0x0a5d A pjlgidxjdlzm
    32	5.979896	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	90	Standard query 0xc511 AAAA fccinagrga
    33	5.979898	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	92	Standard query 0x1c24 AAAA pjlgidxjdlzm
    34	5.979905	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	95	Standard query 0xed57 A pfyymxzqjmlnizw
    35	5.980071	2001:8003:281d:c802:c046:3a94:9c02:53f1	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	90	Standard query 0xa97b A fccinagrga
    36	5.981185	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	170	Standard query response 0xed57 No such name A pfyymxzqjmlnizw SOA a.root-servers.net
    37	6.006253	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	165	Standard query response 0xa97b No such name A fccinagrga SOA a.root-servers.net
    38	6.006295	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	167	Standard query response 0x0a5d No such name A pjlgidxjdlzm SOA a.root-servers.net
    39	6.006345	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	165	Standard query response 0xc511 No such name AAAA fccinagrga SOA a.root-servers.net
    40	6.109798	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:c046:3a94:9c02:53f1	DNS	167	Standard query response 0x1c24 No such name AAAA pjlgidxjdlzm SOA a.root-servers.net
    41	33.777903	192.168.20.25	192.168.20.1	DNS	77	Standard query 0x0002 A ps-788.pubnub.com
    42	33.778299	192.168.20.1	192.168.20.25	DNS	130	Standard query response 0x0002 A ps-788.pubnub.com CNAME pubsub.pubnub.com A 54.249.82.169 A 54.249.82.168
    43	36.326473	192.168.20.211	192.168.20.1	DNS	78	Standard query 0xa733 A yjssygfqg.home.lan
    44	36.326479	192.168.20.211	192.168.20.1	DNS	78	Standard query 0x5502 AAAA upswygzru.home.lan
    45	36.326498	192.168.20.211	192.168.20.1	DNS	78	Standard query 0xd2a4 A upswygzru.home.lan
    46	36.326691	192.168.20.211	192.168.20.1	DNS	78	Standard query 0x490e AAAA yjssygfqg.home.lan
    47	36.327049	192.168.20.211	192.168.20.1	DNS	78	Standard query 0x8e61 AAAA qfjqynrec.home.lan
    48	36.327075	192.168.20.211	192.168.20.1	DNS	78	Standard query 0x7639 A qfjqynrec.home.lan
    49	36.327270	192.168.20.1	192.168.20.211	DNS	153	Standard query response 0x5502 No such name AAAA upswygzru.home.lan SOA a.root-servers.net
    50	36.327271	192.168.20.1	192.168.20.211	DNS	153	Standard query response 0xd2a4 No such name A upswygzru.home.lan SOA a.root-servers.net
    51	36.327273	192.168.20.1	192.168.20.211	DNS	153	Standard query response 0x490e No such name AAAA yjssygfqg.home.lan SOA a.root-servers.net
    52	36.327283	192.168.20.1	192.168.20.211	DNS	153	Standard query response 0xa733 No such name A yjssygfqg.home.lan SOA a.root-servers.net
    53	36.327418	192.168.20.1	192.168.20.211	DNS	153	Standard query response 0x8e61 No such name AAAA qfjqynrec.home.lan SOA a.root-servers.net
    54	36.327448	192.168.20.1	192.168.20.211	DNS	153	Standard query response 0x7639 No such name A qfjqynrec.home.lan SOA a.root-servers.net
    55	36.335718	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	98	Standard query 0x653d AAAA qfjqynrec.home.lan
    56	36.336319	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	173	Standard query response 0x653d No such name AAAA qfjqynrec.home.lan SOA a.root-servers.net
    57	36.338028	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	89	Standard query 0x8e19 AAAA qfjqynrec
    58	36.351236	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	164	Standard query response 0x8e19 No such name AAAA qfjqynrec SOA a.root-servers.net
    59	37.337286	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	98	Standard query 0x6f88 AAAA upswygzru.home.lan
    60	37.337389	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	98	Standard query 0x90ad A upswygzru.home.lan
    61	37.337689	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	173	Standard query response 0x90ad No such name A upswygzru.home.lan SOA a.root-servers.net
    62	37.337770	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	98	Standard query 0x00fb A qfjqynrec.home.lan
    63	37.337791	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	98	Standard query 0xc8c2 A yjssygfqg.home.lan
    64	37.337895	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	98	Standard query 0x8685 AAAA yjssygfqg.home.lan
    65	37.337937	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	173	Standard query response 0x6f88 No such name AAAA upswygzru.home.lan SOA a.root-servers.net
    66	37.337960	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	173	Standard query response 0x00fb No such name A qfjqynrec.home.lan SOA a.root-servers.net
    67	37.337981	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	173	Standard query response 0xc8c2 No such name A yjssygfqg.home.lan SOA a.root-servers.net
    68	37.338081	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	173	Standard query response 0x8685 No such name AAAA yjssygfqg.home.lan SOA a.root-servers.net
    69	37.341283	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	89	Standard query 0x61df AAAA upswygzru
    70	37.341291	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	89	Standard query 0xf8a8 A qfjqynrec
    71	37.341501	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	89	Standard query 0x7d58 A yjssygfqg
    72	37.341564	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	89	Standard query 0xbb15 AAAA yjssygfqg
    73	37.341626	2001:8003:281d:c802:d19:5c00:568b:ef7b	2001:8003:281d:c802:20d:b9ff:fe53:2a11	DNS	89	Standard query 0x6225 A upswygzru
    74	37.341803	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	164	Standard query response 0xf8a8 No such name A qfjqynrec SOA a.root-servers.net
    75	37.354938	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	164	Standard query response 0x7d58 No such name A yjssygfqg SOA a.root-servers.net
    76	37.354978	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	164	Standard query response 0x6225 No such name A upswygzru SOA a.root-servers.net
    77	37.366798	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	164	Standard query response 0x61df No such name AAAA upswygzru SOA a.root-servers.net
    78	37.370878	2001:8003:281d:c802:20d:b9ff:fe53:2a11	2001:8003:281d:c802:d19:5c00:568b:ef7b	DNS	164	Standard query response 0xbb15 No such name AAAA yjssygfqg SOA a.root-servers.net
    
    

  • LAYER 8 Global Moderator

    And what is in there that you think is odd?

    Or that didn't resolve? Or is problematic?

    Already went over what those random hostname queries are. If you don't want your phone to use IPv6, then don't setup IPv6 on your wireless network.

    Look at your response times - they are normal even.

    What I don't see is any queries for actual Instagram domains..



  • I started the trace then opened the app, I can see the first 4 lines of the capture requesting and resolve the Instagram domain, then it goes into a fizzy with the whole random domain that you have rightly mentioned is a common thing when using Chrome.

    Odd that it's problematic and doesn't seem anyone else running pfSense with DNS Resolver and pfBlocker is having any issues with the Instagram app.


  • LAYER 8 Global Moderator

    Have you tried turning off IPv6? Maybe your IPv6 is spotty?

    Not sure how I missed the instagram queries - but again, I don't see anything in there that didn't resolve how it should, nor any long response times..



  • Thanks, johnpoz. I'll try disabling IPv6, if it is spotty I'd expect to see it across other applications but it's worth a shot.



  • OK, a few hours after disabling IPv6 on my wireless LAN interface and I have had no issues with the Instagram app on iOS. I have left IPv6 enabled on other VLAN's as I am not seeing any issues there.

    Seems like one other person is also experiencing a similar issue:

    https://forum.netgate.com/topic/131271/when-6to4-ipv6-is-enabled-facebook-mobile-does-not-fully-load-all-videos-and-pictures-ios-and-android/21

    https://www.reddit.com/r/PFSENSE/comments/8luf26/had_to_disable_ipv6_for_facebook_mobile_apps_to/


  • LAYER 8 Global Moderator

    Well jknott will tell you different, but to be honest I am not really a fan of ipv6... Running dual stack leads to many issues to be honest.. I only run it on a few test devices..

    While it is the future for sure, there is nothing that says you need it or have to run it - or really to be honest any advantages to it currently - other than problems to be honest.

    Its not that there is anything wrong with the protocol, its the implementations and skill sets of people setting it up and maintaining to be honest.. When there is weirdness, its always a good troubleshooting step to disable it and see if issue goes away.

    I have been using it myself for 10 years, but only in test mode.. I serve up ntp to the public on it for example.. And run some dns for it.. And sure access some stuff (testing) via IPv6.. But in general is not active on my systems.. Other than my ntp server.

    My current isp doesn't even support it, and my last isp comcast - that is suppose to be one of the leaders just had so many issues not worth it. I just run a tunnel via HE for my ipv6 needs. And with that its pretty rock solid - but I just don't see a reason... One one of the major players only has IPv6, when you can only get to google via IPv6 - then its ready for primetime.. You would think that the game makers would love it - and they have yet to actually embrace it to be honest.

    So I wouldn't worry to much to just completely disabling it.. Unless you can name 1 service that actually requires it, there is no reason to run it is my point.

    Glad that you got your issue sorted.



  • On the other hand, I've been using IPv6 the day I managed to get l my hand on a "ISPv6" that seems to respect the entire RFC IPv6 related.

    My own ISPv4 only doesn't play well the IPv6 game : their own sites were "hard to visit" when using a IPv6 POP in Paris (I live in France). The site in question, www.orange.fr is IPv6 capable. And I have to say, these days, finally, things get better without me changing what so ever on my side.

    Apple devices always have been very IPv6 aware, as the last 3 Microsoft Windows releases, and most other, more public free OS's.

    For me, IPv6, has become "a set it and forget it" thing.
    I see as many IPv6 leases as IPv4 leases on my network - IPv4 devices fade out quickly.


  • LAYER 8 Global Moderator

    I hear ya - it is suppose to be working int he background with user not having to do anything, and it will just work.. And this can be the case for many users.. But then there is that problem site that isn't doing it right, or the client that doesn't like to switch to IPv4.. Or the users ISP implementation is borked.

    He problem might be his dealy is related to instagrams IPv6 is borked, or his connection to whatever via IPv6 is not working as it should.. And it takes time for the device to try ipv4... This is where you see many of the issues - when there is AAAA client that is dual stack will prefer the IPv6.. Only when this fails will it do the IPv4 connection. This causes delays and issues that the user is unwilling to deal with.

    My point is if your seeing such issues - why put yourself through such grief, when there really isn't 1 site, other than maybe some darkweb or p0rn that is only IPv6.. All of the major players that do support IPv6, also have IPv4.. And many of the major players don't even support IPv6 yet..

    Check out https://whynoipv6.com/ for some major sites that don't yet even support IPv6 for their actual site.

    Its not that the protocol doesn't work - its the transition that is problematic and that everyone is not on it. And there are still many applications and software that are not yet up to speed.. Here is good example of that.
    https://blog.apnic.net/2018/09/17/microsoft-making-progress-towards-ipv6-only/


Log in to reply