Forum Discussion
- Client62Alessandro Volta
Keep on using dns.google !
Virgin Media's primary and secondary DNS both lack an entry for www.battleye.com
This is some kind of DNS propagation failure resulting in ...
> nslookup www.battleye.com
Server: cache1.service.virginmedia.net
Address: 194.168.4.100*** cache1.service.virginmedia.net can't find www.battleye.com: Server failed
Yet with ( any ) Public DNS we have success ...
> nslookup www.battleye.com dns.google
Server: dns.google
Address: 8.8.8.8Non-authoritative answer:
Name: www.battleye.com
Addresses: 2606:4700:3036::ac43:cbe9
2606:4700:3033::6815:2cd3
104.21.44.211
172.67.203.233 - Client62Alessandro Volta
This morning the VM DNS is working ...
> nslookup www.battleye.com
Server: cache1.service.virginmedia.net
Address: 194.168.4.100Non-authoritative answer:
Name: www.battleye.com
Addresses: 2606:4700:3033::6815:2cd3
2606:4700:3036::ac43:cbe9
104.21.44.211
172.67.203.233 - Client62Alessandro Volta
A duplicate post has appeared at :
https://community.virginmedia.com/t5/Networking-and-WiFi/DNS-errors-when-trying-to-connect-to-battle-eye/td-p/5569246
Related Content
- 10 months ago
- 4 months ago
- 3 months ago
- 4 months ago