DS Lite internet connection failed: Reason for error: 2, AFTR sls-ludw.bsr.telefonica.de cannot be resolved

Moin,

are U using the O2 DNS?

What type of router are U using?

Hi

i am using a Fritz!Box 6660 Cable

i was using custom DNS so the first thing I did to try to fix things was to reset the router to the factory settings, however it did not change anything. 

Thanks

If you use the CLI type

nslookup sls-ludw.bsr.telefonica.de 62.109.121.1

Will  you get a result?

Name:    sls-ludw.bsr.telefonica.de
Address:  2a02:3040:0:200::1

I get the following output:

DNS request timed out.
Timeout was 2 seconds

Also, my router also can’t get the proper date. It says it is connected using ipv6 since 01/01/1970 01;05

and the ipv6 I have, even after a factory reset is the ip i had before the issue. 

But when I try to ping 2a02:3040:0:200::1 from my computer I get an answer back. 
 

PS: I just discovered the ändern button and will use it for further modification in my future posts. 

I like German but unfortunately I can’t have this kind of conversation… yet!

the MAC address in Mein O2 is the same one than the one from my router…

No problem, you have a choice...

Shit…

I have dropped a message on WhatsApp and call tomorrow if I don’t get an answer. 
thank you for your quick answers !

Hi @grumlu ,
welcome to our community.
I also recommend that you call our colleagues on the hotline. They will certainly be able to help you. I keep my fingers crossed that the cause can be found and fixed quickly.
Best regards
Larissa

Hi Larissa,

Thank you for your answer. 
Full story: we contacted the support on Monday, a ticket was opened.

we had a technician on Tuesday and another on Wednesday checking the attenuation in the cable. They found an issue, told us to use another plug and left. 
we tried the other plug, same issue. 
the ticket is still opened and the status did not move since Monday
so I looked more into the fact that ipv6 is connected, and posted here.

As suggested schluej, I called the support again, explained that the issue doesn’t lie in the cable but with name resolution of that DS Lite server. I was told nothing could be done.

Today I decided to rent a server with Ipv6 and ipv4, set up a VPN with ipv6 tunneling and used my NAS as a gateway for the whole local network, and as expected, I have full internet access, no packet loss, 350M/s. 

I am a bit desperate because I don’t know how to make O2 acknowledge there is a software issue between my router and their DS Lite server, and it has been almost a week now. 
 

Hello @grumlu,

that is quite some strange behaviour that you are experiencing there. Somehow I find it a bit hard to believe that a DNS would not respond to IPv4 queries, especially since a typical DSN has at least a secondary one that will be used should the primary show any issues. We also did not recieve any more questions regarding this so I wonder if this may have something to do with the question you asked some months ago?

Were you maybe using a seperate Ipv4 DSN entry on your computer? 

Regards,

Lars

Hi Lars,

Thank you for your answer.

I believe I would not have this issue without a DS Lite setup, however I have come to accept that it is how it works :)

No, I am not using a custom DNS on my computer, and it is the fritz box that complains not to be able to resolve the name, even after a factory reset with only one computer connected with Ethernet and DHCP enabled:

Hello @grumlu,

I read some articles and threads regarding this in the vast saces of the internet. It seems like in the past it helped now and then to restrt the router, maybe even several times. 

For whatever reasons the address resolution for that one host does not work as it should, even if the address can be resolved via other connections (i.e.: my DSL connection).

Could you post a screenshot (or just the addresses) of the used DSN server that are shown in the Fritzbox? I assume they should be visible in the Internet -> Online Monitor page. Not using a cable connection but a Fritzbox so I assume the menus are kind of similar :-)

Regards,

Lars

Hi Lars,

I could not find the « used DNS » servers, however I have this configured:

and for the online monitor page, here is what I have:

I have restarted my Fritz!Box several times per day since last Monday, without any result 😕

Thanks

Hey everyone,

has there been a solution to this already? I am currently running into the very same issue on my Kabel-DSL account: My Fritz!Box 6590 Cable easily gets an IPv6 address but then does not get an IPv4 via DS-Lite with the error message:

“Internetverbindung DS-Lite ist fehlgeschlagen: Fehlergrund 2, AFTR lej.tc.bsr.telefonica.de kann nicht aufgelöst werden”

According to the hotline everyting on O2-side is fine. Also the correct CM-MAC is assigned in the customer portal in my account. The cable infrastructure is owned by PYUR (former Telecolumbus) if this is important. I reset the FritzBox multiple times already, also no custom DNS is used.

Hallo zusammen,

gibt es für dieses Problem bereits eine Lösung? Ich erhalte mit meiner FritzBox 6590 Cable aktuell denselben Fehler:

“Internetverbindung DS-Lite ist fehlgeschlagen: Fehlergrund 2, AFTR lej.tc.bsr.telefonica.de kann nicht aufgelöst werden”

Ich erhalte eine IPv6-Adresse, aber die Aushandlung von IPv4 via DS-Lite schlägt fehlt…

Ich habe die Box schon mehrmals zurückgesetzt, auch habe ich den DNS auf Werkseinstellungen gelassen. Nichts scheint zu helfen, ich bin etwas verzweifelt.

VIele Grüße,

Lisa & Jan

Hello @DerGeraet123, welcome to our o2 community :-)

If you encounter issues with the DNS resolution and even several reconnects or maybe resetting the router does not help at all I can only recommend to get in touch with our technical departement so they can have a deeper look into this. Since wei can not promise that you will reach an english speaking technician I recommend to call with a friend of yours who speaks german if you don’t.

Regards,

Lars

Hi @o2_Lars 

just FYI: I contacted the technical support of O2 and they told me that basically the owner of the cable infrastructure (in my case PYUR) messed up their DNS entries.

I documented everything here in case someone runs into similar problems in the future: