BT DNS issue :: BT Broadband :: think broadband

User comments on ISPs
>> BT Broadband

Pages in this thread: 1 | [2] | (show all)

Print Thread

Brunel
(experienced) Tue 07-Jun-22 20:25:41

Re: BT DNS issue

[re: mbames] [link to this post]

ares.krystal.co.uk [77.72.0.130]

amiga_dude
(member) Tue 07-Jun-22 20:28:59

Re: BT DNS issue

[re: mbames] [link to this post]

Would it be posiable to change your NS to use one at cloudflare?
https://www.cloudflare.com

zeb99
(learned) Tue 07-Jun-22 22:07:27

Re: BT DNS issue

[re: amiga_dude] [link to this post]

I'm not sure using Cloudflare will help that much as I'm getting differing results from multiple queries:

Text

$ dig mail.dorsetiam.org.uk @1.1.1.1
 ; <<>> DiG 9.16.1-Ubuntu <<>> mail.dorsetiam.org.uk @1.1.1.1
;; global options: +cmd;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10341;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
 ;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232;; QUESTION SECTION:
;mail.dorsetiam.org.uk.         IN      A 
;; ANSWER SECTION:mail.dorsetiam.org.uk.  14400   IN      CNAME   dorsetiam.org.uk.
dorsetiam.org.uk.       14400   IN      A       77.72.0.130 
;; Query time: 259 msec;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Jun 07 21:15:23 BST 2022;; MSG SIZE  rcvd: 80
 $ dig mail.dorsetiam.org.uk @1.1.1.1
 ; <<>> DiG 9.16.1-Ubuntu <<>> mail.dorsetiam.org.uk @1.1.1.1
;; global options: +cmd;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11365;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
 ;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232;; QUESTION SECTION:
;mail.dorsetiam.org.uk.         IN      A 
;; ANSWER SECTION:mail.dorsetiam.org.uk.  600     IN      A       63.141.242.44
 ;; Query time: 327 msec
;; SERVER: 1.1.1.1#53(1.1.1.1);; WHEN: Tue Jun 07 21:15:25 BST 2022
;; MSG SIZE  rcvd: 66$ dig mail.dorsetiam.org.uk @1.1.1.1
 ; <<>> DiG 9.16.1-Ubuntu <<>> mail.dorsetiam.org.uk @1.1.1.1
;; global options: +cmd;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14359;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
 ;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232;; QUESTION SECTION:
;mail.dorsetiam.org.uk.         IN      A 
;; ANSWER SECTION:mail.dorsetiam.org.uk.  14400   IN      CNAME   dorsetiam.org.uk.
dorsetiam.org.uk.       14400   IN      A       77.72.0.130 
;; Query time: 71 msec;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Jun 07 21:15:40 BST 2022;; MSG SIZE  rcvd: 80
$ dig mail.dorsetiam.org.uk @1.1.1.1 
; <<>> DiG 9.16.1-Ubuntu <<>> mail.dorsetiam.org.uk @1.1.1.1;; global options: +cmd
;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27313
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 
;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:;mail.dorsetiam.org.uk.         IN      A
 ;; ANSWER SECTION:
mail.dorsetiam.org.uk.  600     IN      A       81.17.18.197 
;; Query time: 143 msec;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Jun 07 21:16:38 BST 2022;; MSG SIZE  rcvd: 66

Edited by zeb99 (Tue 07-Jun-22 22:08:27)

zeb99
(learned) Tue 07-Jun-22 22:23:10

Re: BT DNS issue

[re: mbames] [link to this post]

I would suggest you get in contact with Fasthosts to fix the first nameserver:

Text

$ whois dorsetiam.org.uk
     Domain name:
        dorsetiam.org.uk 
    Data validation:        Nominet was able to match the registrant's name and address against a 3rd party data source on 12-Jun-2015
     Registrar:
        Fasthosts Internet Ltd [Tag = LIVEDOMAINS]        URL: http://www.fasthosts.co.uk
     Relevant dates:
        Registered on: 03-Apr-2006        Expiry date:  03-Apr-2027
        Last updated:  04-Mar-2022 
    Registration status:        Registered until expiry date.
     Name servers:
        ns1.krsytal.co.uk        ns2.krystal.co.uk         139.162.230.184
     WHOIS lookup made at 22:10:36 07-Jun-2022

It should, presumably, be ns1.krystal.co.uk, not ns1.krsytal.co.uk - right letters, wrong order!

amiga_dude
(member) Wed 08-Jun-22 08:13:02

Re: BT DNS issue

[re: zeb99] [link to this post]

In reply to a post by zeb99:
It should, presumably, be ns1.krystal.co.uk, not ns1.krsytal.co.uk - right letters, wrong order!

https://www.youtube.com/watch?v=uMPEUcVyJsc

miken06
(committed) Wed 08-Jun-22 08:50:25

Re: BT DNS issue

[re: zeb99] [link to this post]

Just to expand on what zeb99 has correctly identified.

The documented correct nameservers are listed on https://help.krystal.uk/domains/what-are-krystal-s-n...

They should be (.co.uk seems to resolve also):
ns1.krystal.uk
ns2.krystal.uk

They are currently:
ns1.krsytal.co.uk
ns2.krystal.co.uk 139.162.230.184

i.e. as zeb99 says ns1 has a misspelling, ns2 is a concatenation of the nameserver domain and it's IP address when it should just be the domain, it's possible systems are actually ignoring everything after the spaces.

You're getting weird resolutions because the wrong ns1 entry appears to have been setup to send valid replies and intercept traffic.
Whether you get valid or invalid resolutions depends which nameserver entry is used, then it'll get cached for a period of time.

$ dig mail.dorsetiam.org.uk @ns1.krsytal.co.uk +short
81.17.18.197

You should be able to update the nameservers via the Fasthosts control panel, it can take quite a while to update everywhere though.

Edited by miken06 (Wed 08-Jun-22 08:51:26)

mbames
(committed) Wed 08-Jun-22 09:30:41

Re: BT DNS issue

[re: miken06] [link to this post]

Cheers all - good spot. Update applied.

That configuration with Fasthosts has been like that for years, so I'm going to guess that someone has recently registered the domain krsytal.co.uk and whacked a public name server on it ns1

Text

C:\Users\matth>nslookup
Default Server:  pi.holeAddress:  192.168.100.15
 > server ns1.krsytal.co.uk
Default Server:  ns1.krsytal.co.ukAddress:  81.17.29.150
 > dorsetiam.org.uk
Server:  ns1.krsytal.co.ukAddress:  81.17.29.150
 Name:    dorsetiam.org.uk
Address:  81.17.29.146 
> balls.comServer:  ns1.krsytal.co.uk
Address:  81.17.29.150 
*** ns1.krsytal.co.uk can't find balls.com: Query refused>

Arh yes, recently registered:

Text
1 23 45 6	whois:krsytal.co.uk Name ValueRegistered on 02-Jun-2022 Expiry date 02-Jun-2023Last updated 02-Jun-2022 WHOIS lookup made at 09:33:29 08-Jun-2022

Vodafone Fibre (Superfast2 - 80/20), Draytek 130, DrayTek 2925, DrayTek AP-910c x 2
(Gone but not forgotten: AP-700, 2820n x 2, 2800vg, 2800, HG612)

Speedtests:
ThinkBB - Mini | ThinkBB - Full | Speedtest.net

Edited by mbames (Wed 08-Jun-22 09:34:42)

zeb99
(learned) Wed 08-Jun-22 12:20:01

Re: BT DNS issue

[re: miken06] [link to this post]

In reply to a post by miken06:
They are currently:
ns1.krsytal.co.uk
ns2.krystal.co.uk 139.162.230.184

i.e. as zeb99 says ns1 has a misspelling, ns2 is a concatenation of the nameserver domain and it's IP address when it should just be the domain, it's possible systems are actually ignoring everything after the spaces.

It's automatic and just means that Nominet are publishing a glue record for that entry - the name servers for krystal.co.uk are within krystal.co.uk. If there wasn't a glue record then you wouldn't be able to find the IP address of the nameservers. The same is true for krystal.uk.

Oliver341
(eat-sleep-adslguide) Wed 08-Jun-22 13:23:20

Re: BT DNS issue

[re: mbames] [link to this post]

In reply to a post by mbames:
That configuration with Fasthosts has been like that for years, so I'm going to guess that someone has recently registered the domain krsytal.co.uk and whacked a public name server on it ns1

Which suggests to me that you're not the only person to make this typo, and someone wants to capitalise on some of this nameserver typo traffic.

Oliver.

Edited by Oliver341 (Wed 08-Jun-22 13:24:17)

mbames
(committed) Wed 08-Jun-22 17:44:20

Re: BT DNS issue

[re: Oliver341] [link to this post]

In reply to a post by Oliver341:
Which suggests to me that you're not the only person to make this typo, and someone wants to capitalise on some of this nameserver typo traffic.

Its looks that way. I've pointed that out to Krystal. Not really sure what they could, other than script up a process to check the nameservers for domains they are handling are actually correct and not suffering from typos and then contact those customers.

Edited by mbames (Wed 08-Jun-22 17:44:48)

Pages in this thread: 1 | [2] | (show all)

Print Thread

Jump to