DNS resolution for skybroadband.com

[BeSKyID]

Hi

As per the title, skybroadband.com no longer resolves from the Sky router, but does resolve from external DNS services.

Is everyone else seeing this behaviour?

Regards

Ben

[JimM1]

@BeSKyID The router does resolve it via the Sky primary and secondary DNS server links that ar preset on the Sky Hub! You cannot change those if that is what you are getting at with the hub!

[BeSKyID]

Perform a DNS lookup from:
https://192.168.0.1/sky_diagnostics.html

Unknown host.

I used to have a latency check on the DNS servers, the reverse being dns1.skybroadband.com.

If you do a reverse lookup on the Sky DNS servers do you get anything back?

Regards

Ben

[JimM1]

@BeSKyID Unable to test, retired the sky SR203 hub yesterday back into it's box after seeing all was ok for the 10 week period, from my old status sheet DNS server's are shown as 90.207.238.97 and 99 but there may be more than one.!

[BeSKyID]

ping -a 90.207.238.97
Pinging dns1.skybroadband.com [90.207.238.97] with 32 bytes of data

ping dns1.skybroadband.com
Ping request could not find host dns1.skybroadband.com. Please check the name and try again.

If you try the above bold commands from a PC command window, I expect you will see the same. Reverse works, forwards doesn't.

If you then do (on separate lines, using Google 8.8.8.8 as DNS):
nslookup

server 8.8.8.8

dns1.skybroadband.com

You should get:
Non-authoritative answer:
Name: dns1.skybroadband.com
Address: 90.207.238.97

How can I flag this to someone at Sky who might understand this issue?

[JimM1]

@BeSKyID The return, just not sure what you are looking for? It even returned the IPV6 also. Have added ping for you also!

C:\Users\Jim Murray>nslookup dns1.skybroadband.com
Server: UnKnown
Address: 2a02:c7e:5cbb:f600::1

Non-authoritative answer:
Name: dns1.skybroadband.com
Address: 90.207.238.97

C:\Users\Jim Murray>ping 90.207.238.97

Pinging 90.207.238.97 with 32 bytes of data:
Reply from 90.207.238.97: bytes=32 time=10ms TTL=250
Reply from 90.207.238.97: bytes=32 time=12ms TTL=250
Reply from 90.207.238.97: bytes=32 time=11ms TTL=250
Reply from 90.207.238.97: bytes=32 time=11ms TTL=250

Ping statistics for 90.207.238.97:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 11ms

[Chrisee]

@BeSKyID Sky's DNS will return different links for addresses within sky.com domains which when you think about it is quite sensible as they are internal within Sky's own network. The addess skybroadband.com maps to sky.com/broadband when I test it. I suspect you would see similar behaviour from BT's DNS for their internal addresses.

[BeSKyID]

The thread title should really be DNS resolution for dns1.skybroadband.com

So if you try the below:
- -

nslookup
> server 90.207.238.97
Default Server: dns1.skybroadband.com
Address: 90.207.238.97

> dns1.skybroadband.com
Server: dns1.skybroadband.com
Address: 90.207.238.97

*** dns1.skybroadband.com can't find dns1.skybroadband.com: Server failed

Am I the only one that - when using Sky's own DNS server in nslookup - gets the above result?

It used to work a few weeks ago.