DNS Issues

[LD0291]

Sky's DNS servers are currently resolving the wrong IP addresses for the isc2.org subdomains – please see an example below:

nslookup
Default Server: SkyRouter.Home
Address: 192.168.0.1

> www.isc2.org
Server: SkyRouter.Home
Address: 192.168.0.1

Non-authoritative answer:
Name: www.isc2.org
Address: 90.207.238.183 <<< incorrect address

> server 8.8.8.8
Default Server: dns.google
Address: 8.8.8.8

> www.isc2.org
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: www.isc2.org
Address: 107.162.133.105 <<< correct address

I imagine other domains are resolving incorrectly too.

[Skull+Treaty]

@LD0291 

 To related to your DNS  issue...I've been in talks with ICS2 for years, do my head in! Looking for something in particular, CISSP?

ISACA may be a better fit

[LD0291]

Thanks for the reply - I'm already an ISC2 member, so just want to be able to connect to manage my account / participate in their community without having to change my DNS settings.

[LD0291]

Now resolved - thank you!

nslookup
Default Server: SkyRouter.Home
Address: 192.168.0.1

> www.isc2.org
Server: SkyRouter.Home
Address: 192.168.0.1

Non-authoritative answer:
Name: www.isc2.org
Address: 107.162.133.105 <<< correct address

[Jenny+wwh]

I have seen that Sky Boradband Consumer service has an intercept layer for all DNS queries which can result in stale data problems when servers change IP addresses. Also DNS queries pointed towards non-exitant DNS server will still suceeded but may provide old or incorrect data.

Using the Google dig tool on 

https://toolbox.googleapps.com/apps/dig/

Gives the correct result but the command line equivlent look up that is suposed to be using Goggle DNS server ....

% dig  @8.8.8.8  domainname.com MX

Gives a stale out of date answer  hours after the result should have changed.

Given a non-existant DNS server with an address similar to Googles connection is not possible 

% ping 8.8.8.99 

PING 8.8.8.99 (8.8.8.99): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

^C

but DNS look up succeds 

 % date; dig  @8.8.8.99  apple.com MX      

Mon  2 May 2022 14:29:38 BST

; <<>> DiG 9.10.6 <<>> @8.8.8.99 apple.com MX

; (1 server found)

;; global options: +cmd
......snip 

;; ANSWER SECTION:

apple.com. 3600 IN MX 10 rn-mailsvcp-ppex-lapp15.apple.com.

apple.com. 3600 IN MX 10 rn-mailsvcp-ppex-lapp24.apple.com.

apple.com. 3600 IN MX 10 rn-mailsvcp-ppex-lapp34.apple.com.

apple.com. 3600 IN MX 10 rn-mailsvcp-ppex-lapp35.apple.com.

apple.com. 3600 IN MX 10 rn-mailsvcp-ppex-lapp44.apple.com.

apple.com. 3600 IN MX 10 rn-mailsvcp-ppex-lapp45.apple.com.

apple.com. 3600 IN MX 10 ma1-aaemail-dr-lapp01.apple.com.

.......
Gets you an answer. How is this possible or correct ????

This has the follow on implications
1) DNS lookup results can be stale or incorrect hours after a change at source.
2) Changing the DNS settings on your PC/Device  makes no difference as the "Sky Results" are used in any case. 

3) All DNS lookups can be recorded / traced at the ISP level.
4) Time to live should be set low on domains to avoid any excuse by Sky for keeping stale data when noone else does.

Only solutions are to use external tools to check against Sky DNS results. Or use a VPN.