DNS not resolving on google, but is on other services

G.W. Haywood bind at jubileegroup.co.uk
Sat Feb 17 12:48:14 UTC 2018


Hi there,

On Sat, 17 Feb 2018, LuKreme wrote:

> ... Is google just b0rked? ...

You might need to look closer to home.

You claim three nameservers, but it appears that they're all on the
same network segment - a *really* bad idea - and one of them doesn't
respond to DNS requests, using IPs located both here in the UK and
way over in the western USA:

8<----------------------------------------------------------------------
laptop3:~$ >>> dig www.david-dodge.com
[snip]
;; ANSWER SECTION:
www.david-dodge.com.    86349   IN      CNAME   www.covisp.net.
www.covisp.net.         86361   IN      A       65.121.55.45
;; AUTHORITY SECTION:
covisp.net.             172119  IN      NS      ns2.covisp.net.
covisp.net.             172119  IN      NS      ns3.covisp.net.
covisp.net.             172119  IN      NS      ns1.covisp.net.
[snip]
8<----------------------------------------------------------------------
laptop3:~$ >>> dig @ns1.covisp.net -t any covisp.net
[snip]
;; ANSWER SECTION:
covisp.net.             86400   IN      SOA     ns1.covisp.net. root.covisp.net. 2018020300 14400 1800 1209600 3600
covisp.net.             172800  IN      NS      ns1.covisp.net.
covisp.net.             172800  IN      NS      ns2.covisp.net.
covisp.net.             172800  IN      NS      ns3.covisp.net.
covisp.net.             172800  IN      MX      10 mail.covisp.net.
covisp.net.             86400   IN      TXT     "v=spf1 mx a ip4:65.121.55.42/32 -all"
covisp.net.             86400   IN      TXT     "google-site-verification=6rB9Dkgu8_hfTbLiieRTAkvFitENOvyszmzoAu1N27U"
covisp.net.             86400   IN      A       65.121.55.42
;; ADDITIONAL SECTION:
ns1.covisp.net.         172800  IN      A       65.121.55.42
ns2.covisp.net.         172800  IN      A       65.121.55.43
ns3.covisp.net.         172800  IN      A       65.121.55.45
mail.covisp.net.        172800  IN      A       65.121.55.42
[snip]
8<----------------------------------------------------------------------
laptop3:~$ >>> dig @ns3.covisp.net -t any covisp.net
; <<>> DiG 9.10.3-P4-Debian <<>> @ns3.covisp.net -t any covisp.net
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
8<----------------------------------------------------------------------

However ns3 responds to 'ping'
8<----------------------------------------------------------------------
laptop3:~$ >>> ping ns3.covisp.net
PING ns3.covisp.net (65.121.55.45) 56(84) bytes of data.
64 bytes from www.covisp.net (65.121.55.45): icmp_seq=1 ttl=49 time=141 ms
64 bytes from www.covisp.net (65.121.55.45): icmp_seq=2 ttl=49 time=141 ms
64 bytes from www.covisp.net (65.121.55.45): icmp_seq=3 ttl=49 time=141 ms
...
8<----------------------------------------------------------------------

Maybe the nameserver just isn't running?

Perhaps you should look into one of the free DNS slave services.

-- 

73,
Ged.


More information about the bind-users mailing list