Connected to gateway but not dns server

[#1]

That certainly looks as though the DNS look ups aren't happening
Can you try ping 212.159.6.9 also ping 212.159.6.10
Can you edit your previous post and remove the last 5 characters of the serial number.

[#2]

Well its taken 10 mins to post this as it was down
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

ping 212.159.6.9
Pinging 212.159.6.9 with 32 bytes of data:
Reply from 212.159.6.9: bytes=32 time=35ms TTL=59
Reply from 212.159.6.9: bytes=32 time=33ms TTL=59
Reply from 212.159.6.9: bytes=32 time=73ms TTL=59
Reply from 212.159.6.9: bytes=32 time=91ms TTL=59
Ping statistics for 212.159.6.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 91ms, Average = 58ms

ping 212.159.6.10
Pinging 212.159.6.10 with 32 bytes of data:
Reply from 212.159.6.10: bytes=32 time=34ms TTL=59
Reply from 212.159.6.10: bytes=32 time=34ms TTL=59
Reply from 212.159.6.10: bytes=32 time=34ms TTL=59
Reply from 212.159.6.10: bytes=32 time=34ms TTL=59
Ping statistics for 212.159.6.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 34ms, Average = 34ms

[#3]

and now
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
ping 212.159.6.10
Pinging 212.159.6.10 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 212.159.6.10: bytes=32 time=2992ms TTL=59
Reply from 212.159.6.10: bytes=32 time=69ms TTL=59
Ping statistics for 212.159.6.10:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 69ms, Maximum = 2992ms, Average = 1530ms
ping 212.159.6.9
Pinging 212.159.6.9 with 32 bytes of data:
Reply from 212.159.6.9: bytes=32 time=55ms TTL=59
Reply from 212.159.6.9: bytes=32 time=56ms TTL=59
Reply from 212.159.6.9: bytes=32 time=59ms TTL=59
Reply from 212.159.6.9: bytes=32 time=53ms TTL=59
Ping statistics for 212.159.6.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 59ms, Average = 55ms

[#4]

When you say it was down, I assume you mean the Internet PPP side was not responding, rather than you have lost sync?
The big question remains, is the TG582n spoofing (that's when it gives 198.18.1.xxx addresses) because it's faulty or because the DNS lookups are failing?
Can you get RSL setup and running? The modem/router choice is straight forward and the rest of the setup is a previously given. Set the ping address in it to 212.159.6.9. Before you start to do that delete the old .ini configuration file.

[#5]

btw what exchange are you on? PM me if you don't want to say in an open post.

[#6]

EABMK

[#7]

I've set up the routerstats as before. Connection speed and noise margin both on zero    there is a changing number in the bottom rhs currently says 62

[#8]

have just run pings and tracert. ntp.plus.net did 3 hops and timed out:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
tracert ntp.plus.net
Tracing route to ntp.plus.net [198.18.1.215]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  dsldevice.lan [192.168.1.254]
  2    39 ms    35 ms    40 ms  lo0-central10.pcl-ag03.plus.net [195.166.128.184]
  3    37 ms    36 ms    35 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.168]
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *        *        *    Request timed out.
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14    *        *        *    Request timed out.
15    *        *        *    Request timed out.
16    *        *        *    Request timed out.
17    *        *        *    Request timed out.
18    *        *        *    Request timed out.
19    *        *        *    Request timed out.
20    *        *        *    Request timed out.
21    *        *        *    Request timed out.
22    *        *        *    Request timed out.
23    *        *        *    Request timed out.
24    *        *        *    Request timed out.
25    *        *        *    Request timed out.
26    *        *        *    Request timed out.
27    *        *        *    Request timed out.
28    *        *        *    Request timed out.
29    *        *        *    Request timed out.
30    *        *        *    Request timed out.
Trace complete.

[#9]

Damn, that's another correction to my Guide   RSL puts the wrong login username in the box for the TG582n, it should be admin all in lower case.
The number incrementing at the bottom is the number of samples taken. When it's working you should also see the Start date, Noise Margin and the Connection Speed in boxes at the bottom.
What's the ping plotter graph looking like? - Attach one to a post.
Can you also log into the TG582n and go to the Internet box and click Disconnect to drop your PPP session, wait about 30 seconds and then click Connect. You could then do another tracert to ntp.plus.net, we'll see if being on a different Gateway makes any difference.

[#10]

" RSL puts the wrong login username in the box for the TG582n"
It is also wrong on RS Full - IIRC   it said Administrator -caught me out for a while when I swapped routers at the weekend.
I would also like to chip in with another red herring. ( Found something I am good at at last!!!  )
OP is on Win 10 and there seems to have been a DNS problem looking at this thread seems to be since April:
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/windows-10-dns-issue/693c...
EDIT  wouldnt recommend downloading any files it suggests though
 

[#11]

Yes neither would I recommend downloading anything. I'll re-read it in slower time and suggest some checks.

[#12]

PING 212.159.6.9
Pinging 212.159.6.9 with 32 bytes of data:
Reply from 212.159.6.9: bytes=32 time=102ms TTL=59
Reply from 212.159.6.9: bytes=32 time=99ms TTL=59
Reply from 212.159.6.9: bytes=32 time=148ms TTL=59
Reply from 212.159.6.9: bytes=32 time=77ms TTL=59
Ping statistics for 212.159.6.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 148ms, Average = 106ms
PING 212.159.6.10
Pinging 212.159.6.10 with 32 bytes of data:
Reply from 212.159.6.10: bytes=32 time=35ms TTL=59
Reply from 212.159.6.10: bytes=32 time=38ms TTL=59
Reply from 212.159.6.10: bytes=32 time=36ms TTL=59
Reply from 212.159.6.10: bytes=32 time=36ms TTL=59
Ping statistics for 212.159.6.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 38ms, Average = 36ms

I had already changed the login to admin.  I have double checked everything and it is correct. Might the password have got addled with the download? Don't seem to be able to attach the ipad?

[#13]

In that tracert it has ntp.plus.net as  198.18.1.215  when I do it it says 212.159.13.49  is that something spoofing?

[#14]

Yes it is spoofing cedlor, I mentioned it in reply #108. and well done for the spot on the Windows 10 DNS issues, we'll look into that a bit more shortly.
The TG582n login password is OK because you used it to get the stats and again to check the firmware update.
I'm thinking RSL is not getting any data from the TG582n because it has to Telnet in to get it with this modem/router, and Telnet has to be active, if it is, there could also be two Telnet sessions open on the 582n which will prevent any more, so they'll need to be killed. I'm not familiar with Window 10, so I'll have to check on that.
As for the iPad, I've no real idea, but I'd say something like delete any previous wireless connections it has set up and then create a new one.
As for the tracert to ntp.plus.net do tracert to 212.159.6.9 instead for now.

[#15]

I had to set up telnet on win7 it was disabled and it appears win 10 may be the same
https://www.rootusers.com/how-to-enable-the-telnet-client-in-windows-10/