on 29-07-2021 10:44
Returning wrong (old?) address from both Virgin resolvers:
```
$ dig github.com @194.168.8.100
; <<>> DiG 9.16.1-Ubuntu <<>> github.com @194.168.8.100
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26097
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;github.com. IN A
;; ANSWER SECTION:
github.com. 0 IN A 81.99.162.48
```
$ dig github.com @8.8.8.8
; <<>> DiG 9.16.1-Ubuntu <<>> github.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14014
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;github.com. IN A
;; ANSWER SECTION:
github.com. 59 IN A 140.82.121.4
```
It's been this way for several days, looks like A record changed to 140.82.121.4 on 18/7/21.
Thank you!
Answered! Go to Answer
on 29-07-2021 13:47
on 29-07-2021 13:47
on 30-07-2021 10:28
Yep, added github.com to allowed sites and it's now working. Thank you!
What category of forbidden content would that be under I wonder? Hacking seems the only possibility, but that seems rather bleak...
on 31-07-2021 11:16
Hi @devlinm.
Welcome to the community and thanks for your first post, we're happy to have you with us 🙂
Apologies you were having some issues with this, I'm glad to see @legacy1 was able to help get this sorted for you.
If you have any further issues please let us know and we'll happily assist.
Thanks,
New around here? To find out more about the Community check out our Getting Started guide