DNS Advice - Site not visible on Plusnet

[#1]

I can see the results of the dial test have been passed through for further investigation.

[#2]

Were you intending to answer my question at the top of page 4 @Chris or deliberately ignoring it?

Fine either way.. it would just be nice to know where we users stand on some aspects of customer service.

[#3]

Sorry but I'm not going to provide information about how our DNS servers are built, nor the software on them.

[#4]

From that I can conclude it is policy then.

Thats fine Chris but if you'd said that the first time round that would have made it crystal clear - your previous reply was vague!

It was only a simple question which could have been given a simple answer! 

[#5]

Oh well, been away on holiday. Checked access from various networks using both my laptop and computers on Ferry and holiday resort. Site is visible on all but not visible when we got home... Oh and I got an email from Plusnet telling me that the site is visible on ALL checks carried out by Plusnet... That's great, but they didn't actually visit the site but a server on WEEBLY where the site used to be hosted and hasn't been there for a few months...

"

Apologies about the delay in getting back to you/, I've taken a look at the DNS for this domain and I received a response on all my requests.  do you know the administrator of the website ?
they haven't blocked your Plusnet IP for any reason have they? I noticed you have a statically assigned address and it's not uncommon for some services / Administrators to block specific IP's

If you test via a VPN/ proxy service you suggest that you can connect?

I looked up the A records for the domain across our internal / customer facing and multiple DNS servers externally which all provide consistent results.  Also I've had a colleague test from their own Plusnet connection and that also works fine.

Performing Lookups against our DCDNS

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55


Performing Lookups against Customer DNS

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55


Performing Lookups against External DNS Google & Opendns

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55


Performing Lookups against BT's DNS

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55


Performing Lookups against SKY's DNS

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55


Performing Lookups against Talk Talk's DNS

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55


Performing Lookups against Virgin's DNS

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55


Performing Lookups against Zen's DNS

www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55
www.ericwatsonfs.co.uk.	14400	IN	A	199.34.228.55

Our traceroute's also suggest that we can communicate with the site without any issues.

Kind regards,

"

[#6]

I can confirm what you see..

GOOLE
;; ANSWER SECTION:
www.ericwatsonfs.co.uk. 9770    IN      CNAME   ericwatsonfs.co.uk.
ericwatsonfs.co.uk.     10934   IN      A       91.224.108.20

PLUSNET
;; ANSWER SECTION:
www.ericwatsonfs.co.uk. 14400   IN      CNAME   ericwatsonfs.co.uk.

;; AUTHORITY SECTION:
ericwatsonfs.co.uk.     14400   IN      SOA     ns.123-reg.co.uk. hostmaster.ericwatsonfs.co.uk. 2013080602 86400 0 604800 14400

OPENDNS
;; ANSWER SECTION:
www.ericwatsonfs.co.uk. 14400   IN      CNAME   ericwatsonfs.co.uk.
ericwatsonfs.co.uk.     14400   IN      A       91.224.108.20

[#7]

Oh jee we're back in this thread again lol.

Hope you had a nice holiday but to be honest given your previous response times and the fact that PN aren't bothered... I'm not holding out much hope for you.

[#8]

Sorry to see this is still going on. The only thing I can think of that could be happening now is that the hosting company have blocked your static IP address, however you've advised that this is not the case.

As DNS resolves correctly and you can view the site from the same equipment on a proxy, alternate connection and we can view if from a Plusnet connection on a different IP it could point to the IP being the issue.

This may sound like a drastic measure, but do you utilise the static IP? We could give you a dynamic one, or an alternate static IP to try and resolve this. If we did this we wouldn't be able to restore your original IP address though.

[#9]

@AndyD_OHD - I’m wondering if you have created an entry in your host file or local DNS and forgot it’s there. This might explain the reasons for seeing what you do. Just a thought.

[#10]

It wouldn't explain the lookups the rest of us have been seeing through plusnets nameservers though.

[#11]

---

@Chris wrote:

As DNS resolves correctly

---

But last time I tried it chris it didn't resolve correctly - using your nameservers!

[#12]

Good point, sorry I'd forgotten about that part. I've passed this back through for further investigation.

[#13]

Could this be a clue?

:~$ dig +trace ericwatsonfs.co.uk @212.159.6.10

; <<>> DiG 9.9.5-9+deb8u11-Raspbian <<>> +trace ericwatsonfs.co.uk @212.159.6.10
;; global options: +cmd
.                       17120   IN      NS      h.root-servers.net.
.                       17120   IN      NS      a.root-servers.net.
.                       17120   IN      NS      l.root-servers.net.
.                       17120   IN      NS      g.root-servers.net.
.                       17120   IN      NS      m.root-servers.net.
.                       17120   IN      NS      e.root-servers.net.
.                       17120   IN      NS      i.root-servers.net.
.                       17120   IN      NS      c.root-servers.net.
.                       17120   IN      NS      b.root-servers.net.
.                       17120   IN      NS      j.root-servers.net.
.                       17120   IN      NS      k.root-servers.net.
.                       17120   IN      NS      d.root-servers.net.
.                       17120   IN      NS      f.root-servers.net.
.                       17120   IN      RRSIG   NS 8 0 518400 20170731050000 20170718040000 15768 . Uvd4kjYLtbJWjsnWDwO/223DPqSG3wr2QSJ6Iy8kNmbdL3t+mdRqNl6F M/7dMn4fmhRdMelXYrhN/73pS9mebk4eNBIIMUL1hRQz+fAkjiBPb0Pp k55Zu9g5AhiLdUZhRSCFZAmd7wIJwGYa5S++JJ/LrnF5qxuK9E5RM4O2 lgVE1eCoBQRKO+DBzugDryY3qwcvl43CDHPNif6xqVExZ8+iUCAQoRWq y2fN6d+CKPhdW93f/HIdNopAuRUyvRY3ndukRX1T0z9XOJf/HSRY4mXC 8d3qF472madwP1fe7dZs0qMIY8wMdqAvlnEYm9T/GzMQ4AueaOEA7KNW ZkmDoQ==
;; Received 525 bytes from 212.159.6.10#53(212.159.6.10) in 314 ms

uk.                     172800  IN      NS      nsd.nic.uk.
uk.                     172800  IN      NS      nsb.nic.uk.
uk.                     172800  IN      NS      nsc.nic.uk.
uk.                     172800  IN      NS      dns1.nic.uk.
uk.                     172800  IN      NS      nsa.nic.uk.
uk.                     172800  IN      NS      dns4.nic.uk.
uk.                     172800  IN      NS      dns2.nic.uk.
uk.                     172800  IN      NS      dns3.nic.uk.
uk.                     86400   IN      DS      43876 8 2 A107ED2AC1BD14D924173BC7E827A1153582072394F9272BA37E2353 BC659603
uk.                     86400   IN      RRSIG   DS 8 1 86400 20170731050000 20170718040000 15768 . go07GAam81Gh9IU4JdLEDP5164r5Ue3ht8/UeqlYHKbWfhwjjq3Znz2L xDDHY6OwSkaNlP3hZsok0gV1EoCETtEuaTLGyezIxxvCdue/Y4iSLD6X kI/m0Wmjtcg7qJW1vX8AjrPkZF7N5FsDn74KksD39qgWDlHyGpiAng8S 3Nd6brkfdPlvL3FxLuQtmSeOyeVNdPl+KUhzTeHyE/ic5lQ8eJl9WlSp OzBhFPaLDXfXTfjq0druPyciRIf1ejHI9UiRbGKa6JwlL+dysz+UUH7t y5AHxjEzXb3/62/alHkIhSh0/fWz4nQ1suTlcdItUT0I1bz4BYAWlyvJ smEZwQ==
;; Received 802 bytes from 202.12.27.33#53(m.root-servers.net) in 225 ms

ericwatsonfs.co.uk.     172800  IN      NS      ns1.hostsrvrs.com.
ericwatsonfs.co.uk.     172800  IN      NS      ns2.hostsrvrs.com.
G9F1KIIHM8M9VHJK7LRVETBQCEOGJIQP.co.uk. 10800 IN NSEC3 1 1 0 - G9HKV8PHGJ1NMH94L9RMIQM0J64UCIPK NS SOA RRSIG DNSKEY NSEC3PARAM TYPE65534
G9F1KIIHM8M9VHJK7LRVETBQCEOGJIQP.co.uk. 10800 IN RRSIG NSEC3 8 3 10800 20170818115137 20170714114620 33621 co.uk. x47/HNiNqOZFr2TWw9uIPRXbzhnQK1Mbma5qRcGs/M/1mS5KMP7cY0qb VPOjEk25l+aDITaehOefl83OT885gYaJRUQMDVgZ5A4f5JszGx9N/dFO /5TMblVwm5iuafdsDTxadvmdbjO1uxWbySA+KVWnLWdtQX07s0k8m5TV t80=
SF4VJKFBE5H0H08SQSO450D6262ECETN.co.uk. 10800 IN NSEC3 1 1 0 - SF9RT8JSNP4RFKS6ANMS63DU7NKN7LRC NS DS RRSIG
SF4VJKFBE5H0H08SQSO450D6262ECETN.co.uk. 10800 IN RRSIG NSEC3 8 3 10800 20170815205423 20170711202741 33621 co.uk. QMJtUMNaG9RHxvdVLxilTvgPE4HzCX6zduObXHE7+2ZqV91mvD5FYzlk JVtHA9olUCx2VD+24CCL3cJhZX0W/Zt7Rexx90+1qZmFCNMrHBMvFt9c PxU2RdrOf2+gfvEhkbXJg3Hn+QZtyJrwINX9QG3FUfm78gRAyyh9yFO/ h/I=
;; Received 619 bytes from 156.154.101.3#53(nsb.nic.uk) in 93 ms

ericwatsonfs.co.uk.     14400   IN      A       91.224.108.20
ericwatsonfs.co.uk.     86400   IN      NS      ns2.123-reg.co.uk.
ericwatsonfs.co.uk.     86400   IN      NS      ns.123-reg.co.uk.
;; Received 106 bytes from 109.123.121.102#53(ns2.hostsrvrs.com) in 27 ms

Why are there two sets of authoritative nameservers in DNS? A pair belonging to SiteHQ:

ericwatsonfs.co.uk.     172800  IN      NS      ns1.hostsrvrs.com.
ericwatsonfs.co.uk.     172800  IN      NS      ns2.hostsrvrs.com.

And then these belonging to 123-reg:

ericwatsonfs.co.uk.     86400   IN      NS      ns2.123-reg.co.uk.
ericwatsonfs.co.uk.     86400   IN      NS      ns.123-reg.co.uk.

The former responds to DNS queries for the zone:

:~$ dig ericwatsonfs.co.uk @ns1.hostsrvrs.com

; <<>> DiG 9.9.5-9+deb8u11-Raspbian <<>> ericwatsonfs.co.uk @ns1.hostsrvrs.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11066
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ericwatsonfs.co.uk.            IN      A

;; ANSWER SECTION:
ericwatsonfs.co.uk.     14400   IN      A       91.224.108.20

The latter doesn't though:

:~$ dig ericwatsonfs.co.uk @ns2.123-reg.co.uk

; <<>> DiG 9.9.5-9+deb8u11-Raspbian <<>> ericwatsonfs.co.uk @ns2.123-reg.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25851
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1680
;; QUESTION SECTION:
;ericwatsonfs.co.uk.            IN      A

I'm no expert on DNS, but the authority for the domain looks all screwed up to me. It could just be that some DNS resolvers are handling the fallout more gracefully than ours/Plusnet's.

I think the root (no pun intended) of the problem is upstream from us.

Edit: Looking in whois, the domain is registered with 123-reg and hosted with SiteHQ. Why therefore are there NS entries in DNS for 123-reg?

[#14]

Hi Mook, I haven't made any changes at all. Basically I was able to upload the site one day then the next I wasn't. I can view site, access via ftp if I am using another ISP but that would mean visiting friends whenever I want to upload anything to the site, all a bit inconvenient. My host has no problem accessing the site and they are confused as to why whenever Plusnet try their tests that the Weebly ip comes up as their own tests bring up their own ip.

[#15]

7UP thanks for the vote of confidence lol. Response times have been slow from me because I have been trying to get help from Plusnet but it all seems to go round in circles. I now have to tell them that site is not with Weebly, something I did weeeeeks ago. I don't want to mess about with using Google DNS simply because I am not familiar with doing that sort of thing. I had hoped Plusnet could sort it out. I have no problem off their network, and as my home office uses their network, it does get a bit frustrating.